Assistance operates on the same system

Orbit’s assistant surfaces make it easier to capture and review life activity in the moment. They are interfaces to the Orbit data model, not a separate data product.

Chat

The web app includes a streaming chat experience with named sessions and message history. Users can create, retrieve, rename through update flows, and delete sessions. A chat turn can use Orbit tools to perform structured work, then stream the response back to the interface.

Shipped Chat is a product interaction surface with its own session model and telemetry boundaries.

Voice

Voice sessions use a realtime connection model. The API creates a session, handles tool execution, and records hangup state. Voice tool calls carry the same domain context and auditability expectations as other assistant work.

MCP

Remote MCP exposes Orbit to compatible clients such as Cursor and Claude. The toolset provides generic CRUD plus task-focused shortcuts for balance, habit check-offs, mood, journals, tickets, telemetry, and UI coordination.

Principle	Product consequence
One model	Actions from app, chat, voice, and MCP operate on shared goals, habits, entries, and reflections.
Explicit tools	The assistant performs named operations instead of relying on untraceable free-form behavior.
Correlated activity	Requests, sessions, and tool calls can be traced through product telemetry.

See API, MCP, and OAuth for the integration boundary.