Every pull request, commit, and in-flight change across every repository and SCM system, scoped to your organization.
Approve, merge, or close pull requests across hundreds of repositories without leaving the platform.
Coding agents query Changelog through MCP and GraphQL to understand what is in flight before they act.
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.
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.
Changelog connects to GitHub organizations, Bitbucket instances, GitLab deployments, and internal VCS systems, including separate network segments. The view is scoped to your organization structure as defined in the Moderne Platform.
Filter by pull request type, review state, check results, contributors, or repositories. Search title text across every PR. Transformations driven by Moderne recipes surface as changesets, grouping every affected repository into a single coordinated effort.
Approve, merge, or close pull requests across hundreds of repositories at once. Available actions update dynamically based on the real-time state of what you have selected, so you triage an entire batch without touching individual repositories.
Agents access Changelog through Moderne's MCP server and GraphQL API to understand what is already in flight before they act. Instead of scanning repositories to figure out what has already been changed, agents read system-wide change context directly.
Track Spring Boot migrations, CVE remediation, and framework upgrades across every affected repository in one view.
Recipe runs, agent edits, and hand-written commits each get tagged, so reviewers know what level of scrutiny each one needs.
See what is ready, blocked, or waiting so shared libraries publish before dependent services update.
Identify and close pull requests that pile up during long-running initiatives, without touching individual repositories.
Agents read in-flight change state through MCP and GraphQL, instead of burning tokens scanning repos to figure out what changed.
Agents download changeset results, refine edge cases, and push updates back as part of the same coordinated effort.
Every PR across every repository in one feed, with bulk action available at any scope.
Agents reason from system-wide change context instead of reconstructing it on every run.
Multi-repository initiatives stay in one place from kickoff through merge.

How Changelog gives engineers and AI coding agents a unified control plane for cross-repo change.
See how Prethink works under the hood and how to tailor context for your repositories and agent workflows.
Compiler-accurate codebase context for coding agents, the structural pillar of Moderne's agent tools.
Moderne Changelog is a unified control plane that overlays existing source code management 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. Moderne 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.