Threads now open GitHub issues

File FinOps findings from Insights and CloudFlow straight into the repositories your engineers already work in. Available now to all Cloud Intelligence™ customers.

Most cloud "waste" does not survive first contact with a backlog. An insight flags a database that has been idle for 60 days. Someone screenshots it, pastes it into a chat, and it dies there, because the team that owns the database plans its week in GitHub Issues and nobody wanted to open a ticket in a tool they never check. Threads exists to fix that handoff, but until now it could only file into Jira and Linear. If your engineering work lives in GitHub, the last step was still copy and paste. That gap is closed. Threads can now create and track GitHub issues.

What you get

Once the Cloud Intelligence Threads GitHub App is installed on your organization or personal account, GitHub Issues appears as a target wherever threads are created. From an insight, you pick a repository, review the pre-filled title and description, optionally add labels and assignees, and the issue is opened. From CloudFlow, the Threads node gets the same fields (repository, title, Markdown description, labels, assignees), so a flow that detects an anomaly can open the issue on its own with the numbers attached.

The Integrations page and the Threads header now show which of Jira, Linear and GitHub are connected, so you can tell at a glance where a thread can go before you create one.

Cloud Intelligence™ keeps tracking the issue after it is created. State, labels, assignees and milestone are read from GitHub, and a Manage in GitHub button takes you to the issue itself. Edits made on the GitHub side show up in the console. If someone transfers the issue to another repository the app can access, the thread follows it. The console does not add issues to GitHub Projects, so if your team plans in a Project, turn on its built-in auto-add workflow for that repository.

Setup is deliberately boring. The app asks for two repository permissions: Issues (read and write) and Metadata (read-only). You decide at install time whether it can see all repositories or only selected ones, and you can change that later on GitHub. An organization owner installs it; if a member starts the install, GitHub routes an approval request to the owners and the console shows Awaiting approval until one of them accepts. Uninstalling the app disconnects everything, and the console marks existing GitHub threads as not available within seconds.

Get started

1. Connect GitHub from Integrations and install the Cloud Intelligence Threads app on the repositories you want.
2. Open an insight and create a thread, choosing GitHub Issues as the target.
3. Or add a Create a thread action to a flow with the Threads node and pick a repository.

GitHub Issues is available to any account with the Thread Manager permission. If you already run Threads into Jira or Linear, nothing changes; GitHub connects alongside them. The feedback we want most is from teams filing real insights into real repositories: which fields are missing, what the issue body should carry, and whether the thread status kept up with the work.