acp, opencode or grok gets
this server with its own token (see Agents get these tools),
and outside tools and bots reach it with a token you create. It is separate
from the Channels bridge (overdeck-bridge), which delivers messages into one
running agent.
Every tool calls an existing dashboard route with the token the client
presents, so a tool can do only what that token’s scopes allow on that route.
There is no second path to any operation.
Tools
No tool pairs devices, creates or revokes tokens, reads or writes settings, or
touches the session vault.
tools/list shows only the tools whose scope the token holds, so a
read:state token sees only list_machines. Calling a tool the token cannot
see answers Unknown tool <name>. Tools for managed agents are listed only to
agent tokens.
Agent-only tools
A worker or lane wait returns within 50 s; call its
next again instead of polling.
Each workflow tool runs the pan command for the calling agent, on that
agent’s issue, and waits up to 50 s. It answers done with the exit code and
output, or running with next, a wait_job call to make again. A non-zero
exit code means pan refused; stderr says why. Review, test and ship agents
lack operate, so done is hidden from them.
Most agent-only tools call routes under /api/self/, which refuse any token that is not
an agent token. lane_status and lane_stop call the lane routes, and task_cancel
calls the worker stop route after an owner check, so the token’s scopes judge those.
Secrets
An agent that needs an API key or a password callsrequest_secret instead
of asking in chat, so the value never enters its transcript.
- The request shows in Needs you (top bar, project Home, Activity → Needs you); clicking it opens a dialog with the masked input. The owning conversation (or the agent’s session panel) also shows the same card at the top. Only this machine’s own dashboard, opened in a browser on this machine, can answer it. A non-root viewer (a phone, a paired device or another machine’s browser) sees “Answer this on <machine>‘s own dashboard. A secret can be typed only in a browser on <machine> itself, so it never crosses the network.”
- The operator types the value into the masked input and chooses Send, or chooses Decline.
- The value lands in a file:
~/.overdeck/agents/<agentId>/secrets/<NAME>for an agent, or~/.overdeck/conversations/<tmux session>/secrets/<NAME>for a conversation. The file has mode 0600 in a directory with mode 0700. - The
secrets/directory is deleted when the agent stops, is killed, exits or is closed out. - A request expires after 10 minutes by default (
timeoutMsallows 1 to 60 minutes). A dashboard restart forgets every pending request, and the agent must callrequest_secretagain. - The value never appears in a tool result, the transcript, the activity feed
or the dashboard log. The agent reads the file straight into the program
that needs it, for example
KEY="$(cat <file>)" some-command, and never prints it.
Machine links
An agent told to work on a machine that is not linked yet callslink_machine with the operator’s words for it, such as “my desk Mac”. It
never asks for a pairing link in chat, so no pairing code enters its
transcript.
- The request shows in Needs you (top bar, project Home, Activity → Needs you); clicking it opens a dialog with Link a machine… and Dismiss. The owning conversation (or the agent’s session panel) also shows the same card at the top. Only this machine’s own dashboard, opened in a browser on this machine, can answer it. A non-root viewer (a phone, a paired device or another machine’s browser) sees “Answer this on <machine>‘s own dashboard. Machines can be linked only from a browser on <machine> itself.”
- Link a machine… opens the usual Link a machine dialog. After the link
succeeds, the agent’s
link_machine_waitanswerslinkedwith the new machine’senvironmentIdandlabel. The agent passes that label asmachinetodelegate_task,start_workerorstart_conversation. - Dismiss declines the request, and the wait answers
declined. - The agent never sees the pairing link. The label it gets comes from the link itself.
- Only the card’s dialog answers a request. A link made any other way (
pan machines link, the Machines panel, the SSH or Fly dialogs, or the command palette) does not; dismiss the card instead. - A request expires after 24 hours. A dashboard restart forgets every pending
request, and the agent must call
link_machineagain. - An agent may hold 20 pending requests, secret and machine-link requests together. Asking again with the same hint (ignoring case and outer spaces) answers the pending request.
Memory
Bothmemory_add and memory_search run pan memory for the calling agent
in its own checkout and answer done with the result, or running with
next, like the other job tools. A non-zero exit code means pan refused
(an existing id, secret-like text, a home-directory path); stderr says why.
A project fact lands in the agent’s own checkout, so pan memory list --here
run there shows it at once, while the primary checkout shows it only after
the agent’s branch merges. See Project memory.
A tool the token’s scopes hide answers Unknown tool <name>. A route can
still refuse a listed tool, for example a linked machine’s ceiling, with
HTTP 403: insufficient_scope (missingScope: approve).
Pull requests
watch_pull_request gets an agent a message when a GitHub pull request it
cares about changes, without needing a conversation of its own. Overdeck
checks watched pull requests about once a minute, through the existing PR
sync sweep on this machine’s primary dashboard, never a separate poller.
GitHub pull requests only; GitLab merge requests are refused.
A watch delivers one message per change, naming every event the change
produced: the checks failed or passed, the review state changed, merge
conflicts appeared, or the pull request was merged or closed. The message
reads [Overdeck] <repository>#<number>: <phrase>; <phrase>. <url>, for
example [Overdeck] eltmon/overdeck#4943: checks failed (was pending). https://github.com/eltmon/overdeck/pull/4943; a message that ends the watch
adds a trailing sentence saying so. A merged or closed pull request ends the
watch, as does the eleventh consecutive message that only reports a
review-state change (watch_pull_request again to keep watching after
that). Each agent may hold 20 watches, and 50 may exist across every agent
on this machine; past either limit, watch_pull_request answers an error
instead of a new watch. A watch works whether or not its pull request is
linked to any conversation, and a stopped agent’s watches are removed when
its token is revoked.
Over HTTP
Open Settings → Anywhere on this machine and choose Copy MCP URL. The dialog:- Asks for a name, the address the client will use, and whether to allow answering questions and approving permissions.
- Creates an MCP access token and copies the URL,
<address>/mcp, to the clipboard. - Shows the URL, the
Authorization: Bearer odk_…header and a ready client config, each with a Copy button. The token is shown once.
https:// one selected. When there is none, the dialog
offers this browser’s address, which works only on this machine. Add a
reachable address (for example a Tailscale address) under Settings → Anywhere
first.
The token is never part of the URL. Proxy and access logs record URLs, so the
token travels only in the Authorization header. Every common MCP client
accepts a header. With Claude Code:
mcp.json-style config:
POST /mcp gets its own server and one JSON
answer; there is no session and no event stream. GET /mcp and DELETE /mcp
answer 405. Only a browser on this machine can create the token; a paired
device’s browser sees “Only a browser on this machine can create MCP tokens.”
/mcp is served by the production dashboard (pan up) and its reachable
addresses. The Vite dev server (pan dev) does not proxy it.
Over stdio
pan mcp serve serves the same tools over stdin and stdout. It reads the token
from the OVERDECK_MCP_TOKEN environment variable, or, when that is unset,
from the file named by OVERDECK_MCP_TOKEN_FILE; a command-line flag would
show in ps. Create a token first:
admin, or when the file is unreadable, empty, or readable by group or
others. Its stdout carries only JSON-RPC; every message goes to stderr.
A Claude Desktop config:
Sign in with OAuth
A hosted MCP client (a Claude Desktop connector, a chat bot) cannot be handed a token file. It signs in through the MCP authorization flow instead: point it at<dashboard URL>/mcp and it finds the sign-in server by itself. The discovery
document is at <dashboard URL>/.well-known/oauth-protected-resource/mcp, and
an unauthenticated POST /mcp answers 401 with a WWW-Authenticate header that
names it.
- Your app opens a sign-in page in your browser. The page shows the app’s
name, where it will send you back, and an approval code such as
KQZT-MWRB. - The dashboard’s Needs you panel shows a card with the app’s name, the
redirect host, and the same approval code, or run
pan mcp oauth pendingfrom a terminal on this machine. Only this machine’s own session can see it: on its desktop layout that’s the full card below; on its mobile layout, which has no room for the card, it’s “Approve on the desktop” instead. A paired device never receives the pending sign-in at all: there is nothing to approve from someone else’s phone. - You check that the card’s code matches the page you opened, pick an access level (the select starts at the level the app asked for), and click Approve or Deny.
- The page sends you back to your app, and your app is signed in.
An OAuth sign-in never gets
admin, forward, read:settings, read:costs or
read:events. The level the app asks for is only a suggestion: a stock MCP
client asks for every level, so Overdeck offers the lowest one it named, and you
choose the real level when you approve.
Each sign-in gets an access token that lasts 30 days and a refresh token that
lasts 90 days. Each refresh replaces both. A refresh token is single use: if an
old one is presented again, Overdeck treats it as stolen and ends the sign-in.
After 90 days the app must sign in again. A sign-in waiting for approval expires
after 10 minutes, and every waiting sign-in is lost when the dashboard restarts;
start it again from the app.
Manage sign-ins from the terminal:
issue creates a sign-in at once and prints its access and refresh tokens. They
are shown once; store them in the client. Use it for an API caller such as the
xAI API, which takes a token but cannot show you a browser page. The approval
code is case-insensitive and the dash is optional.
The sign-in endpoints answer on this machine, the LAN, the tailnet (Tailscale
Serve) and the dashboard’s other trusted addresses. The discovery documents are
built from the address the client used, so a request for an address Overdeck
does not trust gets 400. A Tailscale Funnel request gets 404 unless Public MCP is
on (below).
Public MCP for hosted bots
A hosted bot, such as Grok Bot or the xAI API, runs on servers you do not control. It cannot join your tailnet or run the Overdeck connector, so it needs a public HTTPS address for/mcp. Public MCP publishes exactly /mcp and the
sign-in endpoints on the internet through Tailscale Funnel. TLS ends on this
machine, and only OAuth sign-ins you approve can use it.
Public MCP is off by default. Turn it on in Settings → Anywhere → “Public MCP
for hosted bots”, or with PUT /api/mcp/public and the body { "enabled": true }
(root credentials only). The switch is mcp.public.enabled in
~/.overdeck/config.yaml. A project .pan.yaml or .overdeck.yaml cannot turn
it on. The dashboard reads the value once and keeps it, so a hand edit of
config.yaml takes effect after a dashboard restart or the next switch change.
Prerequisites are the same as for triggers (see
Publish with Tailscale Funnel):
HTTPS certificates on the tailnet, the funnel node
attribute for this machine, sudo tailscale set --operator=$USER, and this
machine’s .ts.net address saved as a trusted address. Without that trusted
address the dashboard cannot build the public URL, and the sign-in documents
answer 400.
Publish the paths (replace 3011 if your dashboard API port is different;
the Settings panel prints the commands with your port). Overdeck never runs
tailscale for you:
https://<machine>.<tailnet>.ts.net:8443/mcp.
Grok Bot and the xAI API. The Grok Bot plugin and runnable xAI API
examples live in integrations/grok-bot/.
Its mcp.json runs the connector over stdio; for Public MCP, replace it
with the public URL. Grok Bot signs in with OAuth on first use. The xAI API
cannot open a browser, so mint its token with
pan mcp oauth issue --name xai-api --level read and
pass the access token in the authorization field of an mcp tool, with
server_url set to the public URL and server_label set to overdeck.
What is reachable. While the switch is on, a Funnel request reaches only
these nine surfaces, matched on the exact path, plus the trigger route
POST /hooks/*, which Funnel reaches whether or not Public MCP is on (see
Triggers). Every other path gets 404:
POST /mcpGET /.well-known/oauth-protected-resourceGET /.well-known/oauth-protected-resource/mcpGET /.well-known/oauth-authorization-serverPOST /oauth/mcp/registerGET /oauth/mcp/authorizeGET /oauth/mcp/authorize/statusPOST /oauth/mcp/tokenPOST /oauth/mcp/revoke
pan token create token, a Copy
MCP URL token or an agent token gets 403 public MCP accepts only OAuth sign-ins. Those tokens still work on this machine, the LAN and the tailnet.
Limits. Each limit counts requests in a 60-second window that starts at the
first request:
Over a limit, the answer is 429
{ "error": "rate_limited" } with a
Retry-After header. The /mcp limit counts per access token, so a refresh,
which replaces the access token, starts a new count.
Audit. Every public request writes one entry to the activity feed, on a
best-effort basis: the write never delays or fails the request, so an entry can
be missing if the activity store is unavailable at that moment. Each entry reads
Public MCP <METHOD> <path> <status>, with the OAuth client id when there is
one (a client_id that is not an Overdeck client id is recorded as none). No
entry carries a token, a code or a request body. The sign-in page checks its
status every 2 seconds, so a sign-in that waits for you writes one entry each
time.
Turning it off makes Funnel requests to these nine surfaces get 404 again;
POST /hooks/* keeps working for triggers. It does not end any
sign-in: approved apps keep working on the tailnet and this machine. End a
sign-in under Settings → Access Tokens → Sign-ins or with
pan mcp oauth revoke <sign-in id> (see Revoking).
Agents get these tools
Every Claude Code, Codex, Kimi Code ACP (acp), OpenCode (opencode) and Grok Build
(grok) agent that Overdeck launches on this machine starts with the overdeck server: work
agents, role runs (plan, review, test, ship, worker and the others), planning
sessions and conversations. You do not create a token for them.
Each agent holds its own agent token. It sits in mcp-token (mode 0600), next
to overdeck-mcp.json, in ~/.overdeck/agents/<id>/ for an agent or
~/.overdeck/conversations/conv-<name>/ for a conversation. overdeck-mcp.json
runs pan mcp serve and names only the token file, so neither it nor the
launcher script holds the token. The launcher passes
--mcp-config=<file> and, when the role has no tool allow-list,
--allowedTools=mcp__overdeck, so a tool call does not stop at a permission
prompt. Roles with a tools: list (review, test) get mcp__overdeck in that
list instead.
An ACP-hosted agent (acp, opencode or grok) gets the same overdeck-mcp.json. The launcher passes
--mcp-config <file> to the ACP host, which sends the server to the agent in
session/new and session/load. The ACP host approves the agent’s permission
requests itself, so no allow-list is needed.
A Codex agent gets the server differently: Codex has no CLI flag for an
MCP allow-list, so instead of a launcher flag it gets an
[mcp_servers.overdeck] table written directly into
~/.overdeck/agents/<id>/codex-home-v2/config.toml (or
~/.overdeck/agents/conv-<name>/codex-home-v2/config.toml for a
conversation), alongside any MCP servers the role itself declares. The table
names only the token file in its env, never the token. It also carries
default_tools_approval_mode = "approve", because Overdeck’s MCP tools carry
no readOnlyHint annotations: without that key, Codex refuses every
model-initiated call with “MCP tool call requires approval, but approval
policy is never” under approval_policy = "never".
The token’s scopes follow the agent’s role:
A resumed, recovered or relaunched agent keeps the same server and reuses its
live token. Stopping the agent revokes the token.
Work agents and the review security lane also get a
semgrep MCP server when
Semgrep’s MCP server is on; see Semgrep.
To turn injection off, set this in config.yaml:
OVERDECK_DOCKER_WORKSPACE=1
or PAN_DOCKER=1), bare conversations, Fly machines, and harnesses other than
Claude Code, Codex, acp, opencode and grok. When the token cannot be
minted or the config cannot be written, the agent starts without the server and
the log shows one [agent-injection] overdeck MCP skipped for <id>: <reason>
warning. The agent can still reach Overdeck through pan.
What the agent is told
Every Overdeck-launched agent’s launch context ends with a short tools block (src/lib/mcp/agent-instructions.ts, each block at most 1,500 characters).
An agent that gets the overdeck server above is told “Overdeck tools”: prefer
the MCP tools to pan; never poll, call next again when a wait tool answers
running or pending; checklist with task_claim/task_done, finish with
done; get a secret with request_secret; link a machine the operator names
with link_machine; link a PR with link_pull_request/watch_pull_request.
Every other agent is told “Overdeck commands” instead, with the pan equivalent for
each: pi, kimi-code, ohmypi, muse, prime-agent, any agent in a Docker
workspace, and every agent when mcp.agents is false.
Project MCP servers
A project can give its own agents extra MCP servers, separate from every other project’s. Declare them underprojects.<key>.mcp_servers in
~/.overdeck/projects.yaml. Two projects can then use two accounts on one
service, for example two Linear workspaces, without either agent seeing the
other’s server.
mcp_servers uses the role mcpServers: shape: a YAML list of single-key
maps. Each entry follows these rules:
type: stdiois the default. It needscommand;args(a list of strings) andenv(a map of strings) are optional.type: httpneedsurl, which must start withhttps://, or withhttp://localhostorhttp://127.0.0.1.headers(a map of strings) is optional.- A name matches
^[A-Za-z0-9_-]+$. The nameoverdeckis reserved. When two entries share a name, the first one is kept. - An invalid entry is skipped with one warning,
[project-mcp] <project>: server <name> skipped: <reason>. The other entries still apply. A plain map in place of the list is rejected as a whole.
path contains the agent’s cwd. A launch that matches neither, for example a
handoff worktree in an unregistered directory, gets no project servers and no
project secrets.
${NAME} references. Overdeck replaces each ${NAME} in args, env
values, url and headers values at launch time. It looks in the project’s
secrets_file first (see
Project credentials), then in
the environment of the process that launches the agent. A server with an
unresolved reference is skipped with a warning that names the server and the
variable, never a value. $NAME without braces is left as written. The
resolved values are written into the agent’s launch files, which are mode
0600 in a 0700 directory, so keep the values themselves in secrets_file,
never in projects.yaml or the repo.
What each harness gets:
The launch file is written whenever at least one server resolves, so project
servers still load when
mcp.agents is false or the agent token could not be
minted; only the overdeck entry drops out. Bare conversations get no launch
file and no project servers.
When the launching role declares a server with the same name (roles/test.md
declares playwright), the role’s server wins and the project’s entry is
skipped with a warning.
On Claude Code, the launcher adds --allowedTools=mcp__overdeck,mcp__<name>,…
for every server in the file, so a project tool call does not stop at a
permission prompt. Roles with a tools: allow-list (review, test) keep their
own list and do not get the project tools added. Under
claude.permissionMode: auto (the default for new installations), the
auto-approve hook allows tool calls in Overdeck agent sessions, including
tools outside that list, so those calls do not prompt.
See Permissions and agent guardrails for both modes.
Strict mode. mcp_strict: true adds --strict-mcp-config to that
project’s Claude Code launches. Claude Code then loads only the servers from
--mcp-config files: the overdeck server, the project’s servers and the
role’s servers, which also arrive through --mcp-config. Your user-scope
servers in ~/.claude.json and your claude.ai connectors do not load, which
keeps their tools out of the agent’s context. The default is false. Strict
mode has no effect on other harnesses.
A repo .mcp.json does not load in agents. Claude Code waits for an
approval of a project-scope .mcp.json that a spawned agent never gives, so
servers that only live there are unavailable to Overdeck agents with or without
strict mode. Declare them in mcp_servers instead.
OAuth logins. An http server’s OAuth login belongs to its name and URL. A
project server with the same name and URL as one you signed in to yourself
reuses that login. A server under a new name or URL has no login, and an agent
cannot complete an interactive sign-in, so send a token header from
secrets_file instead, as linear-myn does above.
Pack MCP servers
A skill pack can carry its own MCP servers. Overdeck applies only remote,claude-plugin pack entries: type: "http", a url
starting https://, a name matching ^[A-Za-z0-9_-]+$ other than overdeck,
and string header values with no ${...} reference in the url or a header. A
stdio or sse entry is never applied, because that would run pack code at
every launch; the add and update preview and the Skills page list it under
Not applied instead.
Consent. A pack’s MCP servers reach agents only after you confirm an add
or update preview that lists them (pan skills pack add <id> or
pan skills pack update <id>). Overdeck records this as mcp: true on the
pack’s registry entry. The Not applied label means “this pack declares
something Overdeck does not apply,” not “consent is missing”: a pack you
trusted before this consent model, whose https server is otherwise valid,
shows no MCP servers row under Not applied, but its server still does not
reach agents, and each launch for a selected pack without mcp: true logs
one warning naming pan skills pack update <id> instead of using it. Run
that command and confirm the preview to record consent.
When a pack contributes. A pack’s servers join a launch exactly when the
pack is in that launch’s selection, the same rule as its skills: at least one
of its skills resolves on for that launch, including the conversation layer.
A pack that is off contributes nothing, consented or not.
Precedence. Names are claimed in this order: overdeck, then the
launching role’s own servers, then the semgrep server when Semgrep’s MCP
server is on (see Semgrep), then
the project’s mcp_servers, then pack servers, lowest pack id first. A later source’s server with a name an earlier
source already claimed is skipped with one warning,
[pack-mcp] <pack>: server <name> skipped: <reason>. A project mcp_servers
entry named atlassian therefore overrides the atlassian pack’s own server,
which is the escape for an OAuth-only or Bearer-key setup (see
Atlassian auth below).
What each harness gets:
Atlassian auth
Theatlassian pack’s server needs no configuration to be useful in Claude
Code, but Codex agents need Jira credentials because they cannot sign in
interactively. When the Jira tracker keys are both set (email and API token,
from Settings → Tracker Keys or ~/.overdeck.env), and the site is Jira Cloud
or unset, Overdeck adds Authorization: Basic base64(email:token) to the
atlassian server for every harness. Without both keys, a Claude Code agent
reuses your own /mcp sign-in for that server’s name and URL; a Codex launch
gets no atlassian server at all, with one warning naming it. See
the atlassian pack for the full setup.
Scopes and the approve scope
An MCP token is an ordinary access token. Copy MCP URL gives itread:state,
read:conversations and operate by default. operate covers tell, the
start tools, the stop, resume and interrupt tools, and add_skills.
The box Allow answering questions and approving permissions adds
approve. It is off by default, and only approve or admin satisfies it.
approve lets the token answer blocking prompts with any of the eight answer
tools: answer_question, answer_permission, answer_pane_choice,
answer_codex_approval, answer_pi_ask, answer_plan, answer_agent_plan
and answer_agent_permission. See Remote access
for the full scope table.
MCP never accepts an admin token, the machine’s internal token or the
dashboard’s own session. Both transports refuse them.
Revoking
Revoke an MCP token under Settings → Anywhere → Access tokens, under Settings → Access Tokens, or withpan token revoke <id>. A token revoked
through the dashboard fails its next request at once. A token revoked by
another process (for example pan token revoke while the dashboard is
unreachable) fails within 5 seconds, when the dashboard rereads its token list.
End an OAuth sign-in under Settings → Access Tokens → Sign-ins (also
Settings → Anywhere → Access tokens), or with pan mcp oauth revoke <sign-in id> (ids from pan mcp oauth list); its access and refresh tokens
stop working at once. Revoking an OAuth access token under Settings →
Access Tokens or with pan token revoke stops that access token at once and
ends its sign-in at its next refresh.
Both token lists fold one access token per running agent under a collapsed
Show agent tokens (N) toggle, so a fleet of agents doesn’t bury your own
tokens; click it to reveal and revoke an individual agent’s token.
Bots
Hermes, OpenClaw, Grok Build, Grok Bot and the xAI API reach this server through Connect a bot in Settings → Anywhere → Bots. A bot with a shell connects in one paste with Copy for <bot>; see Connect in one paste; the xAI API uses Public MCP above, and Grok Bot can too. See Connect a bot for each platform’s setup and Run the Overdeck connector for the connector. Everypan mcp command is in pan mcp.
Fleet reach
One MCP URL reaches every machine this one is linked to (see Linked machines).list_machineslists this machine and each linked machine with its state, load and tags.list_conversationsandsearch_conversationsinclude linked machines’ conversations. A conversation on another machine is named@<label|environment-id>/<name>; pass that name toread_conversation,send_message, theanswer_*tools, andschedule_message,schedule_recurring,list_scheduled,update_scheduledanddelete_scheduled.start_conversation,start_workerandstart_issuetakemachine, and so do the agent toolsdelegate_taskandlane_start: omit it for this machine, give a linked machine’s label or environment id, orautoto place the work by load. Withauto,needs(a list of capability tags such asdocker) limits the choice.
approve gets 403 on a linked
conversation’s permission prompt, and one without tell cannot message it. Settings are
never reachable: PUT /api/settings answers 403 because an MCP token never carries admin,
and linked machines never forward it. A linked machine cannot use this one to reach a third
machine (no chained hops), so the URL reaches only the machines linked to this dashboard.
An agent’s token acts as that agent on a linked machine. A managed agent’s token is
forwarded as { agentId }, with its scopes as the ceiling, so the agent can read a linked
conversation but not change it, and delegate_task or start_issue with machine start the
work through that machine’s work door as the agent, which may later stop what it started. A
conversation’s token acts as the operator, limited to its scopes, as the conversation’s own
pan does.
Agent answers (answer_agent_plan, answer_agent_permission, answer_question with
agentId) reach agents on this machine only; list_pending_input marks a linked machine’s
agents remote: true.
The linked machine must run a version with the schedule scopes (PAN-4939); an older one
answers 403 insufficient_scope for recurring schedules.
Get help
A tool the token’s scopes hide answersUnknown tool <name>. A tool the token’s scopes
do not cover answers HTTP 403: insufficient_scope (missingScope: ...). A launch that
could not get the overdeck server logs [agent-injection] overdeck MCP skipped for <id>: <reason>.
Still stuck? Ask on the Overdeck Discord or file a
GitHub Issue.