t3-code

T3 Code

Manage T3 Code without tying the setup to one machine, package source, repository layout, or private network.

Start with the surface

Identify the failing surface before changing anything:

1. Desktop application state and launch method.
2. T3 server state under the selected base directory.
3. Project registration, title, workspace root, or favicon.
4. Headless server process or user service.
5. Private remote access through Tailscale.
6. Update source for the desktop application and CLI.
7. Multi-machine topology, saved environments, pairing, or tunnel fallback.

Record the installed version and supported flags first:

t3 --version
t3 project --help
t3 serve --help

Nightly flags and storage details can change. Prefer the installed CLI help over copied commands.

Inspect before changing

• Find the actual executable with command -v t3.
• Identify the configured base directory. The usual default is ~/.t3, but --base-dir or T3CODE_HOME may override it.
• Determine how the desktop application was installed: package manager, AppImage, source checkout, or another channel.
• Determine whether the server runs interactively, through a wrapper, or as a user service.
• Read references/multi-machine.md before setting up one desktop to manage projects on other hosts.
• Read references/windows-remote.md when a remote T3 backend runs on Windows.
• Read references/project-state.md before changing project records or icons.
• Read references/remote-tailscale.md before exposing a headless server.
• Read references/updates-and-launchers.md before installing T3 or changing release channels, updates, wrappers, or services.

Prefer supported commands

Use T3 project commands before considering direct database edits:

t3 project add --base-dir "$HOME/.t3" --title "Project (Workstation)" /path/to/repository
t3 project rename --base-dir "$HOME/.t3" /path/to/repository "Project (Workstation)"
t3 project remove --base-dir "$HOME/.t3" /path/to/repository