Skip to main content
This page gets Scout running on your machine with three context providers: the web, the filesystem (the Scout repo itself), and a CRM (people, projects, notes) backed by Postgres.

Prerequisites

1

Clone and configure

git clone https://github.com/agno-agi/scout && cd scout
cp example.env .env
Open .env and set OPENAI_API_KEY. Everything else has sensible defaults.
2

Start Scout

docker compose up -d --build
First run pulls the base image and builds the Scout container. Takes a minute or two. Subsequent starts come up in seconds.
3

Verify it's running

curl http://localhost:8000/health
Expect {"status":"ok"}. Connection refused means the container is still starting. Check docker compose logs -f scout-api and wait for the Agno banner.

Connect to AgentOS UI

Open os.agno.com and log in. Click Add OS, choose Local, enter http://localhost:8000, click Connect. Try the pre-configured prompt: “Which contexts are you connected to?” Scout reports back web, filesystem, and CRM.

What you have now

Scout is running with three context providers. Each surfaces as a query_<id> tool (plus update_<id> where writes are allowed):
ProviderTool(s)Backed by
Webquery_webParallel’s public MCP (keyless). Set PARALLEL_API_KEY to upgrade to the Parallel SDK.
Filesystemquery_fsThe Scout repo itself, read-only.
CRMquery_crm, update_crmYour own contacts, projects, and notes in the local Postgres.

Try it

Ask Scout to put each provider to work:
“Look up the latest pricing for Anthropic’s models.” hits the web.
“Search the repo for where context providers get registered.” navigates the filesystem.
“Save Sarah Chen as a contact, she’s the head of platform at Acme.” writes to the CRM.

Next

Connect to Slack →