NAH CLOUD · CLOUD AGENTS

Nah agents on
real Linux sandboxes.

Deploy Nah agents in the cloud with a persistent filesystem, your own model key, and every model and tool step streamed live to your terminal. The sandbox keeps running when you disconnect.

Persistent sandbox Your model key Live event stream
sandbox-eu-1 · nah ACTIVE
❯nah cloud attach sandbox-eu-1
Connected to sandbox-eu-1 (eu-central-1)
Filesystem: persistent · Node: 20.x
Agent: code-reviewer · Status: running
[model] Analyzing pull request #412…
[tool] grep src/auth/session.ts · 3 matches
[tool] edit src/auth/session.ts · +6 −4
[model] Fix applied. Tests passing.
Cloud sandbox
Persistent
Terminal access
Socket attached
Spend meter
$0.014 / $2.00
Model key
Your own
Sandbox stays alive between sessions
01 / WHAT A CLOUD AGENT IS

A real machine,
not a container API.

Most hosted agent products hand you a container API and call it a machine. Nah Cloud gives you a persistent Linux sandbox with a working tree, package manager, and build — the same machine you'd use locally, reachable from your terminal.

Linux sandbox with working tree Runtime daemon pre-installed Socket-attached terminal Sessions survive disconnect Spend tracked per run
Launch your first agent
HOSTED SANDBOX LIVE
CLI attachessocket · eu-central-1
Agent runssandboxed Linux
Spend trackedper run, per agent
Trace stored
run_01J8…3 events · 1 tool
02 / LIVE SESSION

Watch the agent
work in real time.

Every model response, tool call, and approval appears in your terminal as it happens. You decide what the agent can change — before it touches a file.

See the CLI guide
~/work/acme · nah INTERACTIVE
❯ Fix the session refresh edge case and add a regression test
I’ll trace the refresh flow, then make the smallest safe change.
grepsrc/auth/session.ts3 matches
readsrc/auth/session.ts:40-112complete
Permission required
edit src/auth/session.ts

Update the expired-token branch and preserve the existing retry behavior.

Reject
❯
ASK MODEsession · 02:14claude-sonnet · $0.08
HOW IT WORKS

Three steps, then it is not your problem.

No image to build, no service to supervise. The daemon is already running by the time the sandbox exists.

See CLI modes
01 / FORK

A sandbox appears

A stopped snapshot becomes a fresh machine in seconds.

02 / ATTACH

Point the CLI at it

One flag streams events over a socket.

03 / WALK AWAY

Detach and reconnect

The session keeps running while you're gone.

Fork sandboxpersistent Linux machine
Attach CLIsocket · eu-central-1
Walk awaysession keeps running
Reconnect anytime
03 / SPEND AND LIMITS

Budgets are first
class.

Set spend, token, and step limits per agent. Track cumulative usage in real time and know exactly why a run stopped. You bring the model key; we meter the runtime.

$ nah cloud run --max-spend 2 ↵
See pricing tiers
SPEND METER ACTIVE
Run spendAll agents⌄
AGENTSTATUSSPEND
code-reviewercomplete$0.018
nahcomplete$0.042
docs-writerrunning$0.009
TOTAL SPEND $0.069
Across 3 runs today
04 / OBSERVABILITY

Every run leaves a
trace.

Model responses, tool calls, results, and stop reasons are recorded as they happen. Inspect any run from the dashboard or replay the event stream in your terminal.

Model responseFound two files to inspect
grep · src/api/**/*.ts8 matches returned
Model responseReviewed validation path
read · route.tsLines 24–90
READY TO RUN

Start with a loop
you can see.

Bring your own model key. We handle the sandbox, the streaming, and the trace storage.