File bugs from Slack without switching context
Describe the issue in plain language. Zero creates a formatted GitHub issue, labels it, and assigns the right person.
Zero connects:


Why filing GitHub issues from Slack saves context switching
You just noticed a UX bug during a demo. Instead of opening GitHub, finding the repo, writing a formatted issue, and assigning someone, you describe it in Slack. Zero creates the issue, adds labels, and assigns the right person. You never leave the conversation.
How to create GitHub issues from a Slack message
@Zero create issue: pressing ESC in the schedule dialog closes it immediately even with unsaved edits. Should ask for confirmation first. Assign to Lancy. Label as bug, platform. Priority medium.
How Zero parses your message and creates a formatted issue
Zero parses the request
Zero understands the bug description, identifies the assignee, and infers appropriate labels (bug, platform) and priority from context.
Issue created on GitHub
Zero creates a properly formatted GitHub issue with a clear title, description, labels, and assignment, all from your natural-language Slack message.
Confirmation in Slack
Zero replies in the same thread with the issue number, title, assignee, and a direct link so you can verify without leaving Slack.
Add details, batch file issues, or automate triage
Required integrations: GitHub and Slack
GitHub
OAuth connection to GitHub. Zero needs read/write access to create and manage issues.
Slack
Zero reads your message and replies in the same thread.
Best practices for filing bugs via Slack
Include the assignee name. Zero matches Slack display names to GitHub usernames.
Mention labels explicitly if you want specific ones, otherwise Zero infers from context.
Works for feature requests too, just say "feature request" instead of "bug".