API
Agents & Sessions API
ImplementedThe legacy session API is the earlier planner loop. It remains because Decision Memory still exposes Planner sessions alongside the newer Decision Runtime.
Why this exists
Why this API boundary exists
The legacy session API is the earlier planner loop. It remains because Decision Memory still exposes Planner sessions alongside the newer Decision Runtime.
Endpoints
POST
/chat/streamImplementedSSE OpenAI chat (agent / plan / debug modes).
Auth: clerk
Framework02
services/api/app/routes/chat.py
POST
/sessionsImplementedCreate a legacy decision session.
Auth: clerk
Framework06
services/api/app/routes/sessions.py
POST
/sessions/{session_id}/runImplementedRun the legacy planner and persist messages.
Auth: clerk
services/api/app/routes/sessions.py
GET
/sessions/{session_id}ImplementedGet session, messages and decisions.
Auth: clerk
services/api/app/routes/sessions.py
POST
/sessions/{session_id}/decideImplementedHITL accept/reject; optional re-run on reject.
Auth: clerk
services/api/app/routes/sessions.py