Skip to content

React to a bug. Get a fix.

Snapwing turns bug reports in Slack into Jira tickets, and optionally into fixes. React to a report and it reads the thread, checks for duplicates and files a ticket that names the likely code. An autonomy dial decides how far it goes, from ticket only to a reviewed pull request.

SnapwingIn development. Not installable yet

Decide how far the agent goes.

Same bug, four levels. Move the dial and watch who does what.

Autonomy level

Set per channel, component and priority. Try each level.

Level 1
Fix on tap
The fix starts
When an engineer taps Fix it
Who merges
A person
StopNot needed
RevertOnly after autopilot
  1. A bug report in Slack

    Runs

    Marcus Bell in #donor-portal

    Donation receipts are going out with last year’s date on them.

    1 bug reaction
  2. A Jira ticket that names the likely code

    Runs
    DON-87No duplicates found

    Receipt PDF uses a cached fiscal year

    src/receipts/renderReceipt.ts:118

  3. A coding agent writes the fix

    Waits for a person

    Nothing starts until an engineer taps Fix it.

    Fix it
  4. A second agent reviews it

    Waits for a person

    Fix receipt year on regenerated PDFs

    After the tap
  5. A person merges

    Waits for a person

    The pull request waits for a person. The Slack thread gets the update.

For product teams and nonprofit staff.

Product teams

Bugs stop dying in Slack threads. Each one becomes a ticket with context, screenshots and the likely code, and at the level you choose, a reviewed fix.

Nonprofit staff

No one has to learn Jira to report a problem with the donor portal or the volunteer app. React to the message, and the right people get a ticket they can act on.

Where it stands.

Snapwing is in active development and is not installable yet. Here is exactly what works.

Slack to Jira to pull request, levels 1 and 2
Passes automated live tests against real Slack, Jira and GitHub sandboxes.
Levels 0 and 3
Built and tested against mocked services.
Microsoft Teams, a CLI and Raycast
In progress.

Be first to try it.

Join the early-access list, or follow the repository to watch it come together.

Questions, answered

What is Snapwing?

Snapwing is an open-source tool from Vouch Networks that turns bug reports in Slack into Jira tickets, and optionally into fixes. React to a report and it reads the thread and screenshots, checks for duplicates and files a ticket that names the likely code.

Can I install Snapwing today?

Not yet. Snapwing is in active development and is not installable. The Slack to Jira to pull request flow at levels 1 and 2 passes automated live tests. Join the early-access list and follow the repository on GitHub to hear when it is ready.

Get early access

What does the autonomy dial do?

It decides how far Snapwing goes, per channel, component and priority. Level 0 files a ticket only. Level 1 starts a fix when an engineer taps Fix it. Level 2 starts the fix automatically, and a person merges. Level 3 is autopilot.

Can the agent merge code on its own?

Only at level 3, and only if the review agent, CI and the merge checks all pass. At levels 2 and 3 every card and status message has a Stop button, and after an autopilot merge a one-tap Revert stays available for 72 hours by default.

Is Snapwing only for software teams?

No. Anyone who reports bugs in Slack can use it, including nonprofit staff who run a donor portal, a volunteer app or a member site. Reporters just react to a message. Snapwing does the writing up.