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):

instance, the, runner, identify, id, debugging, job, access, vnc, rdp, start, session, github, actions, interactive, remote, display, observability, investigating, queue, time, hands, on, support, introducing, devboxes, we, re, hiring, join, us, pause, execution, setting, breakpoints, ssh, integration, performance, metrics, advanced, logging, capabilities, out, of, memory, oom, detection, crash, dump, collection, connect, to, an,

Text of the page (most frequently used words):
nsc (79), the (64), and (29), you (28), job (26), your (25), #instance (24), github (24), can (22), namespace (20), #runner (18), access (17), actions (15), our (13), ssh (13), logs (12), with (11), for (11), debugging (10), performance (10), running (10), step (10), docker (10), action (10), support (9), session (9), name (9), namespacelabs (9), list (9), registry (9), artifact (9), from (8), time (8), also (8), execution (8), memory (8), into (8), open (8), vnc (8), breakpoint (8), profile (8), setup (8), usage (7), dashboard (7), build (7), which (7), cache (7), out (6), workflows (6), metrics (6), run (6), identify (6), rdp (6), runners (6), will (6), token (6), image (6), describe (6), base (6), nscloud (6), overview (6), are (5), that (5), default (5), not (5), workflow (5), start (5), available (5), connect (5), remote (5), reach (4), resource (4), limits (4), custom (4), queue (4), comprehensive (4), crash (4), get (4), any (4), direct (4), container (4), current (4), this (4), set (4), using (4), cli (4), interactive (4), display (4), linux (4), checkout (4), login (4), vault (4), upload (4), buildx (4), team (3), jobs (3), over (3), but (3), understand (3), view (3), investigating (3), investigation (3), insights (3), detect (3), these (3), consumption (3), allocation (3), patterns (3), when (3), logging (3), visibility (3), runs (3), track (3), read (3), write (3), storage (3), look (3), ran (3), found (3), windows (3), currently (3), macos (3), use (3), command (3), line (3), through (3), jump (3), terminal (3), environment (3), tests (3), pause (3), troubleshooting (3), create (3), auth (3), update (3), download (3), ingress (3), expose (3), kubernetes (3), images (3), devboxes (3), started (3), join (2), community (2), one (2), need (2), plan (2), see (2), explorer (2), top (2), recent (2), automatically (2), dumps (2), invaluable (2), dump (2), collection (2), enabled (2), give (2), leaks (2), excessive (2), oom (2), detection (2), traditional (2), containers (2), providing (2), capabilities (2), allows (2), previous (2), network (2), disk (2), bottlenecks (2), cpu (2), steps (2), gain (2), observability (2), visual (2), integration (2), development (2), directly (2), debug (2), issues (2), native (2), executing (2), active (2), sessions (2), continue (2), while (2), examine (2), commands (2), rendezvous (2), minutes (2), until (2), paused (2), username (2), uses (2), failed (2), permissions (2), state (2), breakpoints (2), eliminates (2), resume (2), press (2), status (2), trust (2), generate (2), delete (2), sccache (2), pants (2), gradle (2), bazel (2), expiration (2), extend (2), volume (2), git (2), builds (2), circleci (2), security (2), getting (2), logo (2), last, updated, april, 2026, learn, about, tips, best, practices, discord, talk, engineers, technical, got, stuck, help, here, assist, hands, frequently, reaching, may, benefit, larger, happy, put, together, plans, scale, thousands, vcpus, tbs, ram, sales, most, common, reason, hitting, concurrency, concurrent, offers, analytics, displays, durations, changing, right, case, surprisingly, long, adjust, timeframe, match, crashes, collect, store, them, contain, forensic, information, useful, determining, cause, artifacts, graphs, already, however, only, working, hard, isolate, was, close, limit, encountered, error, automatic, makes, conditions, explicit, simple, collects, retains, too, hovering, easily, correlate, associated, correlation, issued, linked, granting, telemetry, unlike, provides, within, goes, far, beyond, standard, every, aspect, advanced, panel, compare, history, bandwidth, connection, activity, processor, utilization, across, all, cores, intensive, operations, dedicated, correlating, comparing, helps, improvements, detailed, monitoring, rely, other, platforms, mac, supports, multiple, options, gui, applications, testing, user, interfaces, related, coming, soon, enrolled, note, regio, alternatively, simplest, path, browser, web, interface, above, methods, based, modify, without, pausing, still, count, towards, manually, exactly, what, happening, 44793, now, utc, jun, endpoint, 5000, connecting, emit, instructions, how, compatible, outside, another, authorized, users, 15m, duration, failure, bash, shell, repository, contents, point, investigate, variables, interactively, replicate, locally, just, exploring, immediately, setting, after, inactivity, proceed, next, finish, troubleshoot, button, find, target, runing, feature, perfect, examining, file, systems, diagnostic, environments, they, enabling, real, often, involves, guesswork, log, parsing, consuming, iteration, cycles, pain, points, deep, their, characteristics, center, soc2, changelog, revoke, relationships, dev, check, add, policy, share, url, expire, release, submodules, test, optimize, cleanup, attach, context, kubectl, kubeconfig, port, forward, proxy, report, destroy, workspace, version, installation, turbocache, cluster, api, sdk, rwx, openid, gcp, aws, federation, audit, data, residency, billing, workspaces, egress, filtering, networking, secrets, volumes, machine, shapes, compute, framework, tailscale, claude, checkouts, nix, moonrepo, android, emulators, playwright, turborepo, integrations, coding, agents, managing, introduction, previews, tracing, builders, reference, optimizing, migration, guide, caching, roles, hiring, article, introducing, sidebar, company, resources, pricing, customers, cases,

