Meta tags:
description=Namespace accelerates the development workflow of fast-moving software engineering teams. Best-in-class compute and development-supporting services that lead to 2x-10x faster builds, tests, and more.;

Headings (most frequently used words):

devboxes, agents, with, for, commands, configuration, devbox, upload, coding, agent, skills, creating, and, configuring, pool, api, useful, claude, managed, best, practices, introducing, we, re, hiring, join, us, ephemeral, spec, file, dynamic, stdin, egress, filtering, handling, secrets, run, ssh, files,

Text of the page (most frequently used words):
the (95), nsc (73), #devbox (64), and (34), agent (27), devboxes (25), for (24), base (18), github (18), task (14), #agents (14), upload (14), ssh (14), use (13), when (13), create (13), from (13), lease (13), run (12), patch (12), git (12), nam (12), changes (11), ephemeral (11), registry (11), repository (10), namespace (10), artifact (10), spec (10), list (10), docker (10), commands (9), setup (9), tmp (9), workspaces (9), namespacelabs (9), name (8), rep (8), pool (8), image (8), actions (8), this (7), file (7), with (7), useful (7), cache (7), profile (7), not (6), work (6), release (6), can (6), test (6), cli (6), command (6), are (6), api (6), skills (6), describe (6), action (6), nscloud (6), overview (6), access (5), claude (5), files (5), them (5), checkout (5), source (5), delete (5), vault (5), instance (5), token (5), needs (4), network_policy (4), default (4), apply (4), running (4), after (4), that (4), origin (4), into (4), should (4), runs (4), acquire (4), egress (4), filtering (4), your (4), com (4), stdin (4), yaml (4), generate (4), one (4), build (4), project (4), skill (4), coding (4), login (4), buildx (4), secrets (3), outbound (3), domains (3), egress_domains (3), does (3), same (3), name_prefix (3), ref (3), before (3), leases (3), see (3), example (3), depth (3), fetch (3), typical (3), inside (3), returns (3), review (3), releases (3), lets (3), across (3), tasks (3), secret (3), allowed (3), workspace (3), configuration (3), storage (3), result (3), gives (3), install (3), machine (3), auth (3), update (3), download (3), ingress (3), expose (3), kubernetes (3), container (3), remote (3), images (3), started (3), from_secret_id (2), true (2), parallel (2), several (2), shards (2), time (2), warm (2), reset (2), check (2), out (2), intended (2), current (2), expire (2), success (2), failure (2), cancellation (2), done (2), managed (2), session (2), guide (2), covers (2), depends (2), main (2), copies (2), has (2), usually (2), non (2), state (2), bot (2), acquires (2), tag (2), its (2), available (2), creates (2), new (2), reuse (2), without (2), package (2), tokens (2), other (2), reference (2), more (2), services (2), domain (2), integrations (2), org (2), set (2), prefix (2), pass (2), read (2), exact (2), url (2), size (2), policy (2), off (2), code (2), repeatable (2), creating (2), ask (2), installation (2), add (2), you (2), want (2), linux (2), status (2), trust (2), sccache (2), pants (2), gradle (2), bazel (2), expiration (2), extend (2), volume (2), job (2), logs (2), usage (2), builds (2), circleci (2), security (2), limits (2), custom (2), getting (2), logo (2), open (2), last, updated, june, 2026, restrict, sandbox, but, need, disabled, no_checkout, avoid, collisions, treat, pooled, clean, keep, best, practices, each, backed, provisioned, starts, steps, integration, tracked, untracked, separately, bundle, applying, diff, head, merge, sync, flow, checks, known, commit, uploads, applies, there, local, commonly, generated, config, separates, arguments, acquired, created, drive, through, interactive, two, especially, copying, leased, may, contain, previous, using, releasing, member, removed, npm, output, prepares, prints, unleased, already, exists, none, adds, finishes, stays, later, identified, value, injected, environment, appearing, keys, credentials, github_token, env, put, passwords, prompts, store, handling, details, including, how, monitor, denied, requests, omit, private, combine, allowlists, existing, controls, openai, npmjs, githubusercontent, include, subdomains, infrastructure, operate, restricted, only, reach, hosts, registries, model, apis, needed, parsed, json, toml, from_format, cat, also, dynamically, over, dynamic, choose, appends, random, suffix, colliding, names, repo, builtin, define, lifecycle, network, place, ties, single, stops, both, deleted, which, fire, once, load, onto, collect, stop, interactively, simple, flags, enough, concrete, configuring, behavior, relevant, requested, reports, deletes, used, tests, larger, suites, split, multiple, suite, start, npx, directory, global, carry, instructions, everyone, globally, projects, own, worked, testing, publishes, instruction, pack, workflow, loading, cleaning, page, features, most, doing, execution, where, clone, dependencies, return, provide, amd64, machines, scriptable, way, support, center, soc2, changelog, revoke, relationships, dev, share, submodules, optimize, cleanup, attach, context, kubectl, kubeconfig, write, port, forward, proxy, rdp, vnc, top, report, destroy, version, turbocache, breakpoint, cluster, sdk, explorer, dashboard, rwx, openid, gcp, aws, federation, permissions, audit, logging, data, residency, billing, performance, networking, volumes, resource, shapes, display, observability, windows, macos, compute, any, framework, tailscale, checkouts, nix, moonrepo, android, emulators, playwright, turborepo, sessions, development, managing, introduction, containers, previews, tracing, builders, optimizing, migration, debugging, caching, roles, hiring, join, article, introducing, sidebar, get, company, resources, pricing, customers, cases,

Text of the page (random words):
ai agents devboxes namespace logo use cases customers pricing resources company get started login open sidebar introducing devboxes read article we re hiring join us open roles logo overview github actions getting started caching docker builds custom base images debugging github actions migration guide optimizing usage reference docker builders getting started container registry tracing logs previews containers kubernetes devboxes introduction managing devboxes remote development sessions custom images coding agents integrations bazel turborepo playwright android emulators gradle sccache circleci pants moonrepo nix git checkouts docker images claude tailscale any framework compute overview linux macos windows observability ssh remote display machine shapes resource limits storage overview cache volumes container registry artifact storage secrets networking overview ingress performance security egress filtering workspaces overview access billing and limits data residency security audit logging permissions federation overview aws gcp openid github actions circleci rwx dashboard github actions builds registry usage explorer api sdk github actions namespacelabs nscloud setup namespacelabs nscloud setup buildx action namespacelabs nscloud cluster action namespacelabs nscloud cache action namespacelabs nscloud checkout action namespacelabs nscloud expose kubernetes action namespace actions upload artifact namespace actions download artifact namespacelabs breakpoint action namespace actions setup turbocache cli installation nsc version nsc login nsc workspace describe nsc create nsc destroy nsc extend nsc list nsc instance report nsc logs nsc top nsc ssh nsc vnc nsc rdp nsc proxy nsc instance port forward nsc instance download nsc instance upload nsc kubeconfig write nsc kubectl nsc docker login nsc docker attach context nsc docker remote nsc docker buildx setup nsc docker buildx cleanup nsc docker buildx status nsc build nsc base image upload nsc base image optimize nsc run nsc expose container nsc expose kubernetes nsc ingress list nsc ingress generate access token nsc github profile nsc github profile create nsc github profile list nsc github profile describe nsc github profile update nsc github profile delete nsc github profile test build base image nsc github base image list nsc github base image describe nsc github job list nsc github job describe nsc git checkout update submodules nsc volume list nsc volume release nsc artifact upload nsc artifact download nsc artifact expire nsc artifact extend nsc artifact describe nsc artifact cache url nsc registry list nsc registry describe nsc registry share nsc registry update image expiration nsc registry policy nsc registry default expiration nsc cache bazel setup nsc cache gradle setup nsc cache pants setup nsc cache sccache setup nsc vault list nsc vault add nsc vault set nsc vault delete nsc auth check login nsc auth generate dev token nsc auth trust relationships nsc token create nsc token list nsc token revoke changelog trust center soc2 status support devboxes for coding agents a coding agent needs a machine where it can clone a repository install dependencies run commands and return the result devboxes provide linux amd64 machines with docker and the devbox cli gives agents a scriptable way to create lease access and delete them this page covers the devbox features that are most useful when an agent is doing the work the devbox agent skill ephemeral devboxes the pool api command execution file upload and egress filtering agent skills namespace publishes devbox skills in namespacelabs agent skills a skill is an instruction pack for coding agents it gives the agent a repeatable workflow for creating devboxes loading source code running commands and cleaning up after the task for a worked example see testing with devboxes and agent skills install the skill in a project when you want the repository to carry the same agent instructions for everyone install it globally when you want to use the skill across projects from your own machine project global run this from the project directory npx skills add namespacelabs agent skills after installation start the agent from the repository and ask it to use devboxes for a task for example run the test suite in a devbox for larger suites ask the agent to split the work across multiple devboxes run the tests in parallel devboxes the exact behavior depends on the agent and the project in a typical run the agent creates one or more devboxes copies the relevant source state into them runs the requested commands reports the result and deletes or releases the devboxes it used creating and configuring devboxes agents usually create devboxes non interactively for a simple one off task the cli flags are enough for repeatable tasks a spec file gives the agent a concrete configuration to generate review and reuse ephemeral devboxes ephemeral devboxes are useful for one off agent tasks an agent can create an ephemeral devbox load source code onto it run a build or test command collect the result and stop it ephemeral ties the devbox s instance and storage to a single run when it stops both are deleted which is useful for fire once test or build runs create an ephemeral devbox from the cli devbox create ephemeral spec file configuration a spec file lets an agent define the devbox name image size repository lifecycle and network policy in one place devbox yaml name_prefix agent run image builtin base size m ephemeral true repository url github com your org your repo ref main create the devbox from the spec file devbox create from devbox yaml use name_prefix when the agent should not choose an exact devbox name namespace appends a random suffix to the prefix this lets several agents or shards create devboxes at the same time without colliding on names dynamic configuration with stdin agents can also generate a spec dynamically and pass it over stdin pass to read the spec from stdin cat devbox yaml devbox create from stdin is parsed as yaml by default use from_format for json or toml egress filtering a devbox can be restricted to a list of allowed outbound domains this is useful when an agent should only reach source hosts package registries model apis or other services needed for the task set network_policy egress_domains in the devbox spec prefix a domain with to include its subdomains namespace infrastructure domains are allowed so the devbox can operate network_policy egress_domains github com githubusercontent com registry npmjs org api openai com omit network_policy to use the workspace default if a task needs private services combine domain allowlists with your existing workspace integrations and access controls see egress filtering for more details including how to monitor allowed and denied outbound requests handling secrets do not put tokens or passwords in prompts or spec files store them in the namespace vault and reference the secret id from the devbox spec env name github_token from_secret_id secret id the secret value is injected into the devbox environment without appearing in the spec use this for package registry tokens api keys and other task credentials pool api the pool api lets an agent reuse warm devboxes across tasks a pool is identified by a tag when the agent has work to do it acquires a devbox from that pool if an unleased devbox already exists for the tag devbox acquire leases it and returns its name if none is available namespace creates a new devbox adds it to the pool leases it and returns the new name when the task finishes the agent releases the lease and the devbox stays available for later work devbox acquire review bot the command prints the devbox name and a lease id release the lease when the task is done devbox release lease lease i d a typical task acquires a devbox prepares the repository runs the command and releases the lease devbox acquire review bot use the devbox name and lease id from the acquire output devbox ssh nam e git c workspaces rep o fetch depth 1 origin base devbox ssh nam e git c workspaces rep o checkout base devbox upload nam e tmp changes patch tmp changes patch devbox ssh nam e git c workspaces rep o apply tmp changes patch devbox ssh nam e npm test devbox release lease lease i d release the lease on success failure and cancellation so the devbox returns to the pool a leased devbox may contain state from the previous task before using it reset the repository to the intended base ref and apply the current task s changes releasing a lease does not delete the devbox use devbox delete when the pool member should be removed useful commands for agents agents usually drive devboxes through non interactive cli commands two commands are especially useful devbox ssh for running commands inside the devbox and devbox upload for copying files into it run commands with devbox ssh devbox ssh runs a command in a devbox this is useful after the agent has acquired a lease or created an ephemeral devbox devbox ssh nam e git c workspaces rep o fetch depth 1 origin base devbox ssh nam e git c workspaces rep o checkout base the separates devbox cli arguments from the command that should run inside the devbox upload files with devbox upload devbox upload copies a local file into a devbox agents commonly use it to upload a patch a generated config file or a test artifact devbox upload nam e tmp changes patch tmp changes patch a typical source sync flow checks out a known base commit inside the devbox uploads a patch and applies it there base git merge base origin main head git diff base tmp changes patch devbox ssh nam e git c workspaces rep o fetch depth 1 origin base devbox ssh nam e git c workspaces rep o checkout base devbox upload nam e tmp changes patch tmp changes patch devbox ssh nam e git c workspaces rep o apply tmp changes patch this example covers tracked files if the task depends on untracked files upload them separately or bundle them before applying the patch claude managed agents claude managed agents can run on namespace devboxes each claude agent session is backed by an ephemeral devbox that is provisioned when the session starts see the claude integration guide for setup steps best practices expire ephemeral devboxes and release leases on success failure and cancellation so work does not keep running after the agent is done treat pooled devboxes as warm not clean reset the repository check out the intended ref and apply the current task s changes before running commands use name_prefix for parallel work to avoid name collisions when several agents or shards create devboxes at the same time use no_checkout or repository disabled true when the agent needs a sandbox but does not need the default repository use from_secret_id for secrets and network_policy egress_domains to restrict outbound access to the domains the task needs last updated june 19 2026