Agent Tools · Coordination
Multi-repository change visibility and control
Moderne Changelog gives engineering teams and coding agents a single view of everything changing across the codebase, so initiatives stay coordinated instead of fragmented across repositories.
From source control to change control
Approve, merge, or close across hundreds of PRs at once — agent and human change in one view.
Why Changelog
Unified visibility. Coordinated action. Cross-repo awareness for agents.
The idea
What is Moderne Changelog?
Source control systems answer one question: what changed inside this repository? Moderne Changelog answers a different one: what is changing across the organization? Changelog overlays your existing SCM systems to give you a portfolio-wide view of every pull request, commit, and in-flight change.
This isn’t a dashboard, a PR tool, or a notifications layer. Existing tools answer questions about individual repositories; Changelog answers questions about your portfolio.
How it compares
Source control tracks one repository. Changelog tracks the whole organization.
Existing tools each answer a slice of the question. Changelog is the one view that spans every repository and exposes the same state to agents.
| Approach | What it gives you | Where it falls short |
|---|---|---|
| GitHub / GitLab / Bitbucket | Pull requests and commits inside one repository | No cross-repository view, no bulk action across repos, no agent API |
| SCM notifications | A passive activity stream of PRs and commits | Read-only and brittle: no filtering, no action surface, no agent access |
| Internal dashboards | Custom rollups of PR data across repos | Usually read-only and home-grown, with no bulk action and no agent API |
| Moderne Changelog | Every change across every repo and SCM, with bulk action and an agent API | By design, a control plane over your SCMs, not a replacement for them |
How it works
From source control to change control
Changelog surfaces every change across your codebase as a single, filterable feed, with bulk action available at any scope and the same view exposed to coding agents.
- Works across every SCM system you already use
- Inherits your SSO; SCM tokens authorize write operations
- Search and filter across every PR in one feed
- Recipe-driven changes group as changesets across repos
- Approve, merge, or close in bulk across any filtered set
- Triage an entire initiative from one view
- Agents query active changesets via MCP and GraphQL
- Prevents sequencing changes incorrectly across dependencies
Use cases
What you can do with Moderne Changelog
The payoff
End fragmented review. Coordinate change across systems.
Part of the agent toolset
Changelog is the Operate stage of Moderne’s agent toolset. The changes it tracks are produced by recipes and grounded in the Lossless Semantic Tree.
The agent toolset
- DiscoverTrigrepFind
- UnderstandPrethinkFrame
- ActRecipesFix
- OperateChangelogGovern
FAQ
Frequently asked questions
Moderne Changelog is a unified control plane that overlays existing source-control systems and gives engineering teams a single view of every pull request, commit, and in-flight change across their entire repository portfolio. Reviewers can approve, merge, or close PRs in bulk across any filtered set, and coding agents can query the same view through MCP and the Moderne GraphQL API.
Source control systems like GitHub, GitLab, and Bitbucket are designed to show what changed inside a single repository. Changelog answers a different question: what is changing across the entire organization, and is it coordinating properly? It surfaces every PR across every repository in one feed, supports bulk approval and merge, and exposes the same view to coding agents so they understand portfolio state before they act.
Changelog overlays GitHub organizations, Bitbucket instances, GitLab deployments, and internal VCS systems, including instances split across separate network segments. Connection is configured through the Moderne Agent, the same way Moderne already accesses your codebase.
Yes. Approve, merge, or close pull requests across hundreds of repositories from a single filtered view. Available actions update dynamically based on the real-time state of what is selected, so an entire batch can be triaged without opening individual repositories.
Manual edits, agent-driven modifications, and automated transformations such as Moderne recipe runs each carry different review expectations. Changelog preserves that distinction so reviewers can immediately see which parts of an initiative came from automation and which require human judgment, without navigating repository by repository.
Agents query Changelog through Moderne’s MCP server and GraphQL API to understand what is already in flight across the codebase. This replaces token-expensive repository scanning with direct access to system-wide change context, so agents can sequence changes correctly across dependency boundaries and avoid duplicating work that is already in review.
Changelog inherits your existing SSO, and write operations such as merging or closing PRs use the same SCM access tokens already configured for Moderne’s recipe execution. No new permission model is introduced.
A changeset is the logical unit of change that a Moderne transformation produces: every repository affected by a single recipe run, tracked together as one coordinated effort. Changelog surfaces changesets as a unit, so initiative progress is visible across all affected repositories instead of scattered across individual PRs.
Multi-repository changes often have an order of operations: a shared library must build and publish before dependent services can be safely updated. Changelog gives both humans and agents visibility into what is ready, what is blocked, and what is waiting across the entire changeset, so updates are sequenced correctly instead of breaking downstream builds.
Bring change control to your software estate.