What's new · July 2026

July 2026

You can now run independent milestones in parallel and review the same milestone as a team. We've also made upstream sync fully available.

ReleaseJuly 2026
Updates4
ProductMorph

You can now run independent milestones in parallel and review the same milestone as a team. We've also made upstream sync fully available.

Parallel milestones

Milestones now declare dependencies on one another. When milestones are independent, with no shared file dependencies, they can execute simultaneously, each on its own branch and producing its own PR. Dependent milestones remain locked until their prerequisites merge.

This means faster delivery without sacrificing PR review boundaries. You still review and merge each milestone individually; independent work just no longer waits in a queue.

When a milestone merges while sibling branches are in progress, Morph flags branches that need the new code as Rebase Required. Triggering the rebase is a single click, and the agent handles the integration.

Collaborative review

Multiple team members can now review the same milestone at the same time. Each reviewer gets their own independent review chat session, so conversations, issue triaging, and resolutions don't collide.

When one reviewer resolves an issue or the agent applies a fix, Morph propagates the workspace changes to other active reviewers so everyone sees the latest code. Chat sessions are locked to one active user at a time, but multiple reviewers can browse issues and code in parallel.

Per-user ModelDaemon

For self-hosted daemon deployments, the routing model is now one daemon per user instead of one daemon per project. Each team member's daemon handles that user's work and runs one active job at a time, so multiple team members can work on the same project simultaneously.

Daemon busy banner with locked milestones

The daemon reports its status in real time: online, busy, or offline. If your daemon is busy, new requests queue until the current job finishes.

Upstream sync

Upstream sync is now fully available. When your team pushes changes to the repository's mainline during the migration, you can trigger an upstream sync to incorporate them.

This creates a sync milestone, updates the project baseline, and rebases any in-progress milestone branches, all handled by the agent.