1Password Connect on a remote server
Permissions and secrets
Lets the T3 Code server read secrets through a 1Password Connect server you already run, needing no desktop approval.
T3 Code docs: secrets 1password connect
What it’s for
Using an existing Connect deployment, for example on a home server or in Kubernetes, as the secret source for a headless T3 Code server.
T3 Code docs: secrets 1password connect
When to use it
Only if you already run Connect; otherwise a service account is simpler. Do not also set OP_SERVICE_ACCOUNT_TOKEN in the same environment.
T3 Code docs: secrets 1password connect
How to use it
Create a Connect server and an access token limited to the needed vaults, and deploy the Connect containers where the server can reach them.
T3 Code docs: secrets 1password connect
Install op on the server's machine and set OP_CONNECT_HOST and OP_CONNECT_TOKEN in its environment; for a service, add them to service.env and restart.
T3 Code docs: secrets 1password connect
In Settings → Secrets, select Add provider and enter any sign-in address such as my.1password.com.
T3 Code docs: secrets 1password connect
Check the health endpoint with curl, then test with op read, not op vault list.
T3 Code docs: secrets 1password connect
Unofficial notes. Not affiliated with Theo or t3.gg.