Sage Documentation
This site documents the current repository as it exists today. It is organized around the real entry points in examples/, app/server/, app/desktop/, sagents/, and mcp_servers/.
Who This Is For
- Users who want to run Sage locally
- Contributors who need to understand the runtime and application layout
- Integrators extending Sage through tools, skills, APIs, or MCP servers
Start Here
- Applications for getting started, Web (incl. Docker), Desktop, CLI, TUI, and Chrome extension
- Core Concepts for the runtime model
- Architecture for repository and subsystem boundaries
- Configuration for environment variables and deployment knobs
- API documentation for HTTP and runtime interfaces
Common Reading Paths
I want to run Sage locally
Read:
I want to extend the runtime
Read:
I want to integrate with the server
Read:
- Applications
- Configuration
- API documentation (includes HTTP API Reference and the legacy Python notes)
- OAuth2 Lage Integration Guide
Documentation Map
- Applications: getting started, Web, Desktop, CLI, TUI, Chrome extension
- Getting Started
- Web Application (manual stack + Docker Compose)
- Desktop
- CLI Guide · TUI Guide
- Chrome extension
- Core Concepts: sessions, agents, tools, skills, flows, and sandboxing
- Architecture: how the codebase is organized (with sub-chapters)
- App layer: Server · Desktop · Other entries
- sagents core: Overview · Agent / Flow · Session / Context · Tool / Skill · Sandbox / LLM / Obs
- Configuration: runtime environment variables and storage settings
- MCP Servers: built-in MCP servers and how they fit into the platform
- API documentation: navigation hub for HTTP vs legacy Python API
- HTTP API Reference: backend endpoints aligned with
register_routes; the sidebar lists subpages - Python runtime API:
SAgentand related types aligned withsagents/, not the main HTTP app
- HTTP API Reference: backend endpoints aligned with
- Knowledge Base Guide: knowledge base module architecture, ingestion, retrieval, and Agent integration
- Memory: memory, retrieval, and memory-search workstream
- Solution Playbooks: presales documents for concrete business scenarios
- OAuth2 Lage Integration Guide: restored OAuth2 integration guide from historical docs
- Development: contributor workflow and source locations
- Troubleshooting: common startup and environment issues
Current Product Surfaces
Lightweight examples
sage run/sage chat/sage doctor: development CLI entry pointsexamples/sage_demo.py: Streamlit demoexamples/sage_server.py: standalone FastAPI example service
Main application server
app/server/main.py: primary FastAPI application entry pointapp/server/web/: Vue 3 + Vite web client
Use this path when you want the full product surface instead of a demo.
Desktop app
app/desktop/entry.py: desktop bootstrap entryapp/desktop/core/main.py: desktop-local FastAPI backendapp/desktop/ui/: desktop UI
Use this path when you need the packaged desktop experience rather than the browser-based app.
Core runtime
sagents/sagents.py:SAgentstreaming runtime entrysagents/agent/: agent implementationssagents/tool/: tool system and MCP proxy supportsagents/skill/: skill loading and executionsagents/utils/sandbox/: sandbox abstractions and providers
Documentation Principles
- This documentation prefers current source accuracy over historical completeness.
- Historical migration notes and duplicate site pages have been removed from the primary doc set.
- The root repository
README.mdremains the marketing and project overview document; this site is the technical source of truth.