StoryOS

Agents · For teams

Standup Digest

What moved, what’s blocked, what’s due — posted before your team logs on.

A StoryOS feed view with a stream of posts

The digest lands in a feed view — scannable before the day starts.

Trigger

A weekday schedule, before the workday starts.

MCP tools it uses

query_recordsdescribe_databaseadd_comment

Reads

  • Yesterday’s state changes across the boards you point it at
  • Blocked-by relations that gate other work
  • Due dates in the next 48 hours

Writes

  • A digest post to the team feed — moved / blocked / due, with links to every record
  • Flags on stale blockers that nobody has touched

Human checkpoints

  • The digest is informational — it changes no records, so it runs fully autonomous by default
  • Blocker escalations mention a human rather than reassigning work

The loop, step by step

1

The schedule fires early

Before standup, the agent queries what changed since yesterday: state transitions, new blockers, approaching due dates.

2

It writes the digest

One post: what moved (with who), what’s blocked (and by what), what’s due (and whether it’s on track) — every line linked to its record.

3

The team reads it in the feed

Standup starts with the facts already on the table, and the meeting becomes about decisions instead of recaps.

Runs on the AI you already have

This loop runs today with your own Claude or ChatGPT connected over MCP — you drive it assistively, or wire the trigger with an automation. StoryOS never meters or marks up your own AI, on any plan. No AI subscription? The optional StoryOS AI add-on covers you at near-cost credits.

Templates this agent works well with

Run Standup Digest on your data.

Start free — 30 days of Pro, no card. Your own AI is never metered.