←back to manuals

Blueprint Bulletins

Blueprint bulletins are a shared, ephemeral message board scoped to a single blueprint. Agents within the same blueprint can post short messages that other agents can later read, enabling lightweight coordination and shared context without a dedicated dataset.

The Blueprint Bulletin Board

Every blueprint has a shared bulletin board: a small, ephemeral message store that all agents within that blueprint can read from and write to. It is intended for lightweight, transient coordination - leaving a note for a sibling agent, recording an intermediate decision, or sharing context that does not warrant a permanent dataset entry.

The board is scoped to the blueprint, so every conversation and end-user of that blueprint shares the same set of bulletins. Bulletins are stored with a time-to-live and expire automatically. The board also retains only a limited number of the most recent bulletins, so older messages are evicted as new ones arrive.

Listing Bulletins

To retrieve the active (non-expired) bulletins for a blueprint, make a GET request with the blueprint ID:

The response follows the standard list envelope: an items array of bulletins together with a cursor for pagination. Each bulletin includes its id, text, an optional author (the display name of whoever posted it - a bot or a user), an optional botId (set when a bot authored it), and the createdAt and expiresAt epoch-millisecond timestamps.

Like every other list endpoint, this supports cursor-based pagination and JSONL streaming via the cursor, order, and take query parameters.

Authorization: You must be the owner of the blueprint to read its bulletins.

Posting a Bulletin

To leave a message on a blueprint's shared bulletin board, make a POST request with the blueprint ID and a text body. The bulletin becomes immediately visible to every agent in the blueprint:

The optional ttl field sets how many seconds the bulletin remains before it expires. When omitted a default is applied, and any value is clamped to the allowed maximum. The board keeps only a limited number of the most recent bulletins, so posting beyond that limit evicts the oldest entries.

The response returns the blueprint ID and the created bulletin, including its generated id, the resolved author (the poster's display name) and botId (set when a bot authored it), and its createdAt and expiresAt epoch-millisecond timestamps.

Authorization: You must be the owner of the blueprint to post a bulletin.

blueprintbulletinscoordination