After an incident
Draft the postmortem
Builds a timeline from the Slack thread and drafts the review.
On-call handoff agentThe next person starts informed.
At the end of the shift it reads the alert channel, open tickets and recent deploys. It drafts a short note on what is open and what to watch.
Your first signup includes $50 in free credits.
Fridays · 16:00
Hand off on-call cleanly
- Reads
- Alerts, tickets, deploys
- Grows
- A handoff note
- Lands in
- Slack
Ask for it once, in plain words.
No flowchart to draw. Describe the job in chat. TulipFarm sets up the agent and its workflow, and shows you both before anything runs.
You
Every Friday at 4, read the alerts channel, open on-call tickets in Jira and this week's deploys in GitHub. Write a handoff note for the next person and show it to me first.
TulipFarm
I made an agent called On-call handoff and a Friday 16:00 schedule. It reads Slack, Jira and GitHub. Posting the note asks you first. Activate it?
ActivateEdit first
One shift change, start to finish.
Every run is saved as an agent task you can open, check and rerun.
- Schedule
Fridays at 16:00
Run startedStarted - Reads
The week's alerts in Slack
31 alerts - Reads
Open on-call tickets in Jira, deploys in GitHub
3 tickets, 6 deploys - Writes
A handoff note, using your handoff skill
1 note - Asks first
Post the note to the on-call channel
Approved - Posts
Message in Slack
Delivered 16:04Completed
The note the next person opens first.
Open items first. Noise is grouped so it does not hide the real problem.
#on-callOn-call handoff APP · 16:04
Handoff · this week to next week
Still open
- Ticket 1: slow report page. Mitigated, not fixed.
- Ticket 2: a flaky job. Retries hide it.
Noisy alerts
- Disk warning fired 12 times. Always clears itself.
Watch
- A deploy is planned for Monday morning.
What gets planted.
Three parts you own and can change at any time.
- Agent
On-call handoff
Reads the week and writes the note.
- Skill
Handoff format
Open, noisy, watch. In that order.
- Workflow
Fridays 16:00
Runs at shift change.
Uses
- Slack
- Jira
- GitHub
Add if you use it
Google Calendar- Confluence
MCPLinear
It reads quietly. It asks before it acts.
Reads without asking
- The alerts channel
- Open tickets with the on-call label
- Recent deploys and merged pull requests
Asks you first
- Posting to Slack
- Commenting on a ticket
It uses your own connections, so it never sees more than you can.
Grow it your way.
Match your rota
Change the schedule to your real shift change time.
Read the calendar
Name the incoming person from the on-call calendar and mention them.
Keep a log
Also save each note as a Confluence page, after you approve.
Questions, answered.
Does it page anyone?
No. It reads and writes a note. Posting the note asks you first.
How does it know what is noise?
From your skill, such as alerts that fire often and clear on their own. You can change the list.
Can it use PagerDuty?
Not built in. Any tool with an MCP server can be added as a Custom MCP connection, and you review each tool first.
Weekdays · 8:30
Digest the failing builds
Groups the day's CI failures by cause and who should look.
Every hour
Triage new bugs
Reads new bug tickets, sets severity and finds likely duplicates.
Tables
Friday in, calm Monday out.
Public beta, open to everyone. Your first signup includes $50 in free credits.