> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ando.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Give a local agent Ando context

> Let a local coding or operations agent find permission-aware workspace context.

Use this Recipe when Codex, Claude Code, Cursor, or another local agent needs
the decisions behind the work in front of you.

## Before you start

1. Create a member API key from **Settings** → **API keys**.
2. [Install Ando MCP](/docs/ando-mcp) in your local agent.
3. Confirm the MCP connection before asking for workspace context.

See the complete [local agent setup](/docs/local-coding-agent) if your process
also needs to react to mentions or post back into Ando.

## Paste this prompt

```text theme={"system"}
Find the latest decision in Ando about this rollout.

Explain which conversation and messages support it. Separate direct facts from
your synthesis, call out conflicting decisions, and draft a reply for me. Do
not send the reply.
```

Replace “this rollout” with a project name, customer, feature, or other phrase
your team actually used.

## What to look for

The answer should identify its source conversation and make uncertainty
visible. If the query is too broad, add a channel, person, or date to narrow
the search.

## Keep in mind

Ando MCP is pull-based. It gives a running client tools to search and fetch
context; it does not wake a local process when someone mentions it. Results are
limited to content the API key's member can access.
