NOME Code

NOME Code is the native, repo-aware workspace for continuing an authenticated coding task from your Mac or iPhone. NOME owns identity, model selection, permissions, events, persistence, and cross-device presentation. The selected provider runtime remains responsible for reasoning and code execution.

The current path is intentionally narrow: WorkOS authenticates the user, the Rust API owns application policy and PostgreSQL state, and an explicitly authorized seat worker runs the selected provider on a trusted Mac. The public catalog shows only models and efforts that the server reports as selectable on an available worker.

Model, provider, effort, access method, and execution host form one validated server selection. Native clients never invent efforts, silently switch providers, or choose an unavailable fallback. See Models and access.

A worker is an authenticated execution endpoint with an owner, device identity, public key, supported provider seats, allowed workspace roots, availability, and policy. Public self-service pairing, cloud handoff, and additional operating systems will ship only after the physical Mac and iPhone path is proven. See Trusted workers.

Execution policy is exactly Read only, Ask, or Full access. Full access is an explicit durable grant for a trusted host and scope; Ask creates a persisted approval that resumes one paused job idempotently. See Permissions.

PostgreSQL is the durable authority for threads, messages, jobs, events, approvals, and bounded cross-thread memory. Rust compiles the smallest sufficient private context for the selected provider. Native caches are projections, never a second memory system. See Memory and continuity.

Provider credentials stay in their supported host storage. NOME does not embed service keys in native clients or copy subscription credentials into prompts, receipts, logs, or notifications. Every privileged action is scoped, auditable, and revocable. See Security.