Repositories

flowchart TB
  Docs["respire-docs: canonical contracts"] -.-> CLI["respire-cli"]
  Docs -.-> Server["respire-server"]
  Docs -.-> Client["respire-client2"]
  Core["respire-core"] -->|staticlib + C ABI| CLI
  CLI -->|Pinned infrastructure app crate| Server
  Client -->|Local Runtime RPC and host actions| CLI
  Site["respire-site"] --> Website["Website"]

Repository	Purpose
respire-cli	CLI plus protocol, crypto, storage, app and safe SDK crates
respire-server	Authentication, encrypted storage, HTTP API and deployment
respire-client2	Go/Wails desktop client, embedded UI and local Runtime management
respire-docs	Documentation and canonical contracts
respire-site	Marketing website source
respire-releases	Release information and matching binary assets
respire-core	Model execution and memory operations; binary SDK
respire-memtool	Tauri desktop quick-capture companion; see the memTools guide

AI tool plugins

Eleven host plugins connect Respire to AI tools. The portable respire-general package covers Agent Plugins 1.0 clients that have no dedicated adapter. See the plugin guides for installation and usage.

Repository	Host / use
respire-zcode	ZCode
respire-kimi	Kimi Code
respire-dimcode	Dim
respire-qoder	Qoder
respire-workbuddy	WorkBuddy
respire-hermes	Hermes Agent
respire-codex	Codex
respire-pi	Pi
respire-dsh	DSH
respire-magpie	Magpie
respire-minimax-code	MiniMax Code 0.4+ (SessionStart / UserPromptSubmit / Stop hooks)
respire-general	Any Agent Plugins 1.0 client (skill + MCP; no hooks)

CLI/server do not check out Core source or use a Core submodule. The CLI pins an SDK manifest; the server pins the infrastructure app crate revision and uses the same SDK boundary.

Change	Coordinate
Core ABI / SDK	Canonical contract, validated SDK manifest and consumer lock
Infrastructure app	CLI source revision and server dependency
CLI output	CLI contract and desktop consumers
Desktop Runtime	CLI release metadata, platform target and runtime resources