Skip to content
NewsProduct launch

GitHub Copilot September 7 releases: Jira canvas integration and VS Code agent automations reach public preview

· by Pondero Newsdesk

The short version

GitHub shipped Jira integration for the Copilot app on September 10, letting teams pull Jira issues into a shared canvas and drive them through investigation and pull request prep. VS Code 1.137 adds recurring agent automations in public preview alongside experimental voice mode.

GitHub Copilot September 7 releases: Jira canvas integration and VS Code agent automations reach public preview

GitHub published four Copilot updates on September 10, 2026 per its official changelog. The two with the most immediate operational impact are Jira issues landing in the Copilot app's shared canvas and VS Code 1.137 adding the ability to schedule recurring agent tasks on a clock.

What shipped

The Copilot app now connects to Jira. Developers can bring Jira issues into a shared canvas alongside existing Azure DevOps and Microsoft Foundry connections, select which issues move forward, and let Copilot carry the full context through investigation, implementation, and pull request preparation. The practical result is that a Jira ticket becomes the starting point for code work rather than a separate browser tab to juggle.

VS Code 1.137 shipped three Copilot additions in this cycle. Recurring agent automations entered public preview: teams can schedule agent tasks to run hourly, daily, or weekly, or trigger them on demand without writing custom scripts. Voice mode reached experimental status, allowing developers to talk to, interrupt, or redirect Copilot mid-session. A third experimental feature lets developers review issue and pull request details directly inside the Agents window without opening the repository first.

JetBrains users received an enterprise governance addition in the same release window. Enterprise administrators can now configure sandbox behavior centrally for GitHub Copilot in JetBrains IDEs, with managed policies covering sandbox enablement, filesystem access, network access, proxy settings, developer-tool access, and macOS Keychain access. That capability entered public preview.

One more update in the September 7 cycle, Project HydraFusion for Copilot CLI, reached the /experimental flag and handles automated routing between local, cloud, and compound models. That story was covered in Pondero's separate September 7 HydraFusion article.

Why it matters

The Jira integration is the change enterprise teams have waited for. Before this release, a developer had to switch between Jira and their editor to line up a ticket against code work. Copilot now holds both ends of that handoff. For engineering organizations that track time lost to context-switching, this closes a gap that had kept full workflow consolidation out of reach.

The VS Code automations shift how teams can deploy Copilot. Scheduled tasks mean routine code-health checks, dependency audits, or test generation can run on a clock rather than only when a developer explicitly prompts them. That positions Copilot closer to a background process than a conversational assistant, which is a meaningful change in how AI coding tools fit into a team's day.

JetBrains sandbox governance gives security teams a meaningful control layer. The ability to lock down filesystem and network access through managed policy means regulated organizations can enable Copilot in JetBrains without granting blanket system permissions.

What to watch next

Whether the Jira canvas integration expands to other project-management tools is the obvious follow-on. Linear and Asana are natural candidates, since GitHub Issues already integrates natively and Jira was the enterprise-priority holdout. VS Code agent automations are in public preview; based on GitHub's track record, general availability typically follows within two to three release cycles. The JetBrains enterprise sandbox is on the same path.

Sources