Once a few agents are doing real work, their changes start arriving from everywhere. One agent rewrote the pricing copy in a note, another cleaned up rows in a data channel, a teammate edited the onboarding checklist, and something is still sitting in a sandbox on your laptop. The work is useful, but reviewing it means remembering where each change lives. osFoundry Merge Station puts all of it in one review list, and Versions shows who changed what.
One list for every proposed change
osFoundry is a desktop app that puts chat, agents, files and tools in one window. Merge Station collects merge requests from agents and teammates, plus work staged locally in sandboxes, into a single list. The header counts what's waiting (here 3 pending and 1 sandbox).
The Sandboxes section shows local work that hasn't been proposed yet, with its branch and how many files and lines changed. Under Merge requests, each row shows the title, its state (Open, Approved, or Conflicts), who opened it (an agent such as writer or data-steward, or a user), the source and target, and a one-line AI summary of what it touches, for example "Changes 2 sections of one note; no other entities touched." That summary is often enough to decide which request to open first.
Opening a request
A request opens on its Overview: the description, source, target, author, creation time and the AI Summary, with Approve and Reject. A request that needs approval says so ("Requires approval to merge"), so nothing an agent proposes lands on its own.
The Changes tab lists every changed item with its status (modified or created) and the before and after side by side. Here the agent shortened the pricing hero line and created a plan comparison. Each change can be downloaded as the pre-edit original or the post-edit version, which is handy when you want to check it in another tool.
When the target moved
If the target changed after the request was created, the request gets a Conflicts tab and a clear message: the target branch has changed since this branch was created, and conflicts must be resolved before merging. Resolve conflicts takes you to where you fix them. Until then the request can't be merged, so an agent working from a stale copy can't overwrite newer work.
Versions: who changed what
Merge Station is about what's waiting. Versions is about what already happened. It lists changes to notes, data channels, memory groups and more, each with its author, and the filter splits them into All, User, Agent and Maestro. In the example, the writer agent tightened a launch plan summary, a user added rows to a pipeline, and Maestro merged reviewer notes into the onboarding note.
Filtering to Maestro shows only what osFoundry's main assistant changed, which is the quickest way to answer "what did the AI touch today?" Selecting an entry shows its details: type, entity, author, timestamp and ID. On the desktop app, notes also keep restore points you can go back to.
The Review tab in Versions shows the merge requests waiting on you, filtered by status (Open, Approved, Merged or Closed), with Approve and Reject right there and a link to open them in Merge Station.
For code in repositories, osFoundry has GitNest, which brings change sets, checks and review context together in the same spirit.
Use case: a Monday morning review
Over the weekend, three agents worked on a product launch. On Monday, Sammy opens Merge Station and sees three pending requests and one sandbox. The AI summaries show that the pricing request only touches two sections of one note, so Sammy opens it first, reads the before and after in Changes, and approves it. The pipeline cleanup is already approved and gets merged. The onboarding checklist shows Conflicts because a teammate edited the same note on Friday, so Sammy resolves the conflict before merging.
Then Sammy switches to Versions, filters to Agent, and checks everything the agents changed directly over the weekend, without opening a single note to look for edits.
Questions people ask first
Can an agent merge its own changes?
Requests that require approval can't be merged until someone approves them, and a request with conflicts has to be resolved first. Merging needs the right permissions.
Can I see the change before approving it?
Yes. The Changes tab shows each changed item with before and after, and you can download the original and the edited version.
How do I find what an AI changed?
Open Versions and filter by Agent or Maestro. Each entry shows the author, the type of item and when it changed.
Is it free?
osFoundry is free to use on your own device. Work that runs on osFoundry's servers uses credits.
The desktop app is free to download at osfoundry.io/download.
Top comments (0)