This branch is the T3 Turbo operator repo. It carries the complete, versioned kit for standing up the self-hosted stack: Cloudflare relay + tunnel, Clerk auth, and self-hosted Supabase Postgres — no Axiom, no APNs (Android-only operator).
| What | Where |
|---|---|
| Master runbook (bring-up order, architecture, threat model, secrets inventory) | infra/README.md |
| Rebase seam — upstream files we modify + conflict guidance | SEAM.md |
| Supabase: schema, seed, RLS, setup rules | infra/supabase/ |
| Cloudflare Tunnel configs + systemd unit | infra/cloudflared/ |
| GitHub/Cloudflare vars & secrets checklist (names only) | infra/cloudflare/CHECKLIST.md |
| Relay deploy guide (Hyperdrive, Clerk, verification) | infra/relay/DEPLOY.md |
Hard rule: no secret values in this repository — ever. Placeholders in <angle brackets>
are resolved from the operator's private vault at deploy time.
Upstream T3 Code README follows below (kept for rebase context).
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, and OpenCode. 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 and OpenCode. 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 - 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
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-codeyay -S t3code-binThis fork also builds T3 Turbo, our desktop-only downstream variant. Turbo ingests official
T3 source; it never downloads or republishes an official installer. The scheduled
T3-Turbo Nightly Sync workflow:
- checks
pingdotgg/t3code:mainand the newest official Nightly tag every three hours; - verifies that both refs move forward from the checkpoint in
.t3-turbo/upstream.json; - rebases the small Turbo commit stack in an isolated worktree;
- builds the Linux WSL native dependency and an unsigned Windows x64 installer;
- publishes the installer, blockmap, and
nightly.ymlonly in this fork; and - advances the
turbobranch only after publication succeeds.
If Git reports a conflict, the workflow leaves the current branch and release untouched, uploads a conflict report, and opens or updates a review issue. It never guesses whether our change or upstream's change should win.
The workflow file must be identical on both main and turbo. main owns the schedule, while
turbo carries the workflow across upstream rebases. Enable the pipeline with the required
repository variable:
gh variable set TURBO_NIGHTLY_ENABLED --body true --repo gfsaaser24/t3codeOptionally assign conflict issues to a GitHub account:
gh variable set TURBO_NOTIFY_USER --body gfsaaser24 --repo gfsaaser24/t3codeNo official T3 credentials or signing secrets are required for ingestion or packaging. Do not
store a personal access token as an Actions secret for this workflow. GitHub supplies its scoped
GITHUB_TOKEN to read public upstream metadata, open conflict issues, publish fork releases, and
advance the fork branch.
OpenClaw intervention alerts are optional. When used, configure
TURBO_OPENCLAW_ENABLED=true and the three repository secrets named in the
nightly inbound runbook.
The local commands below assume GitHub CLI is authenticated with gh auth login.
# Ask the workflow to check official main and Nightly source now.
gh workflow run turbo-nightly-sync.yml --ref main --repo gfsaaser24/t3code
# Inspect runs and published installers.
gh run list --workflow turbo-nightly-sync.yml --repo gfsaaser24/t3code --limit 5
gh release list --repo gfsaaser24/t3code --limit 5A manual dispatch is a source check, not an unconditional rebuild. When the recorded upstream
main commit and Nightly tag are already current, the run succeeds without producing another
installer; the workflow currently has no force-rebuild input. A changed upstream ref produces a
deterministic .turbo.N version and a new installer on the fork's
Releases page.
For the complete state model, version rules, conflict recovery, updater behavior, permissions, and troubleshooting checks, read T3 Turbo nightly inbound updates.
We 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
- Remote access from a phone or another machine
- Keeping app and server in sync
- Source control integrations
- Multiple accounts: Codex · Claude
- Linux: run T3 Code as a background service
Building from source? Start at docs/internals/overview.md.