| 1 | # Welcome wizard |
| 2 | |
| 3 | T3 Code shows a setup flow when you open a new installation or connect to the |
| 4 | hosted app for the first time. Existing workspaces skip this flow. |
| 5 | |
| 6 | ## Connect your computers |
| 7 | |
| 8 | Select one or more computers to set up. If you opened T3 Code directly from a |
| 9 | server or the desktop app, that computer is already connected and selected. |
| 10 | It is identified by its name, which may differ from the device running your |
| 11 | browser. |
| 12 | |
| 13 | You can add more computers before continuing: |
| 14 | |
| 15 | - **T3 Connect** connects computers that are signed in to your account. |
| 16 | [Install the CLI](./install.md#command-line) and run `t3 connect` on each |
| 17 | computer you want to add, then start T3 Code or run `t3 serve` so the |
| 18 | computer stays available. |
| 19 | - **Add a computer** connects directly to a server on your network or tailnet. |
| 20 | Start the server with `t3 serve`, then run `t3 pair --tailscale` and paste |
| 21 | the pairing link. You can also run `t3 serve --host <address>` and use |
| 22 | `t3 pair` when the server is already reachable on your network. |
| 23 | |
| 24 | Saved computers and computers discovered through T3 Connect are selected by |
| 25 | default. Uncheck any you do not want to set up; this does not disconnect them. |
| 26 | Continue when your selected computers are connected. Setup checks |
| 27 | agents across the selected computers, then offers project import grouped by computer. |
| 28 | |
| 29 | If T3 Code cannot confirm the workspace during startup, the setup flow shows |
| 30 | **Still connecting** instead of opening the app. Select **Reload** to try again. |
| 31 | |
| 32 | If T3 Code cannot read your saved settings, it shows **Could not read settings**. |
| 33 | Select **Retry** after storage becomes available. Setup does not replace |
| 34 | unreadable settings with defaults. |
| 35 | |
| 36 | ## Check your agents |
| 37 | |
| 38 | T3 Code checks each selected computer for Claude Code and Codex. If an agent is |
| 39 | not installed or signed in, select its action to open a terminal with the |
| 40 | correct command ready to run. Install uses the vendor's own installer, which |
| 41 | keeps **Update now** working in Settings. Other providers can be enabled in |
| 42 | Settings. |
| 43 | |
| 44 | The setup terminal uses the home directory and environment configured for the |
| 45 | selected provider instance. Sensitive values remain redacted in Settings and |
| 46 | terminal metadata while the terminal process can use them. |
| 47 | |
| 48 | ## Import your projects |
| 49 | |
| 50 | T3 Code finds directories that Claude Code or Codex has used. Git repositories |
| 51 | are listed first, newest activity on top. When the remote is on GitHub, the |
| 52 | group shows the repository as `owner/name`. Clones with the same remote share |
| 53 | one group. Directories that are not git repositories sit under "Other folders". |
| 54 | |
| 55 | The default selection includes git repositories active within the last 30 days |
| 56 | with at least three conversations. Use the checkboxes, or "Select all" and |
| 57 | "Select none", to change the selection. Linked git worktrees, Codex scratch |
| 58 | directories under `Documents/Codex`, and anything under `Downloads` are not |
| 59 | offered. |
| 60 | |
| 61 | A large or malformed history can reach the scan limit. T3 Code keeps the |
| 62 | projects it found and warns when projects or conversations may be missing. |
| 63 | |
| 64 | Imported projects include Codex and Claude conversations active within the last |
| 65 | 30 days. You can continue those conversations in T3 Code. |
| 66 | |
| 67 | Conversation import is best effort. T3 Code keeps the first user prompt and the |
| 68 | newest remaining visible user and assistant messages, with 200 messages total. |
| 69 | It omits tool activity and attachments. For Codex, it omits generated setup |
| 70 | context only when a canonical user event and a valid shared turn ID identify the |
| 71 | same user turn. Ambiguous legacy or response-only context stays in the imported |
| 72 | conversation so T3 Code does not remove user text. It reads one conversation at |
| 73 | a time and skips files larger than 16 MiB. It ignores malformed records and skips |
| 74 | unreadable or unparseable conversations. |
| 75 | |
| 76 | Each import attempt reads up to 100 conversation files and 64 MiB per project, |
| 77 | with up to 100,000 input records. Run import again to continue a large batch. |
| 78 | Completed conversations are not imported again. You can continue without the |
| 79 | remaining history. |
| 80 | |
| 81 | You can continue without configuring agents or importing projects, or return to an earlier step |
| 82 | using the setup progress bar. Navigation pauses while an import is running. |