You're not lost.Neither are your agents.Your users? Definitely not.

what changed? is one shared log of everything your agents and your team ship. You catch up in seconds. Agents read it before they start. Your users get release notes a person approved.

Start your log Try the board

Private log

3 changes today

Release draft

Nothing yet

Drop changes here

or tap them in the log

Where it goes

Waiting

Websiteorbit.app/changelog
Waiting for approval
In-appOrbit widget
Waiting for approval
Email1,204 subscribers
Waiting for approval
Slack#product-updates
Waiting for approval

This board is the real workflow in miniature. Drag a card, cut the hype, stamp it and send it. No AI of its own: your agents draft through MCP.

Your agents check in before they start.

Give Claude, Codex or any MCP client a token. Before it works, it reads what the others changed. When it finishes, it records its own change, signed with its name.

Two agents, one codebase. Each sees what the other shipped since its last session.
Every change has an author. Agents, GitHub, KRNL OS and people are all named in the log.
They can't publish. Unless you give a token that permission yourself.

Read the agent docs

ClaudeConnected to what changed? over MCP

entry.list {"since": 1760724000000}

7 changes since your last session

Codex Fixed Restored files keep their upload date

Maya Improved Saved views sync across devices

GitHub Internal Bump vite from 8.0.12 to 8.0.13

Claude New Saved views for each project

and 3 more. Nothing here clashes with your task.

{
  "mcpServers": {
    "what-changed": {
      "url": "https://changes.krnl.studio/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_PRODUCT_TOKEN" }
    }
  }
}

Blue pencil never prints.

Editors write private notes in non-photo blue because the printing camera can't see it. Your log works the same way. Flip the switch and watch the private parts drop out.

Imports never publish.: Bring in GitHub releases or an old changelog and nobody gets notified.
Approval covers one revision.: Change a word after approving and it needs approving again.
Agents draft. People publish.: Publishing is a separate permission you give a token on purpose.
Keys stay on the server.: Destination credentials never reach the browser or an agent.

Your logWhat users see

Private log Orbit, this week

Saved views for each project
Rename useFilters to useProjectFiltersno UI change
Restored files keep their upload date
Bump vite from 8.0.12 to 8.0.13chore
Saved views sync across deviceschecked on iPad
Backfill legacy source idsnot until the migration ends
Long company names fit on invoices

Write it once. Every place gets its own version.

The website gets the full story, the app gets a short card and Slack gets a one-liner. Each one has its own wording, time and receipt.

Hosted changelogThe full release
In-app widgetA short card
Website embedYour feed, your styles
RSSEvery release
EmailSent with your Resend account
SlackA channel message
DiscordA community post
GitHub ReleasesA tagged release
LinkedInA post
XA short post
PayloadA native entry
WordPressA post
WebflowA CMS item
GhostA post
ContentfulAn entry
SanityA document
WebhooksA signed payload
KRNL OSIts own Releases screen

We ship ours with it.

17 October 2026, 0.1.0-alphaThe hosted alpha is hereCapture changes privately. Publish reviewed updates across your products.Read the release

A few details.

Does it write the notes for me?

No. It has no AI of its own. Your agent drafts through MCP, or you write the release yourself. Either way, a person edits and approves it here.

Does a deploy publish a release?

Only if you turn that on. By default you publish by hand. With it on, a deploy publishes only a release you approved and queued for that deploy.

What if a destination fails?

Each destination has its own receipt. Retry the one that failed without sending the others again. If a result is unclear, you check it before anything sends twice.

Can I bring my old changelog?

Import GitHub releases, chosen pull requests, Markdown or JSON, and review them before saving. Imports never notify subscribers.

Does it work with KRNL OS?

Yes. Link a KRNL OS project to a product. Finished issues can go straight into the log, and the project gets its own Releases screen.

Stay in touch with everything you ship.

Start your log