Every hour
Triage new bugs
Reads new bug tickets, sets severity and finds likely duplicates.
Tables
GitHub issue triage agentEvery new issue gets a first answer.
Every 30 minutes it reads new issues. It suggests a label, drafts a reply when detail is missing and flags the ones that look like real bugs.
Your first signup includes $50 in free credits.
Every 30 minutes
Triage GitHub issues
- Reads
- New GitHub issues
- Grows
- Labels and replies
- Lands in
- GitHub and a Sheet
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 30 minutes, read new issues in my repo. Suggest a label for each. If a bug report has no steps, draft a reply that asks for them. Log it in a Sheet. Ask before touching GitHub.
TulipFarm
I made an agent called Issue triage and a 30-minute schedule. It reads GitHub. Adding labels, replying and posting to Slack asks you first. Activate it?
ActivateEdit first
One check, start to finish.
Every run is saved as an agent task you can open, check and rerun.
- Schedule
Every 30 minutes
Run startedStarted - Reads
New issues since last run in GitHub
6 issues - Sorts
Label and type, using your triage skill
2 bugs, 3 questions, 1 idea - Checks
Does a bug report have steps?
1 missing - Asks first
Add labels and send the replies
Approved - Updates
Issues in GitHub, log rows in Sheets
6 rowsCompleted
The sheet behind the triage.
One row per issue, so you can scan what came in and what it did.
Issue triage log| Issue | Type | Label | Next step |
|---|---|---|---|
| Issue 1 | Bug | bug | Reply sent: asked for steps |
| Issue 2 | Question | question | Point to the docs |
| Issue 3 | Idea | enhancement | Added to the request list |
| Issue 4 | Bug | bug, high | Flagged to the team |
What gets planted.
Three parts you own and can change at any time.
- Agent
Issue triage
Reads issues and suggests the next step.
- Skill
Label rules
Your labels and when to use each.
- Workflow
Every 30 minutes
Checks for new issues all day.
Uses
- GitHub
- Google Sheets
- Slack
Add if you use it
- Jira
MCPLinear
Confluence
It reads quietly. It asks before it acts.
Reads without asking
- New issues and their comments
- Your label list
- Docs links you give it
Asks you first
- Adding labels
- Replying on an issue
- Posting to Slack
It uses your own connections, so it never sees more than you can.
Grow it your way.
Point to the docs
Give it your docs links so it can answer common questions with a link.
First-timers
Mark small bugs with a good first issue label, after you approve.
Weekly digest
Add a weekly post of open issues with no reply.
Questions, answered.
Does it answer people alone?
No. Every reply and label asks you first. You see the text before it is sent.
Is there an issue trigger?
No. TulipFarm has no new-issue trigger for GitHub, so it checks on a schedule. You can change the time.
Can it close issues?
Only if you add that step. It asks you first.
- Tables
On mention
Summarize a pull request
Paste a PR link in Slack and get a plain summary and risk list.
New response
Track every feature request
Logs each request, merges repeats and counts who asked.
Google FormsTables
Open issues, answered fast.
Public beta, open to everyone. Your first signup includes $50 in free credits.