// the find
agno-agi/scout
Open Source Company Brain
Scout is an agent built on Agno/AgentOS that plugs into Slack, Google Drive, a wiki and CRM it maintains itself, and arbitrary MCP servers to act as a company knowledge layer. It's aimed at teams who want an internal assistant that can answer questions across fragmented company data and write back structured notes, rather than another RAG-over-everything chatbot.
The navigation-over-search bet is a real architectural choice, not a slogan: instead of chunking and embedding Slack/Drive into a vector store, it does the ls/grep/open-file style traversal that coding agents use, which avoids a lot of the garbage retrieval that plagues naive RAG. The context-provider pattern (one query_/update_ tool pair per source, each backed by its own sub-agent that owns pagination, cursors, and thread quirks) is a sane way to keep a multi-source agent's tool surface from rotting the main agent's context. Production defaults to JWT-based RBAC rather than leaving the DB open on a guessable Railway URL, and the eval suite is split into no-LLM wiring checks, behavioral cases, and LLM-judged quality tiers, which is more rigor than most agent repos bother with.
It's tightly coupled to Agno's hosted AgentOS control plane (os.agno.com) for auth, tracing, and even the chat UI — there's no way to actually talk to Scout without logging into their service first, which is real lock-in for something billed as open source. The README's provider table lists GitHub, Gmail, and Calendar as near-term, but they're only 'built and verified on feat/slack-interface' and not actually in this release, so the integration list overstates what ships today. The default wiki backend is filesystem-based and wipes on every container restart, meaning the thing's own long-term memory evaporates unless you do the separate Git-backed wiki setup — a strange default for a product whose pitch is persistent memory. Getting it running at all needs Docker, an OpenAI key, and an AgentOS account just to send one chat message; there's no bare CLI path for someone who just wants to kick the tires.