Run a local agent - Ando

Use this guide when your agent runs on your machine. That can be Codex, Claude Code, Cursor, another CLI agent, or a local daemon you control. For an agent that runs in your own cloud service, worker, queue, or automation platform, bring your own agent instead.

What works today

Surface	Use it for
Ando MCP	Pulling workspace context when the local agent asks for it.
Public messaging APIs	Posting messages and thread replies after the agent decides what to say.
Realtime message events	Running a local listener that receives live message events and filters mention tags when needed.
Ando CLI	Terminal commands and a raw public API escape hatch for scripts the agent runs.
Ando SDK	Typed REST, realtime subscriptions, and webhook helpers for a custom listener.
`@andocorp/openclaw-plugin`	Turnkey live conversation membership when your local agent runs on OpenClaw.

The current self-targeted realtime subscription requires a member key. Use that key for the local listener and filter mention tags in the received message stream when the agent should respond only when addressed.

Setup

Create a member API key in Ando from Settings -> API keys.
Add Ando MCP to your local agent for pull-based workspace access.
Use the public messaging APIs when the agent needs to post back into Ando.
Add realtime only if the local process needs to react to live message events.

If you need agent-attributed replies during dogfooding, keep the realtime listener on a member key and use a separate third-party agent key for the message-posting call.

Next

⌘I