Meet Moderne Changelog

Multi-Repository Change Visibility and Control

Schedule Demo
Moderne Changelog: unified pull request feed across repositories with bulk action panel

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

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.

Portfolio-wide change visibility

Every pull request, commit, and in-flight change across every repository and SCM system, scoped to your organization.

Bulk action at any scope

Approve, merge, or close pull requests across hundreds of repositories without leaving the platform.

Operational context for agents

Coding agents query Changelog through MCP and GraphQL to understand what is in flight before they act.

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.

It's Moderne Changelog.

Existing tools answer questions about individual repositories. Changelog answers questions about your portfolio.

Approach What it shows What's missing
GitHub, GitLab, Bitbucket What changed inside one repository No cross-repository view, no bulk action across repos
SCM notifications and digests A passive activity stream of PRs and commits No filtering, no bulk action, no agent access
Internal dashboards and scripts Custom rollups of PR data, often read-only Brittle, no action surface, no API for agents
Moderne Changelog Every change across every repo, with bulk action and an agent API Nothing.

How Moderne Changelog 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.

Overlays your existing SCM systems

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.

  • Works across every SCM system you already use
  • Scoped to organizations, teams, or business units as defined in Moderne
  • Inherits your existing SSO; SCM access tokens authorize write operations
Icon representing bracketed code

Surfaces every change as a filterable feed

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.

  • Filter by PR type, review state, check results, contributors, repositories
  • Search across every in-flight change
  • Recipe-driven changes group as changesets across repositories
Icon showing connection within a grid of dots

Enables bulk action across any filtered set

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.

  • Approve, merge, or close in bulk across any filtered set
  • Action availability reflects real-time PR state
  • Triage an entire initiative from one view

Exposes the same view to coding agents

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.

  • Agents query active changesets via MCP and GraphQL
  • System-wide context replaces repo-by-repo scanning
  • Prevents agents from sequencing changes incorrectly across dependencies

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 what level of scrutiny each one needs.

Sequence changes across dependency boundaries

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 repositories.

Give agents operational awareness

Agents read in-flight change state through MCP and GraphQL, instead of burning tokens scanning repos to figure out what changed.

Close the agent loop across repositories

Agents download changeset results, refine edge cases, and push updates back as part of the same coordinated effort.

End fragmented review. Coordinate change across systems.

Icon with individuals surrounding a gear

End fragmented review

Every PR across every repository in one feed, with bulk action available at any scope.

Icon representing a speedometer

Stop wasting tokens

Agents reason from system-wide change context instead of reconstructing it on every run.

Coordinate change across systems

Multi-repository initiatives stay in one place from kickoff through merge.

Bring change control to your software estate.

Dive Deeper

Blog

Change intelligence for multi-repository systems

How Changelog gives engineers and AI coding agents a unified control plane for cross-repo change.

agent tools

Moderne agent tools at scale

See how Prethink works under the hood and how to tailor context for your repositories and agent workflows.

product

Moderne Prethink

Compiler-accurate codebase context for coding agents, the structural pillar of Moderne's agent tools.

Frequently Asked Questions

What is Moderne Changelog?
How is Changelog different from GitHub or GitLab's pull request views?
Which source control systems does Changelog work with?
Can Changelog perform bulk actions across repositories?
How does Changelog distinguish automated changes from manual ones?
How do AI coding agents use Changelog?
Does Changelog require new permissions or access grants?
What is a changeset in Moderne Changelog?
How does Changelog handle dependency sequencing across repositories?