Guided example. Fictional data and scripted responses. No connected accounts, live model calls, or external actions.

SELF-GUIDED PRODUCT TOUR

Choose where to start.

Take the complete walkthrough, or jump straight to the finished result. You can move between all four sections either way.

Both paths use the same fictional, preloaded example. Nothing runs, connects, changes, or sends from this page.

Find a useful starting point

01 · AGENT LIBRARY

Start with a useful agent—not a blank prompt.

Follow-Through Check is available in the Agent Library. This preloaded example shows its job, requirements, and limits without asking you to configure an account.

Coordination

Follow-Through Check

See what is due, blocked, waiting, or missing an owner.

Included

WHAT IT DOES

Returns a source-linked review of due work, blocked items, waiting items, and unclear ownership.

WHAT IT NEEDS

Task system · Mail or chat

PERMISSIONS

Read tasks · Read messages

BOUNDARY

Does not change tasks or send follow-ups

SCRIPTED SAMPLE USE

Review the fictional project board and team thread for due work, blocked items, waiting items, and unclear ownership. Return a source-linked handoff; do not change tasks or send follow-ups.

WHAT IS REAL HERE

The product behavior behind the example.

The walkthrough is scripted. These underlying capabilities are implemented in the signed-in workspace and covered by product tests.

Detailed agent listings

Agent listings expose purpose, price, systems, permissions, limits, and support terms before installation.

Clear authorship in shared rooms

Human messages keep their authorship, and each queued model reply is tied to the prompt it answers.

Saved visual workflows

Flow Studio stores allow-listed nodes and blocks activation until required agents and connections are ready.

Review before external actions

Write-capable steps expose their destination and remain behind the configured approval policy.