Docs /

What your agents can do

Every pane is automatically connected to the app over MCP for exactly as long as it lives — nothing to configure for Claude Code, Codex and Qwen Code, which TAO CODING enrolls automatically; other MCP-capable CLIs can be pointed at the per-pane URL by hand (the Meeting Room panel shows the hint). Enrolled agents can drive TAO CODING themselves: open a web preview beside their own pane, spawn / list / remove worktrees to hand tasks to fresh parallel agents (removal refuses uncommitted changes), and use the Meeting Room — list peers, message them in probe or execute mode, read their inbox and reply, wait for a peer to need input or finish (wait_peer) and peek at what its screen shows (read_peer). An execute hand-off to a peer that is sitting on a prompt is refused until that prompt is answered — the sender is told to wait first.

Agents can also use the project's database connections from the Database tab: list them, read the schema (tables, columns, keys, indexes) and run any SQL — reads and writes alike, so treat a production connection with care. Each agent only sees the connections of the project its pane was started in, and every statement it runs appears in the tab's Activity list.

Meeting Room abilities only work for panes you dragged into a room, worktree abilities only in workspaces with isolation enabled — and removing a pane from a room revokes its access instantly.