Run the stack locally, understand the backend runtime, and find the main source areas.
Choose your path
Start with the docs closest to your work
OpenCouch spans safety policy, backend runtime, memory, voice, and web surfaces. Start with the path closest to what you want to inspect or change.
Review the crisis gate, safety boundaries, and response policy.
Understand graph routing, prompt assembly, state, tools, and therapeutic behavior.
Inspect semantic, episodic, and procedural memory plus privacy controls.
Trace the OpenAI Realtime lifecycle, tool policy, persistence, and dogfood flow.
Trust model
Concrete safety and privacy mechanisms
Each principle is backed by a visible implementation artifact instead of a vague promise.
Crisis assessment runs before memory retrieval, so unsafe turns do not load contextual memory first.
crisis_gate → turn_dispatch → load_memoryUser-controlled memoryMemory is documented as inspectable and controllable through explicit user commands and privacy controls.
semantic · episodic · proceduralHonest boundariesOpenCouch provides support without pretending to be therapy.
onboarding · prompts · crisis responsesSelf-hostable infrastructureBackend, web, docs, and persistence modes can be run locally or on your own infrastructure.
backend · web · docsAGPL-3.0 licensedDeployment changes must remain visible, reducing the chance that safety mechanisms are stripped in closed forks.
open source safety preservationRun locally
Start the stack from your checkout
Use the project virtualenv for backend commands and run each surface from its app directory.
cd apps/backend && .venv/bin/python -m uvicorn main:app --reload --host 127.0.0.1 --port 8000cd apps/web && pnpm devcd apps/docs && pnpm startSource map
Jump from docs concept to code
The docs map directly to the backend, agent, voice, web, and evaluation areas of the repository.
Core principles
Built to be trustworthy, not just capable
Most AI products are built for engagement. OpenCouch is built for trust — with clear safety boundaries, user-controlled memory, and an architecture that can run entirely on your own infrastructure.
No data sold. No third-party training. Self-hostable so data never leaves your infrastructure if you choose.
01Crisis detection runs as a hard gate before every response — deterministic patterns plus an LLM classifier, always.
02OpenCouch is not a therapist. It says so clearly, in onboarding, in prompts, and in every crisis response.
03Web chat and OpenAI Realtime voice are the dogfood surfaces today. Additional messaging channels are on the roadmap.
04Not MIT — intentionally. AGPL ensures that anyone who deploys a modified version must publish their changes. Safety features like the crisis gate cannot be silently stripped in a closed fork.
05
OpenCouch