Memory and continuity
SQLite-backed episodic and distilled memory, graph edges, retrieval inspection, artifact-backed recall, and continuous identity state.
Release site
OpenCAS is a local-state autonomous agent with memory, voice, phone, and a real control plane.
It keeps state locally, routes models through open_llm_auth, and exposes the parts operators actually touch: chat, schedule, platform, logs, telemetry, and the dashboard tabs behind them.
Persistent memory
Voice + phone lanes
Schedule + platform
Logs + telemetry
What is live
Current surfaces, not aspirational ones.
The release bundle is meant to describe the running system exactly as it exists now, including the newer control-plane pieces.
Operator control plane
Dashboard-backed chat, operations, schedule, usage, platform, system, and logs views with API and WebSocket access behind them.
Channels
Dashboard chat, voice capture/synthesis, Twilio-backed phone handling, Telegram, and the live `/ws` bridge.
Platform and trust
Capability inventory, extension install/update/uninstall flows, bundle inspection, and plugin trust policy control.
Dashboard map
Rooms in the current control deck.
| Tab | What it shows |
|---|---|
| Overview | System summary and quick status |
| Health | Doctor checks and health event feed |
| Chat | Conversational interface with session and lane metadata |
| Operations | PTY/browser/process sessions, receipts, work, commitments, plans, qualification |
| Schedule | Scheduled tasks and events, calendar view, run history |
| Usage | Token usage, cost, and latency over time |
| Daydream | Daydream sparks, keeper history, conflict log |
| Memory | Episode and distilled memory browser, retrieval inspection, atlas view |
| Identity | Self-model, user model, somatic state, relational state |
| Executive | Goals, task queue, executive snapshot |
| Platform | Capability inventory, extension lifecycle, and trust control |
| System | Bootstrap configuration, effective model routing, phone, and Telegram setup |
| Logs | Runtime telemetry event stream |
Docs map
Find the part you need fast.
Installation
Clone, configure, and launch the current repo layout without pretending it is a packaged future release.
Usage
How to run the dashboard, voice/chat, schedule, phone, platform, and logs surfaces.
Features
Subsystem summary with the current memory, autonomy, channels, platform, and observability features.
API Reference
HTTP and WebSocket routes for the live server, including chat, phone, schedule, telemetry, and platform endpoints.
Architecture
Subsystem boundaries, runtime loops, persistence, and the current control-plane shape.
Terminology
The vocabulary used in the docs, dashboard, and source code.
Release truth
- OpenCAS is local-state and operator-owned.
- Chat, voice, and embedding lanes normally use configured providers through
open_llm_auth. - The current repo is best described as a local-state autonomous agent with provider-flexible model execution and first-class operator control planes.