This fork runs the T3 Code web client and one central server, with conversation state in SQLite on persistent storage. Provider processes, repository operations, terminals, and browser previews run in Kubernetes Agent Sandbox. Agent-runtime and Hatchet manage execution lifecycle.
New top-level threads receive independent workspaces. Delegated subagents share their parent's workspace while keeping separate conversations. Allocation and recovery happen behind the normal thread controls.
Provider executables and versions belong to the execution image. Settings → Providers retains account authentication and model selection. This fork ships the web application; desktop and native mobile applications are removed.
Build the fork and agent-runtime together using the image build guide, then follow the deployment guide. The deployment uses an existing Hatchet installation and Kubernetes cluster with the Agent Sandbox controller.
The images separate the central web service, execution worker, and lifecycle service. Keep central SQLite on its own persistent volume and run one central server replica. Worker workspaces use separate retained volumes.
For source changes, install the repository's pinned dependencies with pnpm install --frozen-lockfile. See development and releasing deployment images for the build workflow.
- Open the application and start a conversation
- Permission modes
- Keyboard shortcuts
- Project settings
- Appearance preferences
- Browser access and pairing
- Connect outside agents over MCP
- Updates
- Source control integrations
- Provider accounts: Codex, Claude
This fork is based on pingdotgg/t3code. Read CONTRIBUTING.md before contributing.