Which harness holds a token
A token minted through the OAuth endpoint (/oauth/token, when a harness such
as Claude Code connects) is listed with the registered name of the client that
holds it, so you can tell who can act as you. A token you made by hand shows
nothing extra.
- Settings › Tokens: under the token's name, "<client> · Signed in through
OAuth; renews itself until you delete it". The name is escaped.
GET /api/v1/tokensand MCPtokens: each token carries
oauthClient, the client's name, or null for a hand-made token.
- Terminal, sign-ins screen: the row reads
<name> · <scope> · <client>, renews itself.
It appears for every token the code exchange or a refresh minted while the client is registered. A token from before OAuth tokens were marked is listed as hand-made. "Renews itself" means the harness swaps it with its refresh token before it lapses; deleting it ends that, see OAuth refresh.
A site admin's tokens are labelled
A site admin's token acts as admin whatever scope it was made with (#596), so
every token of a site admin carries the label "acts as admin" beside its scope
(#12466): a badge in Settings › Tokens, and <name> · <scope> · acts as
admin on the terminal's sign-ins screen. The words are one constant,
ACTS_AS_ADMIN_WORDS in src/core/tokens.ts, used by both doors. Tested in
test/admin-journey.test.ts (the page) and test/tui-signins.test.ts (the
terminal).
Connect Claude Code from anywhere
Settings › Tokens, "Connect your harness", offers one command that works outside a clone, while a source repository is public on this forge (the upstream's counts):
claude plugin marketplace add <forge address>/plugins/claude-code/marketplace.json && claude plugin install forge@forge
The forge serves that manifest itself, from its configured address (never the
Host header); the plugin is fetched as plugins/claude-code of the source
repository, the one an admin names (PATCH /api/v1/admin/settings with
{"forgeRepo": "owner/name"}), else FORGE_REPO.
Run it in a shell, then sign in through /mcp in Claude Code. The same single
command shows on the terminal's screen for a token you just made (Signed in ›
m), wrapped whole; c copies it. A source that is named but private falls
back to the upstream's, so a stranger can still run it; the --plugin-dir
line, for a clone, is always shown. The card at /.well-known/mcp.json and
/llms.txt print the same command. The address is the forge's public one, the
same on the page and in the terminal, and is escaped.