The best way to control Claude Code, Codex and more from any computer or phone
Mirrored from https://github.com/Camo67/t3code.git
Synced Nov 21, 03:37 UTC
| 1 | # Guest links |
| 2 | |
| 3 | A guest link lets a teammate follow one thread in their browser and ask the agent questions, with no |
| 4 | account. They see your messages and the agent's replies as they stream. Each message they send waits |
| 5 | until you send or dismiss it. |
| 6 | |
| 7 | ## Share a thread |
| 8 | |
| 9 | Guest links are a beta. Turn on **Settings → Labs → Guest links** for the machine that runs the |
| 10 | thread. They also need [T3 Connect](./remote-access.md): sign in and link that machine, because the |
| 11 | link points at its T3 Connect address. The machine must stay online while the guest uses it. |
| 12 | While the setting is off, every guest link on that machine stops working; links that have not |
| 13 | expired work again when you turn it back on. |
| 14 | |
| 15 | 1. Right-click the thread in the sidebar and choose **Share with guest**. It is also in the thread |
| 16 | menu and the command palette. In the mobile app, long-press the thread in the list. |
| 17 | 2. Copy the link and send it to one person. It works in one browser and expires after 24 hours. |
| 18 | Opening it again in that browser takes them back to the thread. |
| 19 | 3. When they send a message, it appears at the end of the thread and the sidebar shows **Request**. |
| 20 | Choose **Send** to run it as a normal turn, or **Dismiss**. Files they attached show with the |
| 21 | message, and **Send** includes them. |
| 22 | |
| 23 | Choose **Stop sharing** to end the link at once. Archiving the thread, creating a new link, or |
| 24 | unlinking the machine from T3 Connect also ends it. The mobile app can send, dismiss, and stop |
| 25 | sharing too. |
| 26 | |
| 27 | ## What the guest sees |
| 28 | |
| 29 | The guest sees the thread's recent history and everything after, in the same timeline you see, as |
| 30 | it streams: messages and their files, the agent's replies with the images they show from your |
| 31 | machine, its reasoning, plans, questions, and its work, with command output when they expand a |
| 32 | command. Their composer shows the thread's model, but they cannot change it. They do not see diffs, and they cannot act on the thread: no forking, |
| 33 | reverting, opening files on your machine, or answering the agent for you. |
| 34 | |
| 35 | Anything the agent read or printed can show, such as a value from a file. Share only threads you |
| 36 | are comfortable showing. |
| 37 | |
| 38 | ## Guest attachments |
| 39 | |
| 40 | Guests can attach images and other files to a message: use the paperclip, paste, or drop them on |
| 41 | the message box. A message holds up to 4 files and 10 MB in total. Images must be PNG, JPEG, GIF, or |
| 42 | WebP. While messages wait for you, their files can total 20 MB; the guest can attach more once you |
| 43 | send or dismiss some. |
| 44 | |
| 45 | Dismissing a message, ending the link, or archiving the thread deletes the files of messages that |
| 46 | still wait. A sent message keeps its files, like any message in the thread. |
| 47 | |
| 48 | The guest's text and files run with the thread's current permission mode once you send them. Check |
| 49 | them before you choose **Send**, as you would anything pasted from a chat. |