Memory tools
Episode list, search, graph view, landscape view, embedding projection, node detail, and retrieval inspection.
Operate through the dashboard, API, and configured channels.
The current repo does not expose a separate interactive python -m opencas chat terminal mode. The practical operator paths are the dashboard, the HTTP API, Telegram, phone, and the WebSocket bridge when enabled.
Launch modes
python -m opencas --with-serverThis is the primary operator mode. It serves the dashboard and the HTTP/WebSocket APIs on 127.0.0.1:8080 by default.
python -m opencas --tuiUse the TUI when you need to set up or change provider material, model selection, Telegram settings, or copied credential material.
Dashboard tabs
| Tab | Purpose |
|---|---|
| Overview | High-level runtime, health, token, and memory summaries. |
| Health | Doctor status, recent health history, runtime and event visibility. |
| Chat | Session history, current provider/model lane, somatic context, current work, voice controls, and message send. |
| Operations | Receipts, tasks, work objects, qualification runs, approval audit, and live process control. |
| Schedule | Durable schedules, calendar views, and run history. |
| Usage | Token telemetry, dominant models and sources, provider telemetry notes, and process hygiene clues. |
| Daydream | Reflections, conflicts, keeper promotion, and daydream-origin work. |
| Memory | Memory atlas, retrieval inspection, embedding projection, and node detail. |
| Identity | Self-model, user model, continuity, musubi, and somatic state. |
| Executive | Goals, plans, commitments, and executive snapshot. |
| Platform | Capability inventory, extension lifecycle, and trust policy control. |
| System | Config overview, model/configured option visibility, phone, and Telegram control. |
| Logs | Telemetry event stream and search/filter controls. |
Chat lane behavior
- The chat rail shows the active lane: provider, resolved model, auth profile, and auth source.
- New assistant messages carry their own lane metadata in history.
- Older assistant messages that predate lane metadata should be treated as legacy historical entries.
- The chat context panel also surfaces somatic state, current work, executive intent, and recent background-task counts.
- Voice controls let the operator record a prompt, transcribe it, and synthesize spoken replies when configured.
Memory and daydream behavior
OpenCAS uses provider-backed embeddings by default for semantic memory retrieval. Artifact-backed autobiographical memory is also part of the current system, which means authored plans and stories can be ingested into recall instead of only being found as raw files.
Daydream tools
Reflections, keepers, conflicts, promotion lineage, and daydream-origin work visibility.
Channels
Telegram
Use the System tab or the TUI bootstrap to configure bot token, pairing policy, allowlists, and polling settings.
Phone
The System surface and `/api/phone/*` routes expose Twilio configuration, owner calling, and recent-call inspection.
Voice
Use the Chat tab microphone and speaker controls when voice transcription and synthesis are enabled.
Operations and control planes
- Use the Operations tab to inspect receipts, task state, work objects, commitments, plans, and live process sessions.
- Use the Schedule tab to manage recurring work and see what is due next.
- Use the Platform tab when installing or auditing extensions and trust policies.
- Use the Logs tab when you need the raw event sequence.
- Use the Usage tab to inspect token usage, expensive sources, dominant models, and provider telemetry notes.
- Use the System tab to confirm the effective provider/model configuration before assuming a lane is active.
Good operator habit. When something looks wrong in chat, verify the active lane in the Chat panel and the effective runtime model in the System panel before assuming the dashboard is lying.