Engineering and operations

The weekly busywork, done before you ask.

Agents that write the standup digest, triage new issues, summarise on-call and draft release notes, on a schedule, with every run recorded and alerts when one breaks.

The job

Reports and triage that someone does every week.

Standup notes, a summary of last night's pages, the new issues sorted, the release notes drafted. Each is small, read by the whole team, and done by hand every week. They are good jobs for agents that run on their own, as long as you know when one stops working.

How it runs

On a schedule, on the record.

Each agent runs on a schedule with your tools connected: GitHub, Linear, Jira, Slack and more. Every run is recorded with its steps and cost, alerts fire when an agent fails or goes quiet, and built-in analysts point out what to fix.

Your tools, connected.

Read issues and pull requests, post to Slack, update tickets.

Runs on its own.

Hourly, daily, weekly or monthly, in your timezone, with no one starting it.

Alerts when it breaks.

A failed run or an agent that stops running reaches you in the app, by email or by webhook.

What to fix.

Built-in analysts read the runs and report failures, slow steps and cost.

Our own fleet

We run our company on these agents.

Before and after

The same reports, without the Monday morning.

By hand

  • Someone collects updates from three tools every morning.
  • Last night's pages are summarised when someone has time.
  • Release notes are written the day of the release.

With agents

  • The digest is in Slack before the standup.
  • The on-call summary is waiting at the start of the day.
  • Release notes are drafted from the merged pull requests.

Questions

What teams ask first.

How do I know when one of these stops working?
Set an alert on the agent: it fires when a run fails or when the agent stops running, in the app, by email or to a webhook.
Which tools can it use?
The apps you connect, such as GitHub, Linear, Jira and Slack, the built-in tools, and any HTTP API you describe as a tool.

Free two-week pilot

Try it free for two weeks.

We set it up on one job your team repeats. You approve every email and post. If it does not work for you, you stop and pay nothing.