Summary

Scout is an open-source "Company Brain" and "AI Operating System" tackling information fragmentation. It navigates live sources (web, Slack, Drive) to assemble context on demand, automatically building a persistent wiki and CRM. This provides AI agents and users with actionable, centralized company knowledge.

How It Works

Scout uses "navigation over search," exploring information sources contextually like code agents navigate filesystems. A single agent interfaces with specialized "Context Providers" (e.g., Web, Slack, CRM) via natural-language tools (query_, update_). This architecture abstracts source-specific complexities (pagination, formatting) to sub-agents, preventing main agent context pollution and performance degradation.

Quick Start & Requirements

• Install: Requires Docker Desktop. Clone repo, copy example.env to .env, set OPENAI_API_KEY, run docker compose up -d --build.
• Prerequisites: Docker Desktop, OpenAI API Key. Optional: GDrive credentials, Slack Bot Token.
• Access: Local instance at http://localhost:8000 (via os.agno.com).
• Docs: Guides for Slack, GDrive, MCP, and Git-backed wikis are included.

Highlighted Details

• Dynamic Knowledge Base: Automatically builds and maintains a company wiki and CRM, linking discovered entities.
• Diverse Context Providers: Integrates Web, Workspace (repo code), CRM, Wiki, Voice (style guides), Slack, Google Drive, and MCP servers.
• Schema-on-Demand: Generates/updates data schemas (CRM, wiki) from natural language instructions.
• Agentic Navigation: Prioritizes contextual exploration over bulk data ingestion.

Maintenance & Community

Built on Agno and AgentOS. Upcoming features include GitHub and Gmail providers. Specific community channels or core contributor details are not detailed in the README.

Licensing & Compatibility

The repository's license is not explicitly stated, a critical omission for adoption. Production deployment requires significant security configuration, including JWT verification key setup.

Limitations & Caveats

Production deployment mandates JWT verification key setup for secure API access; opting out is discouraged. The default filesystem wiki is ephemeral; a Git-backed wiki is recommended for persistence. Initial production deployments may require specific setup steps. The absence of a stated license poses a significant adoption risk.