Reading the workspace

The workspace is the shared state a turn operates on. After a turn completes, read it back with the thread_id from the conversation_info event.

export THREAD_ID="..."   # from the conversation_info event

# The co-constructed document
curl -s "https://haico.gr/api/workspace/$THREAD_ID/document" \
  -H "Authorization: Bearer $HAICO_TOKEN"

# The agent's evolving understanding of the goal
curl -s "https://haico.gr/api/workspace/$THREAD_ID/objective" \
  -H "Authorization: Bearer $HAICO_TOKEN"

# The hierarchical plan
curl -s "https://haico.gr/api/workspace/$THREAD_ID/todos" \
  -H "Authorization: Bearer $HAICO_TOKEN"

The persistent data model behind these routes is described in database-schema.md.

document and objective return JSON null with HTTP 200 until the agent has written one, which distinguishes “not written yet” from “written but empty”. A turn the agent answers conversationally, without editing the artifact, leaves them null. Check before subscripting.

See it in a full loop

A Python example that runs two turns and reads the document back afterwards.

Streaming agent turns API-only clients

Guide

Endpoints

Reading the workspace

See it in a full loop