Ravi

t3code

t3code

t3code is a lightweight web and desktop GUI for running coding agents — Codex-first, with Claude Code support in active development. Built by Theo’s ping.gg team (T3 Stack), it launched in March 2026 and reached v0.0.11 within a week, driven by massive open-source momentum (1,000+ PRs). Available via npx t3 or as a downloadable Electron app for macOS, Windows, and Linux.

GitHub: https://github.com/pingdotgg/t3code

How t3code Works

t3code runs a local Node.js server with WebSockets wrapping the Codex CLI, streaming output to a React frontend. Key features:

  • Per-project threads — each thread is an isolated Codex (or Claude Code) session
  • Plan mode — scoped task execution with agent-generated plans before editing
  • Git worktree support — run multiple agents in parallel across the same repo
  • Integrated diff viewer — live streaming of tool call timelines and file diffs
  • GitHub PR creation and push — agents commit, push, and open PRs directly
  • Thread env mode — per-session environment variable isolation, already architecting toward credential isolation

Developers point t3code at a project directory, spawn agent threads, and let agents read code, propose a plan, execute edits, commit, and push PRs — all streamed live to the UI.

Where Ravi Fits

Per-thread credential injection

t3code’s thread env mode is a direct Ravi integration point. Instead of storing API keys in plaintext .env files (which risk ending up in git history), t3code can query Ravi’s secrets vault at thread spawn time and inject credentials as env vars directly into the Codex process.

Thread ends — secrets stay in Ravi. No credential sprawl across worktrees, no secrets committed by accident, no .env.local files that persist after the session closes.

Autonomous service signups mid-task

Codex agents building full-stack apps often need to register for external services during execution — Vercel, Supabase, Stripe, npm orgs. Without Ravi, this either blocks the agent (waiting for a human to create an account) or exposes the developer’s personal contact information.

Ravi’s provisioned email and phone enable agents to sign up for services autonomously, get verification codes, and keep moving — without touching the developer’s personal identity.

Per-project agent git identity

t3code creates PRs and pushes commits. Ravi can supply a per-project agent email (e.g. project-alpha@ravi.app) for commit attribution. This gives you traceable autonomous commits that don’t pollute a human’s GitHub account and make the agent’s work auditable at the project level.

PR review loop closure

t3code agents create PRs that receive review comments asynchronously. Ravi’s email inbox can receive GitHub notifications and route them back to the correct agent thread, closing the review cycle without human intervention. The agent reads the review, makes changes, and pushes — without anyone waiting at a keyboard.

Integration Pattern

The recommended integration uses Ravi’s MCP server with t3code’s thread env mode.

When t3code spawns a thread, it queries the Ravi MCP server for the project’s associated secrets and injects them as env vars into the Codex process. This maps directly to t3code’s existing architecture — the MCP plugin pattern already demonstrates the approach, and a t3code-specific adapter is a small lift.

# Install the Ravi MCP server
npm install @ravi/mcp-server

# Configure t3code to use Ravi for thread env injection
# In your t3code project config:
{
  "envProvider": "ravi-mcp",
  "raviProjectId": "your-project-id"
}

At thread spawn, t3code fetches the project’s secrets from Ravi and injects them as isolated env vars. When the thread exits, nothing persists locally.

Why This Matters

t3code has the highest contributor velocity of any coding agent orchestrator in its category. Open source, Theo’s audience, rapidly maturing, and already architecting toward credential isolation in its thread env mode. The integration surface is clean and the use cases are immediate:

  • Agents that can actually deploy things (not just write code)
  • Credentials that live in Ravi, not in worktree .env files
  • Commits attributed to an agent identity, not a human’s email
  • PR review cycles that close without human intervention

t3code is a high-priority integration target for Ravi because it converts coding agents from “writes code” to “ships software.”