Sign-in, consent and access#
Contents
When you connect, Bitebox asks you to sign in on canvas.bitebox.gg and shows a consent screen. What you choose there is the assistant's grant. The OAuth scope is always mcp; the grant is what limits the assistant.
What you choose#
| Setting | Options | What it allows |
|---|---|---|
| Projects | Every project, or Selected projects | The projects the assistant can see. Others answer as if they do not exist. |
| Documents | None, read, write | Reading and editing story graphs, project changes, layout. |
| Media | None, read, upload | Listing media, uploading files and importing from a URL. |
| Preview | On or off | Preview links and simulated playthroughs. |
| History | None, read | Reading and comparing past revisions, which also needs documents: read. Restoring or naming one needs documents: write, not history. |
| Generate | None, or a daily credit budget | Quoting and running models, up to the budget each day. You can also make it ask before each run. |
| Publish | None, or with your confirmation | Preparing the publish page and asking you to publish. |
| Viewer analytics and templates | Off, or on | Path analytics, benchmarks, templates, and your generation usage with its estimated cost. |
The form starts with documents: write, media: upload, preview on, history: read, publish with your confirmation, and a daily generate budget. Change anything before you click Allow.
Daily generate budget#
The budget is a spending cap, not a credit grant. Runs still spend credits from your balance. The form suggests 25,000 credits per day. The day resets at midnight UTC. Before each run Bitebox reserves the quoted maximum against the budget and releases anything a failed run did not use.
Ask before each run#
Turn on Ask before each run under Generation to approve every generation yourself. It is off unless you turn it on. Before each run, the assistant tells you the estimated credits and the most the run can cost, and gives you an approval link. The link opens the project in the Canvas, where a card asks you to approve that run. Click Approve to let it run, or Decline to stop it. Nothing is charged until you approve, and the assistant cannot approve for you.
An approval covers one run, exactly as asked, at the price you saw. If the prompt, inputs or price change, you get a new card. The daily budget still applies: a run above what is left today is refused, and a card in the Canvas asks you to approve the extra spend.
The setting covers generation runs only. Media reviews and panel watches still spend from the daily budget without asking.
Sessions and tokens#
Your assistant stores its tokens; you never copy them. Access lasts an hour and the assistant refreshes it on its own. After 30 days without use, sign in again. Never paste a token, a sign-in code or a callback URL into a chat, a ticket or a document.
Change or revoke access#
Open the MCP tab on your Canvas home page. It lists every connected assistant. Click Edit to change its projects, permissions or budget, or Revoke to cut it off at once.
An assistant can also drop its own access with agent_grants_revoke. It cannot revoke another assistant, and it cannot change what any assistant may do. Only you can, on this tab.