Sign in #
On this page
You can sign in from the terminal or from the proxy's setup page at http://127.0.0.1:11539. Either way,
the proxy holds the credential and the agent only asks it for models. Signing in again refreshes the same
account — the models it can use, its plan, its allowance — rather than adding another.
maple-harness auth login github-copilot # a browser sign-in
maple-harness auth login claude # an Anthropic API key
maple-harness auth logout claude
maple-proxy auth status # what is signed in
This page is about signing the proxy in to model providers. On a proxy several people share, each person signs in to the proxy with an access token of their own: see How each person signs in.
In plain words #
- What it is. Signing in tells the proxy which accounts it may use for you: a GitHub Copilot seat, an Anthropic API key, or another provider. The proxy keeps the credential; the agent never sees it.
- Why you want it. Without an account (or a model server of your own) there is no model to talk to. With two, the proxy can move to the second when the first runs out.
- The clicks. Open the setup page (
http://127.0.0.1:11539), then Providers. Under Account, press Sign in for GitHub Copilot (a code and a link in your browser), or paste an Anthropic key and press Save key. Other providers (OpenRouter, Grok, Gemini) are under + Add provider on the same tab. Or use the commands below.

GitHub Copilot #
maple-harness auth login github-copilot
The command prints a code and a link. Open the link, enter the code, and approve. The agent then asks Copilot which models your plan allows and configures exactly those.
- Free plan. It works, including Copilot's auto mode. The setup page shows how many chats you have left and when they reset, and the status bar in the agent shows the same.
- Copilot Auto. When your account offers it, the model list also has
github-copilot/auto, where Copilot picks the model for each request. See Copilot Auto. - Paid and organisation plans. The page and the status bar show your plan's allowance where Copilot reports one.
- No models listed. Some accounts have no chat models enabled. Enable them in your Copilot settings on GitHub, then sign in again.
Claude (Anthropic API key) #
maple-harness auth login claude
It asks for an API key (typed hidden), checks it with Anthropic, and configures the models that key can call. You can also paste it into the Anthropic (Claude) card on the setup page. Create a key in the Claude Console. An account with no credit will sign in but its requests will fail with a "credit balance too low" message until you add credit.
The key is checked when you add it. Pasting it on the setup page or running auth login asks Anthropic
for the key's model list, which spends no tokens. A key that is not valid, has expired, was disabled or
deleted, or may not use the API in its workspace is refused with a message that says which, and nothing is
stored. A key that changes in config.yaml (or through the setup page's provider form) while the proxy runs
is checked the same way once; if Anthropic refuses it, the proxy's log and the account card say so. No key
is ever written to a log.
Use an ordinary API key, limited to one workspace. A proxy only sends model requests, so it should hold the least access that does that:
- An Admin API key (
sk-ant-admin...) manages your whole organization and is refused when you add it. One that is already in your configuration keeps working, but the account card andmaple-harness doctorflag it until you replace it. - A key not limited to one workspace (a personal or service-account key made for several workspaces)
must name the workspace each request runs in. Signing in with one asks you to choose: the setup page lists
the workspaces the key can see, and on the command line run
maple-proxy auth login anthropic --workspace wrkspc_...(signing in without--workspacelists them). The chosen workspace is saved with the provider asworkspace_idand sent with every request. A key limited to one workspace is safer, and the account card says so while you use the other kind.
Not a Claude subscription. A claude.ai or Claude Code sign-in (Free, Pro, Max, Team or Enterprise) is not an API key. Anthropic's terms don't allow other tools to use a Claude.ai subscription sign-in, so Maple never takes one: if you paste one by mistake it is refused, and one found in your configuration is never sent. What to use instead:
- An API key, billed per token. Since October 2026, Claude Max and Team plans include monthly API credits in a linked Claude Console organization, and an ordinary API key from that organization uses them. See Anthropic's API credits for Max and Team plans, and Use your Max or Team credits with Maple for a monthly dollar budget that matches them.
- Claude through your own cloud account (Amazon Bedrock, Google Vertex AI or Microsoft Azure), where Maple supports it.
An API key has no fixed seat or subscription cap the way a Copilot seat does, so a second key on a different Console account (its own spend limit, its own rate limit) is a plain, ordinary thing to add as a fallback; see more than one account below.
What the account card shows. After the first request (or the sign-in), the card shows the organization
and workspace ids Anthropic reports for the key, and, from the rate-limit figures Anthropic sends with every
reply, how many requests and input and output tokens per minute are left for each model you used. Nothing is
asked of Anthropic for these. A model with a tenth or less of a limit left shows "near Anthropic's rate
limit" on the Health card, and with alerts.quota_fractions set (see
Alerts and forecasts) it also raises a quota alert. Figures older than an hour are
not shown.
OpenRouter #
OpenRouter can make a key for you when you sign in with your OpenRouter account. Nothing about OpenRouter appears until you choose it.
On the setup page, click Add provider, choose OpenRouter as the type, and click Sign in with OpenRouter. Approve in the OpenRouter tab that opens. Back on the setup page, the provider is saved with its new key, and Detect models lists the models it can use: keep the ones you want and click Save.

From a terminal:
maple-proxy auth openrouter # opens your browser, then waits for OpenRouter
maple-proxy auth openrouter --no-browser # prints the link instead of opening it
maple-proxy auth openrouter --headless # no browser on this machine: paste the code OpenRouter shows
maple-proxy auth openrouter --as work # a second OpenRouter account, with its own name
Or from the harness, which asks your proxy to do the same (the proxy keeps the key; the harness never sees it):
maple-harness auth login openrouter # opens your browser, then waits for the proxy
maple-harness auth login openrouter --no-browser # prints the link instead of opening it
maple-harness auth login openrouter --headless # no browser on this machine: paste the code OpenRouter shows
maple-harness auth login openrouter --id openrouter-work # write a second OpenRouter provider under this id
OpenRouter sends your browser back to the proxy's machine, so without --headless open the link on that machine.
When the harness uses a proxy on another machine, sign in there instead (maple-proxy auth openrouter or the
setup page): maple-harness auth says so.
Then pick its models on the setup page (Detect models), or list them under the provider in the configuration.
- The key is yours. OpenRouter creates it under your account, labelled "Maple Harness". You can set a limit on it or revoke it on OpenRouter's keys page, and you use it under OpenRouter's own terms.
- It is kept like any other key: in the keyring, with only a reference in the configuration. Maple never shows it.
- Pasting a key still works. Type an OpenRouter key into the provider's API key field instead of signing in; a provider you already set up with a key keeps working as it is.
- The sign-in waits ten minutes for you to approve, the same time OpenRouter's code is valid.
Grok (xAI API key) #
maple-harness auth login xai # "grok" works too
It asks for an API key (typed hidden), checks it with xAI, and configures the chat models that key can call, with their context windows. Create a key in the xAI Console. Nothing about Grok appears on the setup page until you choose it: to add it there, open Providers, click + Add provider, choose Grok (xAI) as the type, paste the key, click Detect models, keep the ones you want and Save. Once signed in, Grok has an account card like Claude's.

- The key is checked when you add it. Asking xAI for the key's model list spends no tokens. A key xAI refuses is not stored. A key that is plainly another vendor's (Anthropic, OpenRouter, Google) is refused before it is sent anywhere.
- What it costs. xAI states the price of every reply. Maple records that figure as the request's cost in
dollars (shown where dollar costs are shown, such as
/cost, the usage log and the Costs & budgets tab, which label dollar figures as estimated; for Grok it is the price xAI's reply stated). Tokens spent reasoning count as output, as xAI bills them. - When the money runs out. A team out of credits, or at its monthly spending limit, is treated as an account with nothing left: the proxy moves to the next account in