Sign-ins
Sign the coding agents, GitHub and T3 Code in on a host, which installing them does not do.
A new host has its tools and agents installed but nobody signed in. Each sign-in runs on the host as the agent, and you complete it in your own browser.
From the overview
Under Sign-In:
| Action | Signs in |
|---|---|
| Sign in to GitHub | gh, from the github plugin |
| Sign in to Unity | The Unity CLI, from the unity plugin |
| Show who is signed in | The accounts every plugin of the host knows about |
A plugin that installs a coding agent adds its sign-in to the same group.
A sign-in opens in a panel. It prints a link: click it to open it on your machine, or right-click to copy it. Right-click a one-time code to copy it. The command line does the same in your terminal:
rookery run studio github:login
rookery run studio sign-in:statusGitHub without signing in
A fine-grained token given to the host as GH_TOKEN signs gh and git in for github.com without a browser. See Secrets.
T3 Code on another device
On a host where a plugin installed T3 Code, it asks every new browser to pair once. Use T3 from another device prints a pairing link for the published tailnet address, and the host and code for the T3 app. The code works once, within 10 minutes. T3 has to be published on the tailnet first.
rookery run studio pairKeep T3's pairing enabled and use the tailnet HTTPS address, not a loopback pairing address.
Checking by hand
On the host, as the agent:
sudo -iu agent
gh auth status
t3 service status
box exec rookery-smokeRun sudo -n true from a command T3 started, too, to check the agent's sudo as T3 sees it.
Last updated on