LOCAL-FIRST CODING AGENT

The coding agent that stays in your terminal—and in your control.

Cloud TUI understands the project you opened, carries useful context forward, and coordinates real implementation work without treating your workspace like a black box.

Run cloud-tui ↓Explore the workflow ↓

LOCALworkspace sessions

HUMANapproval checkpoints

GITworktree coordination

LOCAL CONTEXT ✦PARALLEL WORKTREES ✦HUMAN CHECKPOINTS ✦DURABLE SESSIONS ✦LOCAL CONTEXT ✦PARALLEL WORKTREES ✦

WHY CLOUD TUI

Built for long-running work, not one-off answers.

⌁

Context that earns its place

Long conversations stay useful without dragging every historical file rewrite into the next turn.

⌘

Parallel by design

Split independent work across focused sub-agents while the main agent keeps the implementation moving.

⊹

Guardrails in the flow

Risky actions and material decisions pause for your answer instead of becoming silent side effects.

◫

Sessions that remember

Return to a project and pick up the conversation where you left it, locally.

CONTEXT ENGINE

Keep the signal. Leave the bulk behind.

As a run grows, Cloud TUI archives oversized historical file updates as local context artifacts and replaces them with lightweight references. When old detail matters again, the agent can retrieve it on demand.

After repeated compaction, a durable session summary carries forward the decisions, constraints, implementation state, and next steps that still matter.

Large edits → local artifactsDetails → on demandLong run → summary

CONTEXT PRESSUREFRESH

freshworkinglong-running

USER

Build settings navigation with keyboard support.

MODEL

updateFile · SettingsPanel.tsx 4.8 KB

MODEL

updateFile · focus-manager.ts 8.2 KB

◇

context artifact settings-history-02.txt

∼

Durable summary
Keyboard navigation added; focus wrapping remains to verify.

Slide to see how a session gets lighter without losing its useful history.

PARALLEL EXECUTION

Give independent work its own branch of reality.

Delegate focused tasks into isolated Git worktrees, checkpoint before integration, and keep merge status visible.

worktree coordinator

main●

checkpoint: settings foundation

AGENT 01running

Settings UI

worktree / settings-ui

82% · visual components

AGENT 02ready

Keyboard behavior

worktree / focus-behavior

100% · awaiting merge

↘

Merge readycheckpoint before integration

Focused delegated promptsOne isolated Git worktree per sub-agentConflict visibility

ACTIVE WORKSPACE~/projects/acme-app

⌄ acme-app opened directory

├─ src/

│ ├─ settings/

│ └─ app.tsx

├─ package.json

└─ README.md

~/Documents/private-notesoutside active workspace

File tools and shell commands resolve inside the directory you opened.

WORKSPACE SCOPE

Open a directory. Give the agent that directory—not your machine.

Cloud TUI resolves the workspace from the directory where you launch it. File tools and shell commands are scoped to that project workspace, and commands that target a working directory outside it are rejected.

Workspace-scoped guardrails, not an operating-system sandbox.

HUMAN CHECKPOINTS

The agent asks when the decision belongs to you.

Approval-gated operations wait for a real answer. Missing product decisions become structured questions, not assumptions.

PERMISSION REQUESTAWAITING INPUT

Delete `legacy-settings.ts`?

Reason: removes a project file from the active workspace.

The command remains paused until you decide.

DECISION REQUESTQUESTION 1 / 2

Which authentication flow should the dashboard use?

Choose an answer to continue the focused implementation.

VISIBLE EXECUTION

Turn a vague request into work you can follow.

For implementation work, Cloud TUI can form a short outcome-focused task plan, surface it in the conversation, and mark progress as each meaningful step completes.

IMPLEMENTATION PLANSettings navigation

2 / 4

✓Inspect the existing settings architecture
✓Create accessible settings navigation
◌Add keyboard focus behavior
○Verify the updated interaction flow

◆

Working on keyboard focus behavior…

LOCAL SESSION MEMORY

Come back to the codebase, not a blank chat.

Each canonical workspace has a stable identity. Open a saved local conversation with /session, or begin clean with /new.

› /sessionsaved local sessions for ~/projects/acme-app

↑↓ navigate · ENTER select · ESC cancel

YOUR CODEBASE. YOUR TERMINAL. YOUR FINAL SAY.

Less context switching.
More intentional shipping.

Bring agentic implementation work into the place developers already reason about software. Preserve useful context, make parallel work legible, and stop for the decisions only a person should make.

cloud-tui

Run it from the project directory you want it to use.