Skip to content
TulipFarm

Bug report agentA clean bug, in one mention.

Mention it on a support thread. It reads the conversation, writes steps to reproduce and the impact, and opens a Jira issue once you approve.

Sign up for CloudWatch one run

Your first signup includes $50 in free credits.

On mention

File bugs from support

Reads
The thread, the customer email
Grows
One Jira issue
Lands in
Jira and Slack
SlackJiraGmail
File bugs from support: starts On mention, uses Slack, Jira, Gmail.

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

When I mention you on a support thread, read it, write a Jira bug with steps to reproduce and who is affected, and reply in the thread with the link.

TulipFarm

I made an agent called Bug filer and attached it to your support channel in Slack. It reads the thread and the customer's email in Gmail. Creating the Jira issue and replying in Slack asks you first. Activate it?

ActivateEdit first

One bug, start to finish.

Every run is saved as an agent task you can open, check and rerun.

  1. Slack

    You mention the agent on a thread

    Run startedStarted
  2. Reads

    The Slack thread and the customer email

    9 messages
  3. Reads

    Open Jira issues with similar words

    1 close match
  4. Writes

    Title, steps, expected result, impact

    1 issue draft
  5. Asks first

    Create the Jira issue and reply in the thread

    Approved
  6. Creates

    Issue in Jira, reply in Slack

    Issue createdCompleted

What lands in Slack.

A reply in the same thread, with the issue link and what it wrote.

What gets planted.

Three parts you own and can change at any time.

  1. Agent

    Bug filer

    Reads the thread and writes the issue.

  2. Skill

    Bug format

    Title, steps, expected, actual, impact.

  3. Workflow

    On mention

    Starts when someone mentions it in Slack.

Uses

  • SlackSlack
  • JiraJira
  • GmailGmail

Add if you use it

  • GitHubGitHub
  • LinearMCPLinear
  • ZendeskMCPZendesk

It reads quietly. It asks before it acts.

Reads without asking

  • The Slack thread
  • The customer's email, if linked
  • Open Jira issues in your project

Asks you first

  • Creating a Jira issue
  • Replying in Slack
  • Emailing the customer

It uses your own connections, so it never sees more than you can.

Grow it your way.

  • Link, do not duplicate

    If a match exists, comment on it instead of opening a new issue.

  • Tell the customer

    Draft a short note to the customer once the issue is filed.

  • Pick the team

    Route the issue to the right Jira component from your list.

Questions, answered.

Can it reproduce the bug itself?

No. It cannot run your product. It writes the steps from what the customer and your team said, and marks anything it is unsure of.

Will it open issues without me?

No. Creating the issue asks you first, and you can edit the draft before you approve.

Does it work with GitHub or Linear?

GitHub is built in. Linear works through a Custom MCP connection.

TulipFarm for customer support

Bugs that engineers can act on.

Public beta, open to everyone. Your first signup includes $50 in free credits.

Sign up for CloudTake the browser tour