architecture.md

How omp-agents works

The server's design, its protocols, and its HTTP API, one file per subsystem in docs/architecture/. Read this list, then only the file for the subsystem you need. For installation, see the README; for the interface, see Using omp-agents; for where each file lives and what it does, see Code layout.

• omp modules
• Transcripts
• Terminal sessions
  • Why the server joins every terminal session
• Dashboard sessions
  • Session keepers
• Session processes
  • The idle stop
• Replay from here
• Socket requests
• Ask about this
• Desktop shell
  • Packaging and releases
• Terminal panel
• Plan quota
• Analytics
  • Context sources
• Routines
  • One server runs the unattended work
  • Isolation sandboxes
• Scheduled sends
• Projects
• Pins
• User notes
• Notifications
  • Session notifications
• Merges, and the cleanup after one
• Review drafts
• Updating the dashboard
• Settings sync
• HTTP API
  • Files, git, and conversations
  • Pull requests
  • Source control, sync, worktrees, and workspaces
  • Models, skills, and session starts
  • Linear tickets
  • Integrations
  • MCP servers
  • Providers
  • Google Calendar
    • New and local events
  • Gmail
• Front-end components
  • Session visuals