Operate
Operate covers the workflows after Gormes is installed and configured. Use this section for local terminal work, server-side gateways, profile isolation, provider fallback, and runtime inspection.
Local terminal workflow
Section titled “Local terminal workflow”| Task | Use it for |
|---|---|
| First chat | Connect a provider and run a first turn. |
| Local Ollama | Run Gormes against a local model endpoint. |
| Profiles for client work | Keep projects, clients, and workspaces separated. |
| Memory and sessions | Inspect sessions, persisted memory, and local state. |
Server and gateway workflow
Section titled “Server and gateway workflow”| Task | Use it for |
|---|---|
| Telegram bot | Run a Telegram-facing Gormes agent. |
| Multi-channel gateway | Run configured Telegram, Discord, and Slack gateways from one runtime. |
| Channel bindings | Route channels, users, profiles, agents, and workspaces intentionally. |
| Fallback provider chain | Keep runtime turns resilient when a provider fails. |
| Dashboard, status, and logs | Inspect the runtime while it is running. |
Android companion workflow
Section titled “Android companion workflow”| Task | Use it for |
|---|---|
| Navivox and F-Droid | Understand why F-Droid is the natural Android distribution target for Navivox and what evidence is required before claiming availability. |
Related setup
Section titled “Related setup”- Configure providers before provider-backed chat.
- Configure channel credentials before gateway work.
- Troubleshoot doctor output when a runtime check fails.