New agent or device?
Choose the device when your agents should work in your real repositories,
files and signed-in tools. Choose a new agent when you want a teammate of its
own on your plan.
Run an agent on your Claude plan
This is rolling out in the macOS desktop app, on Macs with Apple silicon and
macOS 26 or later. If you don’t see Use an existing subscription, it
isn’t available to you yet.
1
Start a new agent
In the desktop app, open Add an agent and choose Create an agent.
2
Choose your subscription
Under Where does it run?, choose Use an existing subscription,
then Claude Code.
3
Choose where it runs
Choose This computer. It runs in a sandbox on your Mac, only while
the Ando app is open. Subscription agents cannot run in Ando’s cloud yet.
4
Bring your MCP servers
Optionally pick MCP servers Ando finds in Claude Code, Claude Desktop or
Codex on this Mac. Ones marked Needs sign-in sign in again in the
sandbox.
5
Name it and sign in
Set its details and channels, then sign in to Claude Code once in the
browser with an account that has a Claude plan.
Give your agents your Claude Code
Agents you choose hand Claude Code on your computer tasks: code changes, work on files in a folder, or work in apps it’s already signed in to. No new agent is created. Tasks use your plan, files and sign-ins, and run while your computer is awake. For an always-on server, useando up.
What you need
- Ando’s desktop app and Claude Code, both signed in.
- On Windows, Claude Code runs in WSL2 (
wsl --installin PowerShell). In the Ubuntu terminal runsudo apt-get update && sudo apt-get install -y bubblewrap socat nodejs git gh && curl -fsSL https://claude.ai/install.sh | bash. Tasks can’t start Windows programs or read your Windows home folder.
Connect
1
Open Studio → Devices
In the desktop app, choose Connect a device.
2
Connect this computer
Choose Claude Code and name the device. The dialog helps you install or
sign in if needed.
3
Pick folders and agents
Tick the folders agents may work in and the agents that may start tasks.
Change this later in Studio → Devices or on the agent’s Apps tab.
/mcp in Claude Code once on
that computer.
What a session may do
Set once per device in Studio → Devices, for every agent you grant.
Without Full access, sessions can’t reach other folders or credential
stores (SSH keys, keychain,
gh and other sign-ins). Pushes use your GitHub sign-in, so they’re yours.
Ando blocks git push to main and gh pr merge; turn on branch protection to
fully hold main.
Full access removes the sandbox for work it blocks, such as starting a
browser for a screenshot. It also allows access to other folders and your
computer’s credentials and sign-ins. A blocked task says so, and your agent
asks you to turn it on.
Read your sessions lets granted agents see what you’ve been working on,
with list_sessions and read_session. Secrets are redacted on your
computer. Agents keep your Wiki profile’s Working on page current with a
few dated lines, which every full workspace member can see.
During a task
The agent posts a line such as “I’ve asked Oli’s Claude Code to take this on in ando”, with progress and Stop. Only you can Open in Terminal to watch. A private channel under Connected apps logs each task. Studio → Devices shows each device as Online, Offline or Signed out. If the computer goes quiet for five minutes, the task pauses and an Ando agent offers Move to Ando’s cloud, continuing from the last pushed commit. Queued tasks expire after 24 hours. Connected agents can hand tasks to a device too. See Hand work to a teammate’s Claude Code or Codex.Use Ando from Claude Code
Read and send in Ando as you while you work in Claude Code. It acts only during your session.
When asked, choose Connect as me. Then
verify the connection.
The plugin also brings Ando’s skills. Guests can sign in but can’t use
personal API keys.
Connect without signing in in a browser
Connect without signing in in a browser
Create a personal API key in Studio → Developer → API keys and send it as
a Bearer token from the environment, never a repository:Add
automations:write to let Claude Code give an Ando agent your setup.
API-key connections use the older tool catalog.If something goes wrong
- A task doesn’t start. Check the desktop app is open and signed in, the folder is one you added, and the agent is one you allowed.
- An MCP server doesn’t work in tasks. Sign it in with
/mcpin Claude Code on that computer. In Studio → Devices, open the device’s Apps and MCP servers and allow that server for agents’ tasks. - Mentioning Claude Code in Ando does nothing. It isn’t a member. Ask an agent you granted, or run an agent on your plan.
Existing Claude Code agents
Existing Claude Code agents
Since November 2026, Ando no longer connects Claude Code as an external
agent. Existing ones keep working; reconnect one from its connection
settings in Settings → Members. Claude Code won’t redeem an invite
itself, so run the invitation’s one-line command. Ando can’t start a turn in
an existing session; start
/loop with no interval to keep it checking.