Text of the page (random words):
debugging github actions 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 debugging github actions traditional ci debugging often involves guesswork log parsing and time consuming iteration cycles namespace eliminates these pain points by providing comprehensive debugging capabilities that give you direct access to your running workflows and deep visibility into their performance characteristics interactive debugging get direct access to your runners while they re executing your workflows enabling real time debugging and investigation pause job execution you can pause execution of a running job and connect to it using an interactive terminal for command line debugging and investigation this is perfect for examining file systems running diagnostic commands and troubleshooting build environments this feature is available for jobs running on linux find the target job on namespace dashboard if the job is currently running you will see the step the is currently runing press the troubleshoot button and a terminal session into the execution environment of the current step will open the execution of the current step will continue but the workflow will not proceed to the next step until you finish the troubleshooting session and press resume if step execution is paused but no troubleshooting session is open execution will automatically resume after 10 minutes of inactivity setting breakpoints pause your github actions workflows at any point to investigate the current state examine variables and debug issues interactively using breakpoints eliminates the need to replicate the ci environment locally you can just jump into the failed state and start exploring immediately jobs tests runs on namespace profile default permissions id token write contents read steps name checkout the repository uses actions checkout v4 name run tests shell bash run name breakpoint if tests failed if failure uses namespacelabs breakpoint action v0 with duration 15m authorized users your github username another github username the breakpoint action will emit instructions how to access the paused runner the action is compatible with any runners and also available outside of namespace run namespacelabs breakpoint action v0 connecting endpoint rendezvous namespace so 5000 breakpoint running until jun 26 09 58 26 utc 14 minutes from now connect with ssh p 44793 runner rendezvous namespace so while the breakpoint is active you can also vnc into the runner to examine the environment run commands manually and understand exactly what is happening in your workflow workflows with active breakpoint sessions are still running and continue to count towards your usage instance ssh access if the above methods are not available e g the job is not linux based and you can t modify the workflow you can access the instance that is executing the job directly without pausing the workflow the simplest path to jump into an interactive terminal is through your browser with our web ssh interface alternatively you can jump into an ssh session from your command line identify the runner instance id open the set up job step in your job logs the instance id can be found in the runner name runner name nsc runner instance id you can also look up which instance ran which job in our dashboard connect to the runner to open an ssh session you can use our cli or connect using native ssh nsc ssh instance i d ssh instance i d ssh regio n namespace so ssh access is available for linux and macos runners with windows support coming soon note native ssh access is not enabled by default reach out to our support team to get enrolled remote display namespace supports visual debug access through multiple options which is invaluable for debugging gui applications testing user interfaces and investigating display related issues vnc integration access your mac runners through remote display vnc directly from the namespace dashboard you can also start a vnc session from your command line identify the runner instance id open the set up job step in your job logs the instance id can be found in the runner name runner name nsc runner instance id you can also look up which instance ran which job in our dashboard start a vnc session to connect to the runner instance you can use our cli nsc vnc instance i d vnc support is currently available for macos runners support for other platforms is in development rdp access to gain interactive visual access to your windows runners you can rely on our rdp integration you can start an rdp session using our cli identify the runner instance id open the set up job step in your job logs the instance id can be found in the runner name runner name nsc runner instance id you can also look up which instance ran which job in our dashboard start an rdp session nsc rdp instance i d job observability gain comprehensive insights into your github actions performance with detailed metrics logs and resource monitoring performance metrics the dedicated job view allows correlating job steps with performance metrics and comparing a job s performance to previous runs this visibility helps you identify performance bottlenecks and track improvements over time cpu usage track processor utilization across all cores identify cpu intensive operations memory consumption detect memory leaks and excessive allocation disk i o understand disk read write patterns identify storage bottlenecks network activity track network usage bandwidth consumption and connection patterns the previous runs panel allows you to compare the performance of the current run to the recent history of this job advanced logging capabilities access comprehensive logging that goes far beyond standard github actions logs providing visibility into every aspect of your workflow execution container logs unlike traditional github actions namespace provides direct access to logs from running containers within your workflows build logs any docker build issued from a namespace runner is linked from the job ui granting you direct access to the build logs and build performance telemetry metrics correlation namespace also collects and retains step logs too when hovering over a step you can easily correlate it with the associated instance metrics out of memory oom detection memory consumption graphs can already give insights on memory leaks and excessive allocation patterns however when only working with memory allocation metrics it is hard to isolate if a job was running close to a memory limit or encountered an error when running out of memory namespace s automatic oom detection makes these conditions explicit and simple to detect crash dump collection namespace can automatically detect if your job execution crashes collect crash dumps and store them as artifacts these dumps contain invaluable forensic information useful for determining the cause of the crash crash dump collection is not enabled by default reach out to support namespace so to get access investigating queue time the insights view offers comprehensive performance analytics of your jobs over time by default the explorer displays your job durations but you can also understand the queue time by changing the view on the top right if you are investigating a recent case of surprisingly long queue time adjust the timeframe to match your investigation the most common reason for queue time is that you are hitting your concurrency limits you can see the concurrent resource usage in the usage dashboard if you are frequently reaching your resource limits you may benefit from a larger plan we d be happy to put a custom plan together for you reach out to our sales team for custom plans that scale up to thousands of vcpus and tbs of ram hands on support got stuck need help with debugging one of your workflows our team is here to assist technical support reach out to support namespace so to talk to one of our engineers community join our community discord to learn about tips and best practices last updated april 25 2026