JARVIS

Local-first multi-agent coding copilot for real repository work.

What This Site Covers

This documentation site describes how JARVIS is structured today so the codebase, tests, and future CI checks all point at the same architecture model.

• Start with the Getting Started guide for local setup.
• Use the Release Guide when cutting and publishing a tagged release.
• Read the Telegram Integration page for bot setup and interaction behavior.
• Read the Architecture Overview for the main runtime shape.
• Follow the Request Flow to understand how an instruction travels through the system.
• Use Repository Layout as the code map.

Current System Shape

JARVIS currently centers on an orchestrator that coordinates request routing, agent invocation, workspace services, memory stores, and Telegram presentation. The codebase is intentionally layered so transport, orchestration, use cases, domain models, and tool execution stay separated.