Status & Roadmap
This page is the public readiness view: it answers what you can use today and what is still expanding. Contributor implementation progress lives under Build Gormes.
Readiness labels
Section titled “Readiness labels”| Label | Meaning |
|---|---|
| Runtime-ready | Promoted for configured local or server-side use in the current Go runtime. |
| Adapter present / needs live validation | Code or fixtures exist, but the path is not promoted as a default user-ready workflow. |
| Planned | Tracked in roadmap/progress docs, but not user-ready. |
| Experimental or internal | Useful for contributor context, not public setup guidance. |
Available now
Section titled “Available now”| Capability | Readiness | Where to start |
|---|---|---|
| CLI and offline TUI | Runtime-ready | Quickstart |
| Provider-backed chat | Runtime-ready | Configure providers |
| SQLite memory and sessions | Runtime-ready | Memory and sessions |
| Local dashboard | Runtime-ready | Dashboard, status, and logs |
| Telegram, Discord, and Slack gateways | Runtime-ready | Operate gateways |
Expanding next
Section titled “Expanding next”| Capability | Readiness | Evidence |
|---|---|---|
| More Hermes compatibility | Planned | Build Gormes |
| Voice/TTS | Planned | Implementation roadmap |
| MCP/plugin support | Planned | CLI reference and Build Gormes |
| Package-manager installs | Planned | Install |
| More gateways | Planned | Gateway donor map |
| NaviWogs/NaviVox control plane | Experimental or internal | Build Gormes |
Implementation evidence
Section titled “Implementation evidence”Use Build Gormes for progress rows, parity workflow, builder queue, generated architecture archives, and contributor handoff material. Use this page when you need public readiness without the deep implementation inventory.