Your code does not go through us.
T25 runs on your machine, with no collector and no telemetry on by default. Agent CLIs send data to their own providers, on your account and under each provider’s policies.
fig. 1: where each piece of data lives
On your machine
Orchestrator, Postgres and workers
- Code, diffs and worktrees
- Agent prompts, outputs and logs
- CLI credentials
- Tasks, runs and events
At the agent provider
On your account, under its rules
- What the CLI sends to the model to work
- Retention follows each provider’s policy
With T25
By default, none of your work
- Code, prompts, logs and credentials are not collected
- The invite request asks only for contact and context
How T25 contains an agent.
One task, one worktree
No agent runs in the main checkout. Each task gets its own worktree and branch.
A Docker sandbox for whoever touches the code
Implementation and QA (dev-frontend, dev-backend, qa-frontend and qa-backend) run in a container, in the image the project declares, when the risk policy asks for sandbox: docker. The other roles run in the worktree, without a container.
No shell in between
Calls to git and the CLIs use argument lists. A branch name never becomes a command.
Diff limits
Files and lines have a limit. A runaway agent stops before the pull request.
Plan comment without free text
The plan comment on the issue only carries fields T25 builds itself: state, version and next step. Other reports on the issue, such as triage, may include analysis written by the agent.
Human merge
T25 delivers the pull request. Putting it on main stays your decision.