All agents

Operations Manager Agent

An autonomous ops lead that turns your team's status into a daily standup digest — progress, blockers, risks, top-3 priorities, and leadership escalations — and posts it straight to Slack.

View in marketplace Open dashboard

The Operations Manager Agent runs your daily standup for you. Each run it reads the latest team status, synthesizes a structured digest (progress, blockers, risks, top 3 priorities, and any escalations for leadership), and — when Slack is connected — posts it to your ops channel. For concrete action items it can open a tracking issue in GitHub or Linear. It runs on a schedule (Daily, Weekly, or Monthly) or on demand, so status-chasing stops being a manual chore.

What it does

This agent acts as a tireless operations manager. Given a snapshot of where projects stand, it writes a clean, consistent standup digest covering progress, what's blocked and who's needed to unblock it, emerging risks, and the three priorities that matter most today — then flags anything leadership needs to know early, before a slip becomes a fire. Each run finishes by recording the digest to your dashboard's execution feed and, where you've connected the tools, pushing it into the places your team already works.

Operationally it's a tight, tool-driven loop with a 5-turn cap. It posts the digest to your configured Slack channel via slack_post (resolving the channel id with slack_list_channels when needed), and for action items it can open a tracking issue with github_create_issue or linear_create_issue. When Slack isn't connected, it gracefully degrades — the full digest is still returned and saved on the deployment page. It works from the status you give it: pasted updates today, with Linear/Jira/Notion connections able to deepen the source over time.

How it works

Your Business
1
Gather status
Reads the latest team status — either the updates you pasted into the Team status field or the status passed into the scheduled run.
2
Synthesize digest
Writes a structured standup: progress made, current blockers (and who's needed), emerging risks, and the top 3 priorities for the day.
3
Flag escalations
Identifies anything that needs leadership attention — slipping timelines, stuck blockers — and calls it out explicitly in the digest.
4
Post to Slack
If Slack is connected, posts the digest to the configured channel via slack_post, using slack_list_channels to resolve the channel id when needed; otherwise includes it in the output.
5
Open tracking issues
For concrete action items, optionally opens a tracking issue with github_create_issue or linear_create_issue when those tools are connected.
6
Record output
Calls record_output once with the digest plus a note of what was posted or created — saved to the deployment's execution history feed on the dashboard.
Outcomes delivered

Setting it up — owner / admin

  1. 1
    Deploy from the dashboard
    After subscribing, the agent appears in your dashboard. Open its deployment page at /dashboard/agents/[id] — this is where you configure, schedule, and run it.
  2. 2
    Connect Slack (and optionally GitHub/Linear)
    Go to /dashboard/tools and connect Slack so the agent can post the digest. Optionally connect GitHub and/or Linear so it can open tracking issues for action items. Without Slack, the agent still produces the digest but only returns it to the dashboard.
  3. 3
    Fill the config fields
    In the Configure panel, set: Team status (for test runs) — paste current project updates; Slack channel — where to post, e.g. #ops; Run frequency — Daily, Weekly, or Monthly. Save the configuration.
  4. 4
    Set the schedule
    The Run frequency field drives automatic runs: Daily advances the next run by +1 day, Weekly by +7 days, Monthly by +1 month. Daily each morning is typical for a standup.
  5. 5
    Do the first run
    Paste a status update, set the Slack channel, and click Run now. Watch the Execution history feed for the digest and confirm it landed in your Slack channel.

Using it day to day — your team

  1. 1
    Read the morning digest in Slack
    Once scheduled, the team sees the standup digest land in the configured channel (e.g. #ops) each run — progress, blockers, risks, and the day's top 3 priorities, in a consistent format.
  2. 2
    Act on blockers and priorities
    Use the 'who's needed' callouts to unblock work and the top-3 priorities to focus the day. Escalations surface delays to leadership early.
  3. 3
    Pick up tracking issues
    If GitHub or Linear is connected, action items show up as tracking issues in your existing board — assign and work them as normal.
  4. 4
    Review past digests on the dashboard
    Every run is saved to the Execution history on the deployment page (/dashboard/agents/[id]) — a record of standups even if you missed Slack.
  5. 5
    Trigger an ad-hoc standup
    Need a mid-day status? An admin can paste fresh updates and hit Run now for an on-demand digest without waiting for the next scheduled run.

Use cases

Daily standup digest
Auto-generate and post a structured standup to your ops Slack channel every morning, replacing the manual status round-up.
Blocker tracking
Surface what's stuck and who's needed to unblock it, and optionally open a GitHub/Linear issue to track the fix.
Leadership escalation
Flag slipping timelines and stuck blockers as explicit escalations so leadership sees delays before they slip.
Agency delivery tracking
Keep client/project delivery moving with a consistent daily digest of progress, risks, and priorities across teams.

What to expect

  • A daily standup digest covering progress, blockers, risks, and the top 3 priorities
  • Risks and delays escalated to leadership early
  • The digest posted straight to your team's Slack channel (when connected)
  • Optional GitHub/Linear tracking issues for concrete action items
  • A saved execution-history record of every standup on the dashboard
  • Less manual status-chasing for ops leads and founders

Metrics to watch

  • Run success rate (status = success in the execution feed) — runs typically complete in under a minute
  • Standup digest reliably posted to the configured Slack channel each scheduled run
  • Blockers surfaced and resolved faster (shorter time-to-unblock)
  • Fewer surprise slips — risks flagged as escalations before deadlines are missed
  • Tool-call count and token usage per run staying stable (visible per run on the deployment page)

FAQ

Does it post to Slack itself?
Yes, when Slack is connected at /dashboard/tools it posts the digest to your configured channel via slack_post. If Slack isn't connected, it returns the full digest in the run output on the dashboard instead.
Where does the status come from?
Today, from the updates you paste into the Team status field (used for test runs and as the run input). Connecting Linear, Jira, or Notion can deepen the source over time.
Can it create tasks or tickets?
Yes — for concrete action items it can open a tracking issue with github_create_issue or linear_create_issue, but only when those tools are connected.
How often does it run?
It runs on the schedule you pick in the Run frequency field — Daily (+1 day), Weekly (+7 days), or Monthly (+1 month) — or on demand via Run now. Daily each morning is typical for a standup.
What does each run produce?
A standup digest (progress, blockers, risks, top-3 priorities, escalations) posted to Slack or returned, plus a saved record in the deployment's execution history with a note of what was posted or created.