v0.6.10
The "one session" redesign — a REPL/session is the single container, and every agent-loop execution under it (chat, a /command, a workflow run, a subagent call) is a trace tagged with the executing agent and, for workflows, workflow_id/workflow_run_id. The synthetic workflow:…:run:… and subagent:… session schemes are removed.
Runtime
- workflow_id/workflow_run_id are first-class columns on the runtime event log and the persisted turn, stamped on every workflow-request event.
- Workflow tasks run under the caller session (threaded through run_workflow; fresh per-run session otherwise); run history/summaries/live stream re-keyed onto workflow_run_id.
- Subagents run under the parent session, tagged with the executing agent.
- New
replayablecolumn: workflow/subagent turns are recorded but excluded from the model's replayed history and compaction.
API / telemetry
- POST /workflow/{id}/run accepts session_id.
- New GET /telemetry/sessions (event-log rollup). /telemetry/traces accepts session_id without agent_id to list a session's traces across agents.
Admin UI
- Sessions is a real table (Agent · Session ID · Started · Tokens · Traces); expanding shows a Traces table (Started · Trace ID · Ran on · Workflow · Duration · Events).
- New CopyId: full, untruncated session/trace ids with copy-to-clipboard.
416 tests pass. The live DBOS/Postgres workflow path and the admin UI in a browser are not yet smoke-tested; schema migrations are idempotent.