This repository is the active Scient Desktop application and the sole source of current desktop releases. It preserves the official T3 history while keeping Scient-owned product behavior behind explicit seams. Release machinery does not itself authorize publication: every release still requires an exact-tree promotion, green source CI, native packaging and signing proof, and an explicit publishing run.
Production packages use the canonical Scient installation identity. Existing
installations keep their scient-next data directory as a compatibility value;
the directory name is not current product branding and must not be changed by a
repository rename. Development builds remain independently named and isolated.
The exact donor base, safety envelope, verification, limitations, and rollback are recorded in the D4 bootstrap record. Contributor boundaries are in AGENTS.md, and the continuing T3 relationship is in UPSTREAM.md.
Maintainers can run the isolated Scient (Dev) application with
pnpm dev:app. The canonical installation, lifecycle, feature-worktree, and
recovery procedure is the
local dev app runbook. This development app
is never a publication source. Its identity, state, and protocol remain
separate from production.
Scient owns a versioned SQLite migration runner
(apps/server/src/orchestration/scient-fork/scientMigrator.ts). It runs four
ordered, transactional migrations for Scient's active fork lineage and
normalizes legacy provider modes to transcript-bootstrap. Its ledger is the
separate scient_schema_migrations table; the inherited T3
effect_sql_migrations ledger and numbering are never modified.
Existing databases remain compatible: legacy applied_at ledger timestamps are
reconciled into created_at without losing IDs, names, or timestamps, and
physical compatibility columns remain queryable with their data. Legacy
lineage rows are normalized in place with safe defaults and fail-closed
validation. Migration 4 is an additive compatibility repair for development
databases that already recorded migration 3: it upgrades the quarantine
evidence schema and removes decoder-invalid recovery rows by SQLite row ID,
including rows with null or blank thread IDs. Valid lineage remains active,
and pending, recovery, terminal state, restart, and retry behavior is
preserved. The finalized persistence design and evidence are documented in
the Scient fork divergence record.
Focused validation for this persistence work:
pnpm exec vp test run \
apps/server/src/orchestration/scient-fork/schema.test.ts \
apps/server/src/orchestration/scient-fork/crossArea.test.ts \
apps/server/src/orchestration/scient-fork/crossAreaPR15.test.ts
pnpm exec vp fmt --check
pnpm exec vp lint --report-unused-disable-directives
pnpm run typecheck
git diff --checkThe remainder of this README is inherited T3 product documentation. It remains useful for understanding the host platform but does not describe Scient's current public product or release status.
T3 Code is an "agent harness control surface". It enables control of the agents on your machine with a best-in-class mobile app (iOS, Android), web app and Electron-based desktop app.
Works with your subscriptions on Claude Code, Codex, Cursor, Grok Build, OpenCode, and Google Antigravity. If they're set up on your computer, T3 Code can control them.
Nothing. We built T3 Code because we wanted the best possible development experience with agents. We were inspired by existing solutions like the Codex desktop app, Conductor, Claude Desktop and Cursor Glass, but none met our bar.
We wanted something performant, remote-ready, and truly open. If we ever go the wrong direction, we want you to have everything you need to fork and build the editor that you want.
Warning
T3 Code currently supports Codex, Claude, Cursor, Grok Build, OpenCode, and Antigravity. Install and authenticate at least one provider before use:
- Codex: install Codex CLI and run
codex login - Claude: install Claude Code and run
claude auth login --claudeai - Cursor: install Cursor CLI and run
agent login - Grok Build: install Grok Build CLI and run
grok login - OpenCode: install OpenCode and run
opencode auth login - Antigravity: enable it in Settings, then use Install Antigravity and Sign in with Google. No CLI is required.
The easiest way to test T3 Code is to run the server in your terminal (requires Node.js 22.16+, 23.11+, or 24.10+):
npx t3@latestThis will launch T3 Code's backend on your machine as well as the local web app to control your agents.
Tip: Use npx t3@latest --help for the full CLI reference.
Install the latest version of the desktop app from GitHub Releases, or from your favorite package registry:
winget install T3Tools.T3Codebrew install --cask t3-codeWe are very very early in this project. Expect bugs.
We are (mostly) not accepting contributions yet. Small fixes may be considered. Big features will not be.
Full docs live in docs/. There's no docs site yet.
- Install and first run
- Permission modes
- Keyboard shortcuts
- Project settings
- Remote access from a phone or another machine
- Keeping app and server in sync
- Source control integrations
- Multiple accounts: Codex · Claude
- Run T3 Code as a background service
Building from source? Start at docs/internals/overview.md.
T3 Code uses Vite+ so you'll need to install the global vp command-line tool.
curl -fsSL https://vite.plus | bashirm https://vite.plus/ps1 | iexCheckout their getting started guide for more information: https://viteplus.dev/guide/
vp iRead CONTRIBUTING.md before opening an issue or PR.
Need support? Join the Discord.