Compare · As of November 2026

Scape vs T3 Code

T3 Code calls itself the open-source control plane for coding agents.^[1] Here is how it compares with Scape, with a source for every claim about T3 Code.

Feature	Scape	T3 Code
Agents
Agents	Claude Code, Codex, Copilot, Cursor, OpenCode, pi, omp and Kimi Code, on your own subscriptions.	Codex, Claude Code, Cursor, Grok Build, OpenCode and Antigravity.^[2]
Manager agent (Argus)	Argus reads your mission, starts child agents in their own worktrees, checks on them, and keeps a log table. You choose which agent and model its children run on, and can restart it on another agent without losing them.	No.
Agent rooms	Chat rooms where agents and people work one problem together, such as Claude and Codex debating an approach.	No.
Messages between sessions	One agent can message or direct another session.	Agents connected to its MCP server, or scripts using the t3 thread command, can start and message threads.^[3]
Agent review	Adversarial review: a second agent reviews the first one's diff (/scape-codex-review ships with Scape).	No.
Watchdogs	Supervisors that spot stuck sessions and auto-answer questions and permission gates (Claude Code).	Permission modes include Auto, which uses the provider's own automatic review to approve routine actions, and Full access, which skips approval prompts.^[4]
Automation
Playbooks	Step-by-step automations that chain shell commands, agent prompts, HTTP calls and Scape tools. Lock one and it runs as a fixed script.	No.
Scheduler	A per-project calendar that runs playbooks and messages Argus, once or daily, weekly or monthly, while Scape is open.	Scheduled tasks that run an agent on a fixed schedule or once at a set time, on a chosen environment.^[5]
Triggers	Run a playbook or prompt Argus when a webhook arrives, an integration record changes, a table query matches, or a calendar event happens. You arm each one.	A scheduled task can run on a webhook, for example a GitHub pull request or a failed CI job. A public URL needs a T3 Connect tunnel.^[5]
Working with people
Flight Plans	One shared, end-to-end encrypted plan for any number of people and their agents. Every open question is a thread; answers land in the doc as decisions and tasks, and you can hand a task straight to an agent. Share it by link and approve each person who asks to join.	No.
Encrypted chat	End-to-end encrypted group and one-to-one rooms. Messages are never stored on a server.	No.
Sharing	Drag notes, playbooks and tables into an encrypted chat to share them.	Guest links (beta) let a teammate follow one thread in their browser and send messages you approve before they reach the agent.^[6]
Workspace
Notes	Rich-text notes with version history, embedded charts and full-text search, synced through your iCloud.	No.
Tables	SQLite-backed tables your agents and playbooks read and write, viewed as a table, kanban or gantt.	No.
Charts	Bar, line, area, scatter, pie and KPI charts built from your tables, embeddable in notes.	No.
Custom Apps	Small apps built from a JSON spec, kept in your project.	No.
Integrations	Jira, GitHub, Slack, Notion, Linear, ServiceNow, Bugsnag, Datadog, or any HTTP source, in your sidebar.	Source control integrations with GitHub, GitLab, Forgejo, Gitea, Bitbucket, Azure DevOps and GitCafe for repos, pull requests and reviews.^[7]
Dev tools
Worktrees	A git worktree per session, with a post-create hook you set per repo or globally.	Each thread writes to its own branch.^[1]
Code editor	Monaco, with 60+ languages, a diff view, Vim mode and LSP.	No.
Browser	A built-in browser your agents can drive: screenshots, clicks, forms and scraping.	Built-in browser tabs shared with agents. You can take control of an agent's tab and hand it back.^[8]
Dev servers	A live browser preview paired with each server. Cmd+click jumps to the source, and each worktree gets its own port.	Lists local servers a thread's terminals or agent started; select one to open it in the browser panel.^[9]
Spectator mode	Every file an agent edits opens live in the editor, so you can follow along.	No.
The basics
Status	In active development.	Latest release v0.1.7 on 2026-11-04, with nightly builds the same day.^[10]
Where agents run	On your Mac. Claude Code sessions can also run on a saved SSH host. No hosted agents.	A local server that runs in the background, with remote access. No hosted agents.^[2]
Platform	macOS. Claude Code sessions can also be driven from the Claude mobile app through Remote Control, opt-in per project. There is no Scape mobile app yet.	Desktop on macOS, Windows and Linux, plus web, iOS, Android and a CLI.^[2]
Price	14-day free trial, no account or card. Then Pro at $9.99 a month or $99 a year; you bring your own agent subscriptions.	Free. Its README says nothing is for sale.^[2]
Open source	No.	Yes, MIT.^[2]

Agents

Scape: Claude Code, Codex, Copilot, Cursor, OpenCode, pi, omp and Kimi Code, on your own subscriptions.

T3 Code: Codex, Claude Code, Cursor, Grok Build, OpenCode and Antigravity.^[2]

Manager agent (Argus)

Scape: Argus reads your mission, starts child agents in their own worktrees, checks on them, and keeps a log table. You choose which agent and model its children run on, and can restart it on another agent without losing them.

T3 Code: No.

Agent rooms

Scape: Chat rooms where agents and people work one problem together, such as Claude and Codex debating an approach.

T3 Code: No.

Messages between sessions

Scape: One agent can message or direct another session.

T3 Code: Agents connected to its MCP server, or scripts using the t3 thread command, can start and message threads.^[3]

Agent review

Scape: Adversarial review: a second agent reviews the first one's diff (/scape-codex-review ships with Scape).

T3 Code: No.

Watchdogs

Scape: Supervisors that spot stuck sessions and auto-answer questions and permission gates (Claude Code).

T3 Code: Permission modes include Auto, which uses the provider's own automatic review to approve routine actions, and Full access, which skips approval prompts.^[4]

Automation

Playbooks

Scape: Step-by-step automations that chain shell commands, agent prompts, HTTP calls and Scape tools. Lock one and it runs as a fixed script.

T3 Code: No.

Scheduler

Scape: A per-project calendar that runs playbooks and messages Argus, once or daily, weekly or monthly, while Scape is open.

T3 Code: Scheduled tasks that run an agent on a fixed schedule or once at a set time, on a chosen environment.^[5]

Triggers

Scape: Run a playbook or prompt Argus when a webhook arrives, an integration record changes, a table query matches, or a calendar event happens. You arm each one.

T3 Code: A scheduled task can run on a webhook, for example a GitHub pull request or a failed CI job. A public URL needs a T3 Connect tunnel.^[5]

Working with people

Flight Plans

Scape: One shared, end-to-end encrypted plan for any number of people and their agents. Every open question is a thread; answers land in the doc as decisions and tasks, and you can hand a task straight to an agent. Share it by link and approve each person who asks to join.

T3 Code: No.

Encrypted chat

Scape: End-to-end encrypted group and one-to-one rooms. Messages are never stored on a server.

T3 Code: No.

Sharing

Scape: Drag notes, playbooks and tables into an encrypted chat to share them.

T3 Code: Guest links (beta) let a teammate follow one thread in their browser and send messages you approve before they reach the agent.^[6]

Workspace

Notes

Scape: Rich-text notes with version history, embedded charts and full-text search, synced through your iCloud.

T3 Code: No.

Tables

Scape: SQLite-backed tables your agents and playbooks read and write, viewed as a table, kanban or gantt.

T3 Code: No.

Charts

Scape: Bar, line, area, scatter, pie and KPI charts built from your tables, embeddable in notes.

T3 Code: No.

Custom Apps

Scape: Small apps built from a JSON spec, kept in your project.

T3 Code: No.

Integrations

Scape: Jira, GitHub, Slack, Notion, Linear, ServiceNow, Bugsnag, Datadog, or any HTTP source, in your sidebar.

T3 Code: Source control integrations with GitHub, GitLab, Forgejo, Gitea, Bitbucket, Azure DevOps and GitCafe for repos, pull requests and reviews.^[7]

Dev tools

Worktrees

Scape: A git worktree per session, with a post-create hook you set per repo or globally.

T3 Code: Each thread writes to its own branch.^[1]

Code editor

Scape: Monaco, with 60+ languages, a diff view, Vim mode and LSP.

T3 Code: No.

Browser

Scape: A built-in browser your agents can drive: screenshots, clicks, forms and scraping.

T3 Code: Built-in browser tabs shared with agents. You can take control of an agent's tab and hand it back.^[8]

Dev servers

Scape: A live browser preview paired with each server. Cmd+click jumps to the source, and each worktree gets its own port.

T3 Code: Lists local servers a thread's terminals or agent started; select one to open it in the browser panel.^[9]

Spectator mode

Scape: Every file an agent edits opens live in the editor, so you can follow along.

T3 Code: No.

The basics

Status

Scape: In active development.

T3 Code: Latest release v0.1.7 on 2026-11-04, with nightly builds the same day.^[10]

Where agents run

Scape: On your Mac. Claude Code sessions can also run on a saved SSH host. No hosted agents.

T3 Code: A local server that runs in the background, with remote access. No hosted agents.^[2]

Platform

Scape: macOS. Claude Code sessions can also be driven from the Claude mobile app through Remote Control, opt-in per project. There is no Scape mobile app yet.

T3 Code: Desktop on macOS, Windows and Linux, plus web, iOS, Android and a CLI.^[2]

Price

Scape: 14-day free trial, no account or card. Then Pro at $9.99 a month or $99 a year; you bring your own agent subscriptions.

T3 Code: Free. Its README says nothing is for sale.^[2]

Open source

Scape: No.

T3 Code: Yes, MIT.^[2]

“No” means it isn’t in T3 Code’s app or docs: we checked their own site, docs, changelog and repo on 2026-11-04, and only count a feature that’s built in and does the same job. If that’s changed, tell us and we’ll update the page.

Why people pick Scape

Hand an Argus the whole job. Give it the goal and your guardrails. It starts your agents with the routine permissions already granted, checks on them, and only brings you the decisions that are yours to make.
Solve the problem in front of you. Ask your agents for a Custom App, a playbook or a table that does the job: a morning incident triage, a launch tracker that refreshes itself on a schedule, a report that lands in your notes. Code is only part of the work.
Let your agents talk to each other. Put Claude and Codex in one room to argue out a fix while you read along, or have one session hand work to another. Any agent, any model, on the subscriptions you already pay for.
Work with your team, privately. Bring your whole team and everyone's agents into a Flight Plan. Each open question is a thread, the answers land in the doc as decisions and tasks, and a task can go straight to an agent. Talk in end-to-end encrypted rooms: messages aren't stored on a server, and you can run the relay yourself.
Own your AI setup. Your apps, playbooks and tables live on your Mac, and your notes sync through your own iCloud. Switch the agent or model underneath them whenever you like, and everything you built keeps working.

Where T3 Code is stronger

Free and open source.^[2]
Web, iOS and Android apps.^[2]

Sources

Facts about T3 Code were checked on 2026-11-04 and may have changed since. Something wrong? Email contact@scape.work and we’ll fix it.