Quick start
Connect GitHub once in Settings → Integrations → Github → Connect. Then, from any Thread, Highlight, or Cluster, click Share → Share to GitHub → choose your connection → Share. NEXT AI creates a GitHub issue with your insight text and a link back to the video evidence in NEXT AI, so engineering has everything needed to code and build.
Why integrate with GitHub?
Our NEXT AI × GitHub integration sends Threads, Highlights, and Clusters straight into your backlog as GitHub issues, automatically linking back to recordings and Highlights. Creating an issue (user story, bug, enhancement) from NEXT AI preserves a traceable chain from the problem to the evidence, so teams can plan and track work with confidence.
What NEXT AI creates: A GitHub issue in the repository defined by your connection.
What’s included: Title/body from your insight, plus a link to the video evidence in NEXT AI (Issues must be enabled in the repo).
Where it lands: The target repository’s Issues tab.
Connect GitHub (one-time)
In NEXT AI, click your profile photo (top right) → Settings
Open Integrations → GitHub → Connect
Click New connection, name it clearly (e.g., “GitHub — Bugs”, “GitHub — Product”)
Enter the repository URL for your organization (for example, https://github.com/<org>/<repo>) → Save
⚠️ You can set up multiple connections for different GitHub repositories and pick the right one at share time.
Note: GitHub connects at the teamspace level. Set up the connection in the teamspace where you’ll be sharing.
Create a GitHub Issue from NEXT AI
Toy can share Threads, Highlights, and Clusters to Github.
Open the item (Thread / Highlight / Cluster)
Click Share → Share to GitHub
Choose the GitHub connection you created → optionally edit the text
Click Share — NEXT AI creates a GitHub issue with your insight and a source link back to the evidence in NEXT AI.
Tips
Keep the issue title short and action-oriented; use the description for detail. GitHub Issues are designed for tracking bugs, enhancements, and ideas in your repo.
Create separate connections (e.g., Bugs repo vs Product repo) so it’s fast to route items correctly at share time.
Troubleshooting
GitHub isn’t in the Share menu. Connect it first in Settings → Integrations → GitHub.
“Issues are disabled” / 410 errors. Some repositories turn off Issues. If Issues are disabled, GitHub returns 410 Gone when creating one—enable Issues in the repo or pick another repo.
Permission errors (403). You need permission to create issues in the target repo. Ask a GitHub admin to grant access.
Heavy automation hits limits (“rate limited”). GitHub enforces primary & secondary API rate limits (including caps on content creation per minute/hour). Stagger or batch if you automate lots of shares.
FAQ
Q: What exactly does NEXT AI send to GitHub?
A new GitHub issue using your insight text (title/description) plus a link back to the original video/context in NEXT AI—so devs can verify the signal before acting.
Q: Where do the issues land?
In the repository configured in your GitHub connection. Use multiple connections for different repos to route work cleanly.
Q: Why create issues from NEXT AI instead of typing them in GitHub?
You move customer signal + proof in one step. The source link keeps evidence traceable, cutting back-and-forth during grooming and implementation.
Q: Who can open the NEXT AI link from the GitHub issue?
Only people with permission in NEXT AI for that item. Linking from GitHub doesn’t bypass NEXT AI access controls.
Q: Can I choose labels/assignee/milestone when sharing?
Create the issue from NEXT AI, then triage in GitHub using your normal process (labels, assignees, projects, etc.—all standard Issue workflows).
Q: Our repo rejects creation saying Issues are disabled—what should we do?
Enable Issues in that repository or pick a repo with Issues enabled; GitHub returns 410 Gone if Issues are disabled.
Q: We plan to share many items—anything to watch for?
If you automate bulk creation, observe GitHub’s rate limits (including content-creation caps per minute/hour) and add backoff.
Q: Does NEXT AI upload the actual video to GitHub?
No—NEXT AI adds a link back to the video and context so evidence stays authoritative in NEXT AI while GitHub remains your system of action.