In an April 6 post on X, GitHub said Copilot cloud agent had become “a lot more flexible.” The linked changelog entry makes the change concrete: cloud agent is no longer tied to pull-request-only workflows. Previously, teams had to open a PR before the agent could start working. Now the agent can operate on a branch first, letting developers decide later whether the work is ready to become a reviewable proposal.

That shift matters because it expands the role of the agent from patch generation into earlier-stage engineering work. GitHub’s own framing is “research, plan, and code,” and the changelog breaks the release into sections on generating implementation plans and conducting deep research inside a codebase. In other words, GitHub is moving the cloud agent upstream, from something that reacts after work is packaged as a PR to something that can help shape the work before the PR exists.

GitHub is moving agent workflows closer to the start of development

Practically, this could change how teams use agents in large repositories. One of the expensive parts of a change is often not writing the patch itself, but figuring out where the change belongs, what constraints already exist, and how to sequence the work. Letting the agent research the codebase and generate an implementation plan on a branch makes it more useful as a collaborator during exploration, not just as a code-writing assistant once the path is already obvious.

This is not the same thing as removing human review. Working before a PR exists simply means the agent can investigate, draft, and iterate earlier in the workflow. But the signal is still meaningful: GitHub wants Copilot cloud agent to become part of the repository-native working surface, not a narrow post-PR automation step. Sources: the X post and GitHub’s changelog.

#cloud-agent

GitHub broadens Copilot cloud agent so teams can research, plan, and code before opening a PR