Read a session's live summary over the public API

If you build against the public API, you could pull a session's transcript but not the summary Chief reconciles while the session records. Reading a session's decisions and to-dos meant going through the MCP server.

Live summary in the session response

Retrieve Session now returns a live_summary object with the session's headline and its running bullets. The bullets are the canonical record of what the session decided, and the todo items are the follow-ups.

Each bullet carries an id that stays stable for the life of the session, so you can key an item across reads even after the wording changes. Alongside it you get:

• kind: context, decision, or todo
• topic, the heading the bullet sits under
• text and owner, where an owner was named in the transcript
• state: open, approved, dismissed, or done
• active, true when the item sits in the main summary
• first_seen_sec, the audio-time the item first appeared
• parent_id on a sub-point, one level deep

state and active reflect your own decisions in the app, so a dismissed item stays dismissed when you read it back.

Session lifecycle and language

Both the list and retrieve endpoints now return state, telling you whether a session is scheduled, started, or ended, along with the matching timestamps from the call's own clock and the calendar event id when the session came from a calendar. Check it before you treat a session as finished.

The full session view also returns language, the transcription language the session was recorded in.

Point your automation at live_summary to turn a meeting's to-dos into tickets, reminders, or anything else you run. The OpenAPI spec has the full shape.