- Question
- From Slack
- From the web
- ScoutOne agent
- query_<source> tools
- Context providersA sub-agent per source
- Slack
- Drive
- Wiki
- CRM
- MCP servers
- Answer
- Grounded in sources
- Wiki and CRM kept up to date
Scout is a company-intelligence agent. Instead of chunking and embedding everything up front, it navigates a company’s sources - Slack, Google Drive, a wiki, a CRM and MCP servers - and keeps its own wiki and CRM up to date as it learns.
Built to run in your cloud. Any model, Postgres for its wiki and CRM, JWT auth in production, and Slack as its home - each thread is a session. CRM writes are locked to Scout’s own schema by the database, not by a prompt.
What I built
- The architecture: one agent, one
query_<source>tool per source, each backed by its own sub-agent. - Context providers in Agno - including Slack, Gmail and Calendar - with live streaming of sub-agent work.
- Scout’s first evaluation suite, and the migration onto Agno’s shared context-provider library - which also fixed a user-ID leak into CRM rows.