Surfaces
App access
Drive Lookout from another app over MCP, or from Claude Code with its plugin.
Lookout runs an MCP server, so another app can start, steer and watch chats on your machines. Each app signs in with your Lookout account and gets only the tools you allow. Settings › App access lists these apps. What the agent itself uses is on Settings › Connectors (Connectors and skills).
Server address
https://lookout.arcadia.is/mcpConnect an app, in Settings › App access, shows it as Server URL with Copy.
The hosted address serves the Lookout account that runs it: one Mac answers it, and only that Mac's account can approve an app there. Connect an app offers it only to that account. Any other account sees the local ways instead: the Claude Code plugin with the app on the same machine, and any local command the marketplace lists. When Lookout can't tell whose the address is, it shows the address with that line.
Connect an MCP client
The app then shows under Apps in Settings › App access. The server signs clients in with OAuth (scope mcp).
Connect Grok
Grok reaches Lookout only through the hosted address, so only the account that runs it can connect Grok.
Let apps reach this Mac
The Mac that answers the server address signs apps in with your account, and serves your account alone. Turn it on once:
Connect an app asks for the same password first when the switch is still off. Lookout keeps the credential on this Mac and never shows it; your password isn't stored. When your account no longer takes it, the row says so with Set up again. Turning the switch off revokes it, and the apps that reach this Mac lose access until you turn it on again. Turning it on again asks connected apps to sign in once more.
What a connected app can do
Its tools start chats and send them follow-ups, check, stop, retry and answer them, read the files they changed, merge or push their worktrees, manage projects, list models and plan usage, and list and tune your machines. A chat they start can wait out a used-up plan, or move to models they list, and go on by itself (MCP tools). Every refusal carries a code and the call to make next.
What an app sends shows under its name, never as yours. In a chat the app started it leads the chat, and the agent follows it as it follows you; in an agent's chat, or a chat someone else started, its words are a request.
A chat an app started can ask that app a question while it keeps working: the chat's asking names it, the Claude Code
plugin's watcher prints an asks line, and the app answers with lookout_steer, which the chat reads at its next step.
A call can name the machine it runs on. A new chat can take machine: "auto", which puts it on the machine with the
most headroom that runs its model; the chat stays on that machine. A machine's limits hold
the chats connected apps start there until it has room.
Choose the tools an app can use
The change applies within 5 minutes, on the app's next token refresh. Lookout enforces the choice; the app's own tool switches don't change it.
Let an app add projects
An app works in the projects you already have. To let one add a folder of yours as a project, or clone a repository into one:
Every connected app has its own choice, and so does each client on this Mac, such as Claude Code, once it has asked:
each has one row under Apps.
Each starts Off. Lookout enforces it on this Mac: no app can allow itself or another, and the agents in the chats
an app starts can't add projects through it. An app that asks without it is refused with grant_needed, which names
this place.
Let an app set up agents
An app can't change your agents. To let one set an agent up for you (its name, description, instructions, section, projects, fallback models, and whether its chat shows every step):
Every connected app has its own switch, and so does each client on this Mac, such as Claude Code, once it has asked.
Each starts Off. An agent's limits, allowed models, pause, lock and memory switches stay yours in
the app: no app sets them, whatever its switch says. Every change an app makes names it, in the agent's transcript
and in Lookout's action log. An app that asks without it is refused with grant_needed, which names this place.
Revoke an app
It loses access at once. Connect again from the app to undo it. An app whose sign-in ran out shows Expired, with Reconnect in its menu. Sign out everywhere else in Settings › Account revokes every app's access too.
Claude Code
The Lookout plugin for Claude Code drives your account from a Claude Code session: it hands tasks to Lookout agents, steers chats, and reads machines and plan usage.
Install the plugin
In Claude Code, run:
/plugin marketplace add arcadia-eng/lookout-marketplace
/plugin install lookout@lookout-marketplaceThe plugin runs with Bun: the copy Lookout ships, or Bun installed on the machine.
How it connects
On a machine with the Mac app or the lookout command, the plugin uses that Lookout. While Lookout isn't running, each
call says so, and the first call after it starts works, with no reconnect. On a machine with neither, it uses the hosted
server, which serves the Lookout account that runs it: run /lookout:login and sign in with that account in the
browser it opens. Any other account installs the Lookout app or CLI on the machine instead. If /mcp then shows the
lookout server as failed, reconnect it there. When Lookout updates, a session that is already open
moves to the new version's tools at its next call, with no reconnect.
What the plugin adds
| Part | What it does |
|---|---|
/lookout:status | Your chats, machines and provider quotas |
/lookout:delegate <brief> | Hands a task to a Lookout agent and returns its result. Takes --model, --effort, --machine, --lane, --ephemeral, --background and --direct |
/lookout:steer <threadId> <message> | Sends a follow-up into a chat |
/lookout:machines [name] | Lists your machines, and picks one |
/lookout:login | Signs the plugin in to your Lookout account, on a machine without the Mac app or the lookout command |
lookout:worker | A subagent that delegates a bounded task to a Lookout agent, waits, and returns the result |
| Skills | machines, models, orchestrate, review and vps-workers |
MCP server lookout | The same tools as Lookout's MCP server |
| Monitor | Runs as long as each interactive session does and tells it when a chat it follows settles, asks for a decision, waits for its plan or lands, with nothing to restart. The orchestrate skill adds the chats and lane prefixes it follows |
| Session start | Tells a new session when Lookout already has chats running |
| Status line | A subagent status line with the same count of running chats |