Help
Error reference
The messages Lookout shows when something fails, what each one means and what to do.
Match the message you see to a section below. A word in capitals, such as MODEL, stands for what the message names.
Find your error
| Message | Go to |
|---|---|
| Stopped, Interrupted, Paused, Round limit reached, Context full, Output limit reached, Plan limit reached, Declined, Failed | How a turn ends |
PROVIDER's 5-hour limit is used up, resets in 2h 10m, PROVIDER's weekly limit is used up | Plan limit used up |
MODEL's plan limit is used up, resets in 2h 10m, MODEL's own limit is used up | Plan limit used up |
Your PRODUCT plan has ended. Renew it, or choose another model | Plan ended |
PROVIDER needs you to sign in again, Waiting for PROVIDER: sign in again to account ID in Settings › Providers, PROVIDER refuses ACCOUNT: sign it in again or use another account | Sign in again |
MODEL is limiting requests right now, try again in a moment | Limiting requests |
PROVIDER reports MODEL is overloaded, MODEL overloaded, retrying TIME | Overloaded |
The turn stopped: MODEL was overloaded or unreachable | Overloaded or unreachable |
MODEL declined to answer this, PROVIDER declined this request on MODEL | Declined to answer |
PROVIDER refused this request as a third-party app. Nothing was billed. This is a Lookout bug: please report it | Refused as a third-party app |
PROVIDER accepts your subscription only in its own app, PROVIDER no longer accepts this version of Lookout, No signed-in PROVIDER account has access to MODEL, Your PROVIDER account doesn't have access to MODEL, Your PROVIDER plan doesn't include MODEL, PROVIDER doesn't serve your region | Refused whatever the sign-in |
| Retrying, Retried 3 times, Waiting on the provider's rate limit | Retrying |
Couldn't reach the provider. | Couldn't reach the provider |
The provider closed the connection. | The provider closed the connection |
Reached the limit of N model rounds before the turn ended | Round limit |
Context is not converging | Context is not converging |
context window exceeded and compaction could not recover | Context window exceeded |
The model answered the closing round with tool calls | Closing round with tool calls |
The model's response hit the output limit 2 times in a row | Output limit |
The model's response stream kept breaking before it finished | Stream kept breaking |
The provider sent the same incomplete reply twice, so the turn stopped there | The same incomplete reply twice |
Still over the context budget after summarizing | Compaction notes |
MODEL isn't available: PROVIDER is signed out. Choose a model | Model isn't available |
the machine's disk is full, database or disk is full | The machine's disk is full |
MACHINE answered with an error: MESSAGE | A machine answered with an error |
| Microphone access is off, Dictation kept and the other dictation toasts | Dictation failed |
| Lookout could not start | Lookout could not start |
| This browser isn't signed in to this Lookout | The browser isn't signed in |
| Lookout lost its connection to itself | The window lost its connection |
| macOS says Lookout is damaged and can't be opened | macOS says Lookout is damaged |
| The update didn't install | The update didn't install |
lookout: not signed in on this machine: run lookout login | Not signed in |
lookout: the Lookout app (pid N) is signed out of your Lookout account | The app is signed out |
lookout: lookout VERB is the USER's to run | Yours to run |
lookout: MACHINE is offline | Machine unavailable |
lookout: cannot reach the Lookout account service | Account service unreachable |
lookout: unknown command "WORD" | Unknown command |
Another message starting with lookout: | In the terminal |
An exit code from lookout | Exit codes |
An error code in a connected app, such as machine_unavailable | In another app |
How a turn ends
The line under a turn says how long it took. When the turn didn't finish on its own, the line also says how it ended, unless the notice right above it already does (a failed, spent or declined turn's): then the time's tooltip says it. A spent plan's or a rate limit's notice is a quiet wait, a declined one's a warning, and only a failure's is red.
| Line | What happened | What to do |
|---|---|---|
| Stopped | You stopped the turn. | Send a message to go on. |
| Interrupted | Lookout stopped while the turn was running, such as in a crash. | Click Continue to pick it up where it stopped. |
| Paused | An update or a restart paused the turn. | Nothing: it picks back up when Lookout starts again. If it doesn't, click Continue. |
| Round limit reached | The turn used all the model rounds of a round limit you set. | See Round limit. |
| Context full | The work didn't fit the model's context, even after compaction. | See When the context runs out. |
| Output limit reached | The model's reply was cut off at its output limit twice in a row. | See Output limit. |
| Plan limit reached | The plan behind the model ran out. | See When a plan runs out. |
| Declined | The model declined to go on. Any answer above the line is not complete. | See Declined to answer. |
| Failed | The turn failed. The notice above the line says why. | Find the notice's message on this page. |
A turn that picked back up shows where, with Paused for update, Paused for restart, Interrupted, continued or Interrupted, resumed automatically.
In a chat
A failed turn ends with a notice. Details shows the provider's own message and, when the provider gave one, its Request ID for the request (quote it when you report the failure to the provider). Copy details (⇧⌘⏎) copies both. The buttons under the notice retry the turn on the same model or another: see Try again after an error. A retry that fails the same way (the same message from the same model) doesn't add a second notice: the one notice stays, and its Details say how often it failed, such as Failed 2 times, last at 12:57 PM.
The provider's own message is for you, never for a model. An agent, a parent chat or a subagent's parent hears only the
kind of failure and the provider that reported it, such as declined by the provider (claude), so a refusal never
spreads to the chats that read about it. lookout check, lookout sessions and the connected-app tools say it the same
way; --detail (or detail: true) adds the message. A failure names the provider only when the provider answered
with an HTTP error, such as failed at the provider (PROVIDER, HTTP 418). Any other failure is Lookout's own and
reads as its message's first line, such as database or disk is full.
PROVIDER's 5-hour limit is used up
The plan behind the model has no room left. When the provider says which of its windows ran out, the notice names it,
the 5-hour or the weekly limit, and the provider rather than the model: every model on that plan stops the same
way until the reset. When only the model's own limit ran out (a plan can limit one model on its own, such as Fable's
weekly limit on a Claude plan), it reads MODEL's own limit is used up, and the plan's other models still run.
Otherwise it reads MODEL's plan limit is used up. The notice says when it resets, and hovering it
shows the date and time. Continue on under the notice moves the turn to a model whose plan has room (no model of
the spent plan is listed, and one billed per token reads Per token), or Wait for the reset. A chat with fallback
models offers the first one whose plan has room first. With more than one account on the provider, see
When a plan runs out. lookout exec exits with code 3.
Your PRODUCT plan has ended
The provider says the account has no active plan any more: it was canceled or it expired, and nothing resets it. Lookout sends nothing more on the models the plan took with it, until a read of the plan says it is back. Models the provider still lets the account use without a plan (its own model list says which) are billed per token by the provider: they run only when you pick them, marked API key with no meter, and never as a new chat's model, a fallback or the account balancing's choice (billed per token). Renew the plan on the provider's page (Renew plan in Settings › Providers, or on the provider's Plan ended row under Attention in Settings › Usage), or move the turn: Continue on lists only other providers' models, and a chat with fallback models goes on with the first one that can run, saying the plan has ended. There is no Retry: the same request would be refused the same way.
PROVIDER needs you to sign in again
The provider refused the sign-in Lookout has for it. A spent plan never reads this way: that is Plan limit used up.
Click Sign in again under the notice: Lookout reads the provider's accounts again first, and if one of them can
serve (you signed in meanwhile, or added another account), the turn goes on at once. Otherwise it opens the provider's
row in Settings › Providers, and the same menu offers other models. Once an account serves again, the stopped turn,
subagent or workflow agent goes on by itself where it stopped, unless you pressed Stop meanwhile: Stop ends that
wait, and Sign in again or Retry still runs the turn. lookout exec exits with code 4.
With several accounts on the provider, a request whose account can't sign in moves to another one, so this stop shows
only when none is left. The notice then names the accounts by id, such as PROVIDER needs you to sign in again to account ID in Settings › Providers, and a workflow agent waiting on it reads Waiting for PROVIDER: sign in again to account ID in Settings › Providers on its page.
PROVIDER refuses ACCOUNT is the same stop for one account: the provider turned that account away (its plan ended,
or its organization's access is off) and nothing else could take the request. When the provider refuses one account
a request (HTTP 403), the same request goes to another account with room. If that one serves it, the refused account
is set aside: it reads as needing a new sign-in in Settings › Providers with the reason, you get one notice (once,
a restart included, and again only if it serves and is later refused again), and it takes no requests until you sign
it in again on this device or choose it under One account and it serves one. Nothing else lets it back: not a
restart, not a usage read that works, and not a sign-in or a renewed sign-in your other devices send this one. Each
device sets an account aside on its own. If the other account refuses the request too, the refusal was the request's,
and no account is set aside.
With no other account that has room, the account's own usage read speaks: refused, or naming no plan window, it sets
the account aside until a read works or a new sign-in, and the turn goes by the accounts left. A read that works
decides nothing while the other accounts are only at their limits: the turn stops on Plan limit used up and goes
on by itself at the first reset, when an account with room weighs the refusal. Only when no other account could ever
serve does a working read make it the request's refusal. The account is named by its place in the plans list and its
id, such as Claude account 3 (id a3).
MODEL is limiting requests right now
The provider is pacing requests, for example with many chats running at once. Lookout keeps backing off for a few minutes, honoring a Retry-After, and the chat shows Waiting on the provider's rate limit while it does. A spent plan is different: that fails at once with its reset. If the wait runs out, your plan still has room. Click Retry in a moment, or pick another model from its chevron.
The turn stopped: MODEL was overloaded or unreachable
The provider had a server error or was overloaded, timed out, couldn't be reached or sent an empty reply, and Lookout's own retries didn't get through. An overloaded provider that says how long to wait is waited out on the same model for up to a few minutes first, and the Retrying row says the provider asked to wait. Nobody knows when the provider recovers, so the turn doesn't go on by itself: the notice is red, and the chat shows the red alert under Needs you. Click Retry, or pick another model from its chevron.
PROVIDER reports MODEL is overloaded
The provider answered that this model is too busy to serve now, and Lookout's own retries didn't get through. Only that model is busy: the plan's other models still run. A chat or agent with fallback models goes on with the first one that answers, another model on the same plan included, for that turn only, and says so in a row such as Continued on Opus 5.5: Fable 5.2 is overloaded at Anthropic; its next turn starts on its own model again. Without one, an agent tries its model again after a minute, then after longer waits up to an hour, and goes on as soon as the model answers; its row reads MODEL overloaded, retrying TIME. The notice leads with Continue on a model on your plan that answers now, and Retry waits in its menu. Nothing switches by itself.
Retrying
A request failed for a reason that usually passes, and Lookout is sending it again: Retrying names the reason and the attempt, such as attempt 2 of 8. A rate limit that does not mean the plan is spent waits longer, and the row reads Waiting on the provider's rate limit while it does. Afterwards the row reads Retried request, Retried 3 times, or Waited on the provider's rate limit. Nothing to do unless the turn then fails.
Couldn't reach the provider
Lookout couldn't connect to the model's provider: the network is down, or something on it blocks the provider. It shows on a Retrying row or a subagent's card. Check your connection. If the retries run out, the turn fails with The turn stopped: MODEL was overloaded or unreachable.
The provider closed the connection
The provider ended the connection before its reply was complete, or before it answered at all. Lookout retries on its own; if the turn fails, retry it.
Reached the limit of N model rounds before the turn ended
A turn has no limit on its model rounds (a request to the model and the tool calls it makes in answer) unless you set
one, N, with LOOKOUT_MAX_ROUNDS in Lookout's environment. A turn that reaches it ends with Round limit reached.
Send a follow-up message to continue, with a narrower request if the agent was looping.
Context is not converging
The agent kept reading more than the model's context holds: after each compaction, the context filled up again. The turn ends with Context full. Ask for the work in smaller parts, for example reading large files in ranges, or split the task across chats.
context window exceeded and compaction could not recover
The provider refused the request as too large for the model, or, before sending, Lookout found the next request larger than the model's window. Compaction ran, then a last clear of tool output, and the request still did not fit. Start a new chat from a summary, or switch to a model with a larger window.
The model answered the closing round with tool calls
When the context runs out, Lookout asks the model for a final report without tools. This model called tools instead, and they weren't run. Send a follow-up message to continue.
The model's response hit the output limit 2 times in a row
The model's reply was cut off at its output limit, and cut off again after Lookout asked it to continue. The turn ends with Output limit reached. Ask for smaller steps, for example writing a large file in parts.
The model's response stream kept breaking before it finished
The provider's reply broke off twice in a row before it was complete. Retry the turn, or pick another model.
The provider sent the same incomplete reply twice
The provider's reply broke off, and when Lookout asked it to go on it sent the same words again. Lookout keeps them once and stops asking, since a third request would get them again. Retry the turn, or pick another model from Retry's chevron.
MODEL declined to answer this
The model refused to answer the request, or stopped partway through an answer and declined to go on: then the answer above the notice is not complete, and the notice's mark is a warning, not a failure. Tool calls in a declined answer never run, since one may be cut off partway; each says it wasn't run. The provider's own words, when it gave any, are quoted under the notice with their links, such as its category and reason, or a filter's message. Rephrase the request, or pick another model from Retry's chevron.
The notice names the provider that declined (PROVIDER declined this request on MODEL). What a provider declines is often something new in the chat, such as a file the agent just read, and every later request carries it again. Retry without these N items takes the entries added since the last request that provider answered out of its context and runs the turn again; another provider's models still read them. The model still learns whether each tool call among them ran and succeeded, never what it returned. The entries stay in the chat, dimmed and marked Removed from context, with Undo. To take any other entry out, right-click it and choose Remove from context. An agent's chat, a subagent, and a chat an agent or an orchestrator such as Claude Code started do this once by themselves, or go on with a fallback model on another provider, and say so in a row. They wait for you instead when what was declined holds your own message, and a chat someone else started waits for you on a turn you typed or retried there.
PROVIDER refused this request as a third-party app
The provider read Lookout's request as one from a third-party app, which a plan serves only from paid extra usage, and with extra usage off it refused it. Nothing was billed: Lookout never spends extra usage. Lookout's requests are built not to read this way, so this is a bug in Lookout. How to report, under the notice or in the stop's details, opens Collect a report; quote the Request ID from Details. A retry on the same provider fails the same way. A chat with fallback models goes on by itself on the next one another provider serves, for that turn only; its next turn starts on its own model again. A subagent or a workflow agent does the same through its chat's fallback models or its call's models, for that run only. Otherwise, when the chat may use a model from another provider, the notice leads with Continue on that model and Retry waits in its menu; with none, Retry leads.
Refused whatever the sign-in
The provider refused the request for a reason a new sign-in won't fix, so the notice offers no Sign in again and the chat doesn't wait for one:
When the chat may use a model from another provider, the notice leads with Continue on that model.
Compaction notes
The Context summarized and Context cleared rows can carry a note:
| Note | What it means |
|---|---|
Still over the context budget after summarizing (or after clearing) | Compaction didn't free enough room. If the chat keeps filling up, the turn ends with Context full. |
A summary was rejected and redone | A summary failed Lookout's checks and was written again. Nothing to do. |
A summary could not be written, so only tool output was cleared | Lookout freed room by clearing tool output only. The agent can read the cleared output again. |
The provider rejected the request (PROVIDER): its words
The provider found the request malformed or over one of its limits, and its own words follow, such as At least one of the image dimensions exceed max allowed size for many-image requests: 3000 pixels. Lookout fits every image to
the limits its provider declares before sending, so a rejection names a limit Lookout doesn't know yet, or a part it
couldn't read. An agent's chat, a subagent and a workflow agent take the tool results added since the provider's last
accepted request out of their context once, as Retry without these N items does, and go on; a workflow agent
that still can't go on stays continuable, and the run keeps the provider's whole message. Elsewhere, Retry without
these N items does the same by hand. If it keeps happening, collect a report.
When its words say a tool call has no result right after it, or a result answers no call, nothing added since is the cause: Lookout sends every call with its result, closing one that never got its own as interrupted. So it takes nothing out, and it never sends that same request again: a Retry of the same conversation ends at once and says so. Send a message or pick another model, and collect a report.
Other messages from a provider
When a provider refuses a request for any other reason, the notice shows the provider's own message. Retry, or pick another model. If it keeps happening, collect a report.
The machine's disk is full
Lookout couldn't write on the machine the chat runs on, because its disk is full. The chat stops with the machine's
disk is full, a call to that machine reads MACHINE answered with an error: database or disk is full, and the kind
a connected app gets is disk_full. The words name no size, since you may read them on another machine than the full
one. Free space on that machine, then retry the chat: another model or provider won't help. Archived chats'
worktrees are often what fills it: lookout worktrees reclaim --on MACHINE --dry-run lists what Lookout can remove
there and the space each holds (Free the space archived chats' worktrees hold).
In the message box
MODEL isn't available: REASON. Choose a model
The chat's model can't run, so the message box says why. Use MODEL beside it switches the chat to the same model on another provider you have (Use Haiku 5.5 on your API key, billed per token), else to the model a new chat would start on. A switch that names billed per token moves the chat onto a provider that charges for each token, and happens only when you click it. While the chat's stopped turn offers Continue on, the box says only why, with no Choose a model and no Use: Continue on is the move, and an empty send runs it. A failed turn whose model can't run leads with Continue on another model, never a Retry on the one that can't. The reasons:
| REASON | What to do |
|---|---|
PROVIDER isn't connected | Connect the provider. PROVIDER is the company (OpenAI, Anthropic), or for Anthropic its kind of access (your Claude plan, your API key). |
PROVIDER is signed out | Sign in to it again in Settings › Providers. |
PROVIDER needs a sign-in | The sign-in expired: click Sign in again on the provider's row in Settings › Providers. |
PROVIDER refused the sign-in | Click Sign in again on the provider's row in Settings › Providers. |
PROVIDER has no active plan (renew it, or remove the key) | The provider says the plan was canceled or expired. Renew it with the provider (Renew plan on the account in Settings › Providers when Lookout knows the page), or remove the key or sign out there. A subagent or a delegated chat on that model is refused with the same sentence. |
it isn't on your plan | Pick another model. |
PROVIDER refuses Lookout's client | Pick another model: the provider's free tier stopped serving Lookout (A free tier). |
not enabled for this key on Anthropic | Pick another model: the key was added with --models naming others. |
it isn't available right now | Pick another model. |
Dictation
Dictation failed
The toast's title says what went wrong:
| Title | What to do |
|---|---|
| Microphone access is off | Allow Lookout to use the microphone. In the Mac app, Open Settings on the toast opens Privacy & Security, Microphone; in a browser, allow it in the site's settings. |
| No microphone found | Connect a microphone. |
| The microphone didn't start | Quit the app that uses it, then try again. |
| Dictation kept | Lookout didn't answer, so the take waits on this Mac. Click Retry once Lookout is back (it sends the same recording), or find it under Recent dictations with a right click on the microphone. |
| Dictation kept, not transcribed | The toast says why, and the take waits on this Mac. Downloading the speech model (40%). Try again in a moment. means the first dictation is downloading the speech model: wait for it, then click Retry. |
In the Mac app
Lookout could not start
The app couldn't start its server, and quits after this dialog:
| The dialog says | What to do |
|---|---|
| Another Lookout server is running | Quit other copies of Lookout, then open it again. |
Lookout's bundled runtime is missing or Lookout's bundled server is missing | Reinstall the app. |
Lookout server did not start | Open it again. If it fails again, read server.log (see Logs). |
When the dialog follows an update, it reads Lookout VERSION couldn't start and offers Go Back to the version you had before. Lookout then won't install the version that failed again.
The update didn't install
The restart to update failed, and Lookout is still running the version it had. Settings › General › Software update has the details.
In the terminal
The lookout command starts each error with lookout: and ends with an exit code.
not signed in on this machine: run lookout login
This machine isn't on your Lookout account. Run lookout login. Exit code 4.
On a Mac with the Lookout app, open the app and sign in there instead: while it runs signed in, lookout works through it with no login of its own (On a Mac with the app).
the Lookout app (pid N) is signed out of your Lookout account
The Lookout app runs on this Mac, but it isn't signed in to your account, so lookout has no account to go through. Sign in from the app. Exit code 4.
lookout VERB is the USER's to run
An agent ran a command from its chat's Shell that only you run, such as rename or providers sync. Run it yourself in the app or a terminal. Exit code 2.
lookout VERB takes this machine's own account keys
On a Mac with the Lookout app, devices, recovery-key, remove and choosing a provider's copy change your account's devices or keys, which only the app does. Use the place the message names in the app's Settings. Exit code 4.
this machine's account session ended: run lookout login
Your account no longer holds this machine's session: it was revoked, expired or replaced. Run lookout login. Exit
code 4.
this machine was removed from your account
Another of your devices removed this machine from your account. Run lookout login to add it again. Exit code 4.
the Lookout account refused this machine's signature
The account couldn't verify this machine's request, most often because the machine's clock is off. Set the clock right, then try again. The machine stays signed in. Exit code 1.
MACHINE is offline
The machine you named with --on can't take the call. The message says it is offline, asleep, signed out
or degraded, and why, such as vps-1 is offline (Lookout quit 3 min ago). Check it with lookout machines, and
see Check a machine's status. Exit code 5.
A Linux machine that runs Lookout as the installer's service starts it again by itself after it stops, for an update
or a restart. Until it is back, a call reads vps-1 is offline (went down to restart 5 s ago); it starts again by itself: try again in about 30 s. An agent's Delegate or Steer to it waits up to a minute for it and then goes on.
MACHINE answered with an error
The machine took the call and failed it there: what follows the colon is its own message, such as database or disk is full (The machine's disk is full). A machine that never got the call reads MACHINE didn't answer instead. Fix what the message says on that machine, then try again.
cannot reach the Lookout account service
This machine couldn't reach your Lookout account. The message reads
cannot reach the Lookout account service at ADDRESS, or names the service and says it did not answer within 10s or
failed (HTTP 502); try again shortly. Check the connection, then try again. Exit code 6.
unknown command "WORD"
The first word isn't a lookout command. A single word is never sent as a prompt: when a command is close, the
message asks if you meant it, and lookout exec "WORD" sends the word as a prompt. lookout --help lists the commands.
Exit code 2.
a prompt is required
lookout exec needs a prompt: pass one, pipe it in, or pass - to read it from stdin. Exit code 2.
unknown thread "ID"
No chat on this machine has that ID. On another machine the message reads no thread ID on MACHINE. Copy ID in a
chat's menu copies its ID, and lookout sessions lists a machine's chats. Exit code 2.
Exit codes
| Code | Meaning | What to do |
|---|---|---|
0 | The command succeeded; a run's observed turn ended normally. A successful read does not approve work or assert completion. | Nothing. |
1 | The turn or the command failed; stderr says why. | Read the error, then run it again or resume the chat. |
2 | The command line was wrong: an unknown command or flag, a missing value, an unknown chat. | Run lookout VERB --help for its usage. |
3 | The model's plan ran out for now. | Wait for the plan to reset, or run with another model or account. |
4 | A sign-in is missing: the provider's, or this machine's on your Lookout account. | For a provider, sign in again in Settings › Providers (lookout providers sync brings it to another machine); for this machine, run lookout login. |
5 | The machine is offline, asleep, signed out or not answering. | Check it with lookout machines, then try again once it is online. |
6 | This machine could not reach the Lookout account service. | Check the connection, then try again. |
130 | The run was stopped (Ctrl-C, or lookout stop). | Resume the chat to carry on. |
In another app
A connected app gets a refused call back as an error with a code and a message, and most often next: what to
do instead, often the tool to call. Where calling again can help, retry says when: soon, later, or check_first
when the call may already have run.
| Code | What happened |
|---|---|
lookout_unreachable | Lookout isn't running on that machine, or is still starting. Call again in a moment. |
machine_unavailable | The machine is offline, asleep, signed out or didn't answer in time. lookout_machines shows when it is back. |
network_unavailable | The Lookout account service isn't answering, or this machine can't reach it. Call again later. |
machine_not_found | No machine on your account has that name. |
signed_out | This Lookout isn't signed in to your account. |
busy | A running turn, a compaction or a restore holds the chat. Wait for it with lookout_check. |
not_found | No chat or project has that ID (or, for a chat, starts with it). lookout_fleet lists the chats. |
ambiguous | Several chats' IDs start with that short ID. candidates lists each one's full ID, title, lane and state: call again with the one you mean. |
agent_one_chat | That project or folder is a Lookout agent's, and an agent keeps one conversation: no new chat starts there. threadId is its chat: send to it with lookout_steer. |
unknown_model, model_unavailable | That model doesn't run now. lookout_models lists the ones that do. When a provider billed per token serves the same model, next names its exact ID: call again with it only if you want that spend. |
plan_spent | That model's plan is spent until resetsAt (planSpent), and the chat has no onQuota policy. openModels lists the models whose plans are open now: pass one, or onQuota: "wait" to wait for the reset (a lookout_retry waits with wait: true). |
grant_needed | You haven't given that app the permission the call needs on this machine. setting names the place: Add projects (how) or Configure agents (how) in Settings › App access. For a folder, closest names the projects nearest it until then: pass one's ID. |
outside_grant | The folder is outside what you let that app add as projects. allowed lists where it may. |
outside_roots | The MCP server was started with allowed folders, and this one is outside them. A chat's cwd must sit inside its project or under those folders too. closest names the projects nearest it: pass one's ID. |
title_too_long | A rename over 40 characters, a sidebar title's limit, from anyone but you (lookout_configure, an agent, a model); your own renames go to 120. Nothing in the call changed: pass 2 to 6 words and put the goal in a message. |
invalid_argument | The call is wrong as the message says. |
See App access to connect one, and MCP tools for every tool.