Skip to content
Source
Sign inSign up
Open History to see the last commit

welcome-page.md

112 lines6.2 KB

1# Welcome page
2​
3T3 Code shows a Welcome page when you open a new installation. Existing
4workspaces skip it. It shows what T3 Code found on the computer you are using,
5on one page: your agents, projects from your Claude Code, Codex, and Pi history,
6and the phone app. Only an agent is needed to start chatting.
7​
8To see the page again, go to **Settings → About → Welcome page** and select
9**Open**. Direct links, such as Settings, open normally before setup is done.
10​
11The hosted app at app.t3.codes does not open the page. With no computer connected,
12it asks you to sign in to T3 Connect, then to install T3 Code and run
13`t3 connect` on your computer. From home, it adds compatible computers linked to your account and
14opens the app. To add more computers later, use **Settings → Environments**.
15​
16If T3 Code cannot confirm the workspace during startup, it shows
17**Still connecting** instead of opening the app. Select **Reload** to try again.
18​
19If T3 Code cannot read your saved settings, it shows **Could not read settings**.
20Select **Retry** after storage becomes available. Setup does not replace
21unreadable settings with defaults.
22​
23## Agents
24​
25T3 Code lists the agents it found on the computer first, ready ones on top.
26**Add more agents** lists every other agent T3 Code supports, A to Z. When no agent
27is found, it reads **Set up an agent** and opens by itself:
28​
29- **Turn on** enables an agent that is off on this computer, including one only
30 some projects use. T3 Code then checks whether it is installed and signed in.
31- For Claude Code, **Install** or **Sign in** opens a terminal with the correct
32 command ready to run. Install uses the vendor's own installer, which keeps
33 **Update now** working in Settings.
34- For Codex, **Set up** offers sign-in with your ChatGPT account or your own
35 Codex CLI. **Use existing CLI** opens the terminal to install or sign in, and
36 **Continue with ChatGPT** stays available until Codex is signed in.
37- When T3 Code knows an installed version does not work with it, **Update** opens
38 the agent in **Settings → Providers**, which shows the version to use and updates it
39 when it can.
40- Other agents, and agents that could not load, open their page in
41 **Settings → Providers**.
42- **Browse** opens the ACP Registry for more agents.
43​
44On the desktop app, when the folder of the `t3` command is not on your `PATH`,
45**Add to PATH** adds one line to your shell's startup file.
46​
47The setup terminal uses the home directory and environment configured for the
48provider instance. Sensitive values remain redacted in Settings and
49terminal metadata while the terminal process can use them.
50​
51**Start** waits for one ready agent. Select **Start without an agent** to finish
52without one. Checked projects are still imported.
53​
54## Phone
55​
56Select **Set up** and scan the code with your phone. It opens the App Store on an
57iPhone and Google Play on Android. Then select **Sign in to T3 Connect** and allow
58this computer when T3 Code asks, so the app can reach it. Sign in to the app with
59the same account. If you are signed in but this computer is not shared yet, select
60**Set up T3 Connect**. If T3 Connect is on but the app cannot reach this computer,
61select **Check T3 Connect** to see why. The page leaves the phone out on builds
62without T3 Connect, or when your organization turns it off. You can still pair the
63app with a code from **Settings → Sharing & access**.
64​
65## Projects
66​
67T3 Code finds directories that Claude Code, Codex or Pi has used. Git repositories
68are listed first, newest activity on top. When the remote is on GitHub, the
69group shows the repository as `owner/name`. Clones with the same remote share
70one group. Directories that are not git repositories sit under "Other folders".
71​
72The page offers git repositories active within the last 30 days with at least
73three conversations, already checked. Projects already in T3 Code are not checked
74again. Uncheck the box to start without them, or
75select **Review all** to pick from everything found, with "Select all" and
76"Select none". Linked worktrees of bare repositories
77can be offered as separate projects. Conversations in other linked git worktrees
78count toward their main checkout, so a repository is offered even if you only
79worked in its worktrees. Codex scratch directories under `Documents/Codex`, and
80anything under `Downloads` are not offered.
81​
82A large or malformed history can reach the scan limit. T3 Code keeps the
83projects it found and warns when projects or conversations may be missing.
84​
85Imported projects include Claude, Codex and Pi conversations active within the last
8630 days. You can continue those conversations in T3 Code. Pi is off by default:
87open **Add more agents** and select **Turn on** next to Pi, and the page looks for
88its sessions too. Pi sessions
89are read from each enabled Pi provider's session directory, which follows
90`PI_CODING_AGENT_SESSION_DIR` and `PI_CODING_AGENT_DIR` in its environment. A
91Pi conversation imports its active branch, the one Pi reopens.
92​
93Conversation import is best effort. T3 Code keeps the first user prompt and the
94newest remaining visible user and assistant messages, with 200 messages total.
95It omits tool activity and attachments. For Codex, it omits generated setup
96context only when a canonical user event and a valid shared turn ID identify the
97same user turn. Ambiguous legacy or response-only context stays in the imported
98conversation so T3 Code does not remove user text. It reads one conversation at
99a time and skips files larger than 4 GiB. It also skips a conversation when the
100message text and metadata it keeps need more than 32 MiB of memory. Tool output
101does not count toward that limit. It skips a conversation with more than 100,000
102records every time, so opening the page again does not import it. It ignores
103malformed records and skips unreadable or unparseable conversations.
104​
105Each import attempt reads up to 100 conversation files and 4 GiB per project. To
106continue a large batch, open the Welcome page again and pick the project in
107**Review all**. Completed conversations are not imported again. You can continue
108without the remaining history.
109​
110You can start without importing. While an import runs, T3 Code stays on the
111Welcome page. If you quit, open the Welcome page again from **Settings → About**; the
112projects you started stay checked.