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.

Why Changelog

Unified visibility. Coordinated action. Cross-repo awareness for agents.

Visibility Portfolio-wide change visibility Every pull request, commit, and in-flight change across every repository and SCM system, scoped to your organization.
Action Bulk action at any scope Approve, merge, or close pull requests across hundreds of repositories without leaving the platform.
For agents Operational context for agents Coding agents query Changelog through MCP and GraphQL to understand what is in flight before they act.

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.

ApproachWhat it gives youWhere it falls short
GitHub / GitLab / Bitbucket Pull requests and commits inside one repositoryNo cross-repository view, no bulk action across repos, no agent API
SCM notifications A passive activity stream of PRs and commitsRead-only and brittle: no filtering, no action surface, no agent access
Internal dashboards Custom rollups of PR data across reposUsually 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 APIBy 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.

Step 01 Overlays your existing SCM systems Connects to GitHub, GitLab, Bitbucket, and internal VCS — including separate network segments — scoped to your org structure as defined in Moderne.
  • Works across every SCM system you already use
  • Inherits your SSO; SCM tokens authorize write operations
Step 02 Surfaces every change as a filterable feed Filter by PR type, review state, check results, contributors, or repositories, and search title text across every in-flight change.
  • Search and filter across every PR in one feed
  • Recipe-driven changes group as changesets across repos
Step 03 Enables bulk action across any filtered set Approve, merge, or close pull requests across hundreds of repositories at once, with available actions reflecting the real-time state of your selection.
  • Approve, merge, or close in bulk across any filtered set
  • Triage an entire initiative from one view
Step 04 Exposes the same view to coding agents Agents read system-wide change context through Moderne’s MCP server and GraphQL API instead of scanning repositories to figure out what changed.
  • Agents query active changesets via MCP and GraphQL
  • Prevents sequencing changes incorrectly across dependencies

Use cases

What you can do with Moderne Changelog

Coordinate large-scale initiatives Track Spring Boot migrations, CVE remediation, and framework upgrades across every affected repository in one view.
Distinguish automated from manual changes Recipe runs, agent edits, and hand-written commits each get tagged, so reviewers know how much scrutiny each needs.
Sequence changes across dependencies See what is ready, blocked, or waiting, so shared libraries publish before dependent services update.
Clean up stale work Identify and close pull requests that pile up during long-running initiatives, without touching individual repos.
Give agents operational awareness Agents read in-flight change state through MCP and GraphQL instead of burning tokens scanning repos.
Close the agent loop across repos Agents download changeset results, refine edge cases, and push updates back as part of the same coordinated effort.

The payoff

End fragmented review. Coordinate change across systems.

Unify End fragmented review Every PR across every repository in one feed, with bulk action available at any scope.
Save tokens Stop wasting tokens Agents reason from system-wide change context instead of reconstructing it on every run.
Coordinate Coordinate change across systems Multi-repository initiatives stay in one place, from kickoff through merge.

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.

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.