Full terminal
Use the shells and agent CLIs you already trust.
Ratatosk wraps real PTYs with tabs, panes, scrollback, command entry, and transcripts while preserving the shell underneath.
Full terminal. App preview. Mobile control.
Build apps with AI agents in a real terminal workspace.
Run Codex, Claude, shell jobs, and watchers in real terminals. Ratatosk keeps the app-building loop together: prompt, PTY, browser preview, phone approval, agent status, and session recovery. Run it on your Mac or in an isolated cloud workstation; the workspace stays the same.
App build loop
Prompt, patch, preview, approval, and review stay in one resumable workspace.
Agent workspace
Codex, Claude, scripts, and watchers get names, status, and transcripts.
Control from phone
Approve, nudge, resume, and route access without sitting at the machine.
Ratatosk Terminal
MacBook / ratatosk-cloud / real PTY
READY
ratatosk-cloud / app-build
working
$ codex build billing-dashboard
PTY attached: isolated cloud workstation
workspace: ratatosk-cloud/apps/billing
agent: editing routes, tests, and preview
status: app preview live, patch open
mobile: approval received from phone
execution node: MacBook or isolated cloud workstation
$
ratatosk send "ship the review patch"
User asks
Build a billing dashboard with Stripe import, audit trail, and phone review.
App preview
billing.localhost / review patch
Billing Dashboard
LIVE
Audit log added
Codex patched the route, model, and empty state while the terminal stayed live.
Preview checks
Browser loaded, auth mocked, smoke path green.
review
app is ready
review
Prompt
app requested
Terminal
PTY working
Phone
approved
Preview
review ready
Prompt
app request
Terminal
real PTY
Mobile
approval
Preview
app ready
Terminal first
Start in the terminal. Stay in the workspace.
Ratatosk keeps the command line as the primary surface. The app-owned workspace around it remembers which agent is running, which terminal is safe to resume, and which machine owns execution.
Full terminal
Agent state
Give every long-running task a body, name, and status.
Sprites carry attention: who needs input, who has a review artifact, who is stale, and who survived a restart.
Workspace map
Use the map when one terminal becomes many agents.
Groups, tabs, terminal panes, mobile input, and profile context share one workspace state, so project work stops drifting across windows.
Execution nodes you control
Run the same terminal workspace on your Mac or in the cloud.
Ratatosk separates the workspace from the execution node. A local node or isolated cloud workstation can hold the same repos, agents, transcripts, PTYs, and recovery rules.
Local node runs the terminal
PTYs, files, workspace metadata, readiness, and live sessions stay with the machine running Ratatosk.
Cloud node runs the same workspace
An isolated machine can host Codex, Claude, repos, and PTYs when the laptop is offline, underpowered, or packed away.
Cloud control owns access
Accounts, device sessions, public URLs, access passwords, profile memory, and entitlement checks stay behind the hosted boundary.
The hard part starts after the prompt is sent.
Ratatosk tracks which agents are waiting, which terminal is safe to resume, which transcript matters, which phone nudge needs attention, and which node owns execution.
Get the terminal workspace for agent work.
Request access to the Ratatosk Cloud lane for account, routing, profile, mobile, and workspace-access workflows.