DAI Documentation

• Windows 10 or 11 (x64). macOS and Linux are on the roadmap.
• At least one agent CLI installed and signed in: Claude Code, Codex or Grok. Plain shell panes work with nothing installed at all.
• For remote workspaces: an SSH-reachable POSIX server with your CLIs on its PATH (see Remote workspaces).

DAI is in early access. Join the waitlist and you'll receive the installer. Hub Stripe checkout is parked, so the waitlist is the signup path for now. After the first install, DAI keeps itself current with its built-in updater.

On first launch, DAI detects the agent CLIs available on your machine. On Windows this includes Claude Code installed as an MSIX package, even when it isn't on your PATH.

Work in DAI is organized into spaces, one per project or task stream. Create a space and its welcome screen lets you compose the first panes: dial in how many terminals from each provider, set the working directory, choose an effort level, and optionally pick where the space runs (locally or on a saved SSH location).

• Add more panes at any time, and the grid rearranges by drag and drop.
• Space cards live in the sidebar under the file tree; a Spaces overview shows everything at a glance.
• Each space remembers its panes, layout and working directories.

Every pane is a real terminal session (a PTY), not a webview or a log viewer. Switching spaces never restarts anything. Panes stay mounted; DAI only toggles their visibility. Come back an hour later and your agent is still there, mid-conversation, scrollback intact.

• Persistent sessions: pane state is stored in a local database and scrollback is replayed if the UI ever reloads.
• Idle watchdog: DAI notices when an agent goes quiet and can nudge it or notify you.
• App restarts: terminal processes don't survive quitting the app, by design. Within a run, everything persists.

Each pane runs one provider:

• Claude Code: Anthropic's agentic CLI.
• Codex: OpenAI's coding agent CLI.
• Grok: xAI's Grok Build CLI.
• Shell: a plain terminal for builds, servers, logs, anything.

In swarm mode, DAI injects a role-specific system prompt when the pane spawns, so an "architect" pane and a "reviewer" pane behave like their roles from the first token.

The sidebar file tree follows the active space, including remote spaces, where it lists the server's directory over SSH. From the tree you can create files and folders, open files in the editor dock, and drag entries where you need them:

• Drag into a CLI pane to attach the file to your prompt as a staged path reference.
• Drag a folder onto a pane to change its working directory; drop a script to run it.

The DAI Agent is one input that runs the whole cockpit. It routes what you type automatically:

• Quick questions get instant streaming answers, grounded in your repository.
• Real work gets dispatched as a coding task: you watch a live activity feed, and cancel is always one click away.

Two guarantees separate it from a chat bot:

• Verified results. Before you see a change, the agent runs your project's own test suite against it.
• Nothing lands without you. Changes only touch your files when you hit Apply.

The agent can also drive the app itself: spawn and read panes, create spaces and swarms, switch panels, toggle MCP servers, and navigate the embedded browser.

The DAI Agent is included in the Pro plan.

A swarm is a set of panes with roles, wired to a shared coordination layer:

• Task board: agents create, claim and complete tasks.
• Message bus: agents send each other messages instead of guessing at each other's state.
• Worktree isolation: every agent works on its own branch (dai/<swarm>/<role>) in its own worktree.
• Local state: the board and log are stored in DAI's local database.

DAI embeds a real browser view inside the workspace, and exposes it to your agents as first-class tools: navigate, inspect, click, type, screenshot.

• Element picker: point at anything on the page and hand a precise element reference to your prompt.
• Every Claude pane gets browser tools automatically.

A space can run on another machine. Pick "Runs on" on its welcome screen and choose a saved SSH location. Every pane in that space spawns on the server over ssh -t.

# what DAI effectively runs for a remote pane
ssh -t your-host 'cd ~/apps/api && exec "$SHELL" -l -c claude'

• The file tree lists the remote directory and can create files and folders on the server.
• Auth comes from your ~/.ssh/config.
• Requirements: a POSIX server with the agent CLIs installed on its PATH.
• Local-only affordances (MCP provisioning, attach-to-prompt, open-in-editor) are disabled for remote panes.

Add a server in the MCP panel and DAI validates it with a real JSON-RPC handshake, listing the tools it exposes. Then decide per space which servers are enabled.

• Enabled servers are provisioned to panes at spawn time, scoped to that working directory.
• Remote OAuth servers are supported: authorize in-app.
• Secrets and tokens are stored in the OS keyring, not in config files.

Everything DAI knows lives on your machine: workspaces, panes, swarm boards and message logs are rows in a local database under your user profile. Secrets live in the OS keyring. The updater talks to a static release endpoint and nothing else.

"claude not found" in a local pane

Make sure the CLI is installed and on your PATH. On Windows, Claude Code's MSIX install is detected automatically. If you've just installed it, restart DAI so detection re-runs.

"claude not found" in a remote pane

Remote panes run through a login shell on the server. Test with:

ssh your-host '"$SHELL" -l -c "which claude"'

Panes reset after restarting the app

Expected: terminal processes don't outlive the app. Within a run, switching spaces never restarts panes.

An MCP server won't enable

DAI requires a successful JSON-RPC handshake before a server can be enabled. Check the command path and environment variables in the MCP panel and retry the validation.

Do I need API keys?

No. DAI drives the official CLIs with the subscriptions you already pay for.

Can I mix providers in one space?

Yes. A space can run Claude, Codex, Grok and shell panes side by side. That's the point.

Do agents share context?

Panes are isolated sessions by default. In swarm mode, agents coordinate explicitly through the task board and message bus.

What does DAI cost?

See pricing: a 7-day trial with no card, then Pro at $39/month or Team at $49 per seat (minimum 2 seats). Prices in USD, excluding VAT. One membership covers Code, Voice, Assistant, Creator, Workspace, Business and Hub. The DAI Agent is exclusive to Pro. All plans are bring-your-own-subscription. No à-la-carte apps.

How do I get a build?

Join the waitlist. Early-access installers go out in batches.