@devries-cameron20 / t3code-1 / commits / b46abbf3de
Fork 0

The best way to control Claude Code, Codex and more from any computer or phone

docs(user): explain secret providers and secret requests (#31654)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Julius Marminge committed Nov 5, 2026 at 15:30 UTC b46abbf3deb39020a86faa9479dd1d022711d3f6
2 files changed +59
docs/README.md
+1
@@ -17,6 +17,7 @@
17 - [Use T3 Code as your default browser](./user/default-browser.md)
18 - [Devices](./user/devices.md)
19 - [Usage and limits](./user/usage.md)
20 +- [Secrets](./user/secrets.md)
21 - [Product usage data](./user/telemetry.md)
22 - [Remote access](./user/remote-access.md)
23 - [Guest links](./user/guest-links.md)
docs/user/secrets.md new
+58
@@ -0,0 +1,58 @@
1 +# Secrets
2 +
3 +T3 Code can read credentials from a secret provider, so the credential stays in your password
4 +manager and T3 Code saves only a reference to it. Agents can also ask you for a secret in a
5 +private card instead of in the chat.
6 +
7 +The Secrets settings page is in preview and is not in every build yet. Secret requests from agents
8 +work everywhere.
9 +
10 +## Secret providers
11 +
12 +1Password is the supported provider. T3 Code reads secrets with the
13 +[1Password CLI](https://developer.1password.com/docs/cli/) (`op`), so `op` must be installed and
14 +signed in on the machine that runs the T3 Code server. When you use T3 Code on another machine or
15 +from your phone, that is the remote machine, not the device in front of you.
16 +
17 +To add one, open **Settings → Secrets**, select **Add provider**, and enter a name and the
18 +1Password account: the shorthand, sign-in address (without `https://`), or ID that
19 +`op account list` shows. Secret providers belong to the environment you are connected to. Each
20 +environment keeps its own list.
21 +
22 +## Use a secret reference
23 +
24 +Credential fields in Settings, such as provider environment variables and credentials, source
25 +control tokens, usage limit keys, and device host tokens, show a source picker next to the field.
26 +Pick **Value** to save the credential itself, or pick a secret provider and enter a reference such
27 +as `op://vault/item/field`. Copy the reference from 1Password with **Copy Secret Reference**.
28 +
29 +T3 Code reads the secret when it needs it, for example when a provider starts. Change the
30 +credential in 1Password and refresh to use the new value.
31 +
32 +## When a secret cannot be read
33 +
34 +If 1Password is locked or signed out, the provider or feature that needs the secret shows an error
35 +naming the secret provider. Unlock 1Password on the server's machine, then select **Refresh** in
36 +**Settings → Providers**. T3 Code never replaces a saved credential it cannot read with another
37 +login.
38 +
39 +## Remove a secret provider
40 +
41 +When you remove a secret provider in **Settings → Secrets**, T3 Code lists the fields that read
42 +from it. Removing it clears those fields, so set them again before you need them. The secrets in
43 +1Password are not touched.
44 +
45 +## When an agent asks for a secret
46 +
47 +An agent that needs a token or password shows a secret request card in the thread instead of asking
48 +you to paste it into the chat. Type or paste the value and select **Save securely**, or select
49 +**Decline**. You can answer from web, desktop, or mobile.
50 +
51 +If the environment has a secret provider, the card also lets you pick it and enter a reference
52 +instead of the value. T3 Code reads the secret once, when you answer. If 1Password is locked, the
53 +card says so and the request stays open: unlock it and try again, or enter the value.
54 +
55 +The value never appears in the conversation. Most requests keep it from the agent too: T3 Code
56 +passes it to the tool that needs it. When an agent has to run a command with the value, the card
57 +says so instead: the value goes into a private file that the agent's commands can read for about 24
58 +hours.