Skip to content
boldsoftwarePublic

About

use exe.dev in T3 Code

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

2 Commits

Folders and files

Repository files navigation

t3exe

Run T3 Code agents on exe.dev VMs.

t3exe is an MCP server (and CLI) for T3 Code. An orchestrator thread calls exe_vm_create; t3exe creates a VM, installs the same T3 Code version on it, clones your repository, and links the VM to your T3 Code as an environment. The orchestrator then sends work there with delegate_task, as it would to any linked machine. When the VM's threads go quiet, t3exe deletes or pauses it.

It uses T3 Code's Linked environments and needs no change to T3 Code.

your T3 Code ── exe_vm_create ──▶ t3exe ── exe.dev API ──▶ new VM
                                    │                       ├ T3 Code (same version), t3 serve on :8000
                                    │                       ├ Claude Code, Codex → exe.dev LLM integration
                                    │                       └ git clone, t3 project add, pairing code
                                    └── t3 environment link https://<vm>.exe.xyz
your T3 Code ── delegate_task(target.environmentId) ──▶ a thread on the VM

Setup

You need Node 22.18 or later, T3 Code 0.1.10 or later, and an exe.dev account whose SSH key is on this machine.

  1. In T3 Code, turn on Settings → Labs → Linked environments.
  2. Create an exe.dev API key for t3exe:
    npx -y @exedev/t3exe login
    This runs ssh exe.dev ssh-key generate-api-key and saves the key to ~/.t3exe/token. The key only works on VMs tagged t3exe, for the commands t3exe runs, and expires in 90 days (--exp).
  3. Add the MCP server to the agent your T3 Code runs, on the machine with the T3 Code server:
    claude mcp add t3exe --scope user -- npx -y @exedev/t3exe
    codex mcp add t3exe -- npx -y @exedev/t3exe
  4. Ask a thread: "Start an exe VM and have it fix the failing tests there."

Tools

Tool
exe_vm_create Create and link a VM. Returns environmentId and projectId for delegate_task.
exe_vm_list The VMs t3exe manages, their link status, and when cleanup acts.
exe_vm_destroy Unlink and delete a VM.
exe_vm_pause, exe_vm_resume Pause a VM (memory to disk, no CPU or RAM in use) and bring it back.
exe_vm_configure Change a VM's cleanup: idleMinutes, onIdle, ttlMinutes, keepAlive.

The same operations are on the command line: t3exe create, ls, rm, pause, resume, set, reap (t3exe --help). npm install -g @exedev/t3exe puts t3exe on your PATH; otherwise use npx -y @exedev/t3exe.

Cleanup

exe.dev VMs run until deleted, so t3exe cleans up after itself. Every minute it asks each VM's T3 Code whether a thread there is busy. A VM with no busy thread for idleMinutes (default 15) is deleted, or paused if onIdle is pause. Every VM is deleted ttlMinutes (default 480) after it was created, unless it has keepAlive.

Cleanup runs while an MCP server runs. The VMs are recorded in ~/.t3exe/vms.json, so the next MCP server picks them up; t3exe reap from cron does the same without one.

Models on the VM

If the VM can reach exe.dev's LLM integration, t3exe points Claude Code and Codex at it, so no API key or login is stored on the VM. To use your own credentials instead, name them in T3EXE_FORWARD_ENV, e.g. T3EXE_FORWARD_ENV=ANTHROPIC_API_KEY,OPENAI_API_KEY. Their values are sent through the exe.dev API and stored in a 0600 file that the VM's T3 Code service reads.

Configuration

Variable Default
EXE_API_TOKEN ~/.t3exe/token exe.dev API key
EXE_BASE_URL https://exe.dev exe.dev API, or an exe.dev integration URL
EXE_SSH_HOST exe.dev for t3exe login
T3EXE_TAG t3exe tag on every VM; the key from t3exe login is scoped to it
T3EXE_T3 t3 the local T3 Code CLI
T3EXE_T3_BASE_DIR T3 Code's the local T3 Code data directory
T3EXE_FORWARD_ENV local variables to copy to the VM's T3 Code
T3EXE_HOME ~/.t3exe t3exe's own files

Security

  • The VM's T3 Code is public at https://<vm>.exe.xyz, since a T3 Code link cannot sign in to exe.dev's proxy. T3 Code's own authentication protects it: t3exe links with a single-use pairing code that expires in five minutes and carries only the scopes the chosen access level needs.
  • access (default full-access) is the broadest mode your agents may run with on the VM. The VM is a throwaway machine; your local files are not on it.
  • A private repository needs git credentials on the VM, e.g. an exe.dev GitHub integration.

Limits

  • delegate_task to a linked environment does not support isolation: "worktree".
  • t3exe installs the local T3 Code's version on each VM; both ends must match.

License

MIT

About

use exe.dev in T3 Code

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages