Once you start giving AI agents serious work to do, changes begin arriving from all directions. One agent rewrites the copy on a notebook's pricing page, another cleans up duplicate rows in a data channel, team members revise the onboarding checklist, and work still remains in your local sandbox. All of these are useful changes, but when you try to review them, you have to remember “where what happened.” osFoundry's Merge Station brings them together into a single review list. You can see who changed what in Versions.

All proposed changes in one list

osFoundry is a desktop app that brings chats, AI agents, files, and various tools together in a single window. Merge Station gathers merge requests from agents and team members, along with work underway in your local sandbox, into one list. The header displays the number of items waiting (here, 3 pending and 1 in the sandbox).

The sandbox section shows local work that has not yet been proposed, along with the branch name and the number of files and lines changed. In the merge requests section, each row lists a title, status (pending, approved, conflicted), author (an agent such as writer or data-steward, or a user), source and target, and a one-line AI summary. For example, a summary such as “Modified two sections of one notebook. No other changes.” lets you roughly determine which one to open.

Open a request

When you open a request, an overview appears first. It shows the description, source, target, author, creation date, and AI-generated summary, with Approve and Reject buttons. Requests requiring approval display “Approval is required to merge,” so an agent's proposal will not be automatically applied.

The Changes tab lists the modified items with their status (changed or newly created), allowing you to compare the before and after. In this example, the agent shortens the heading on the pricing page and newly creates a plan comparison. You can download the original pre-edit version and the edited version of each change, making it convenient to verify in other tools.

If the target changes first

If the target changes after the request is created, the request will have a Conflicts tab and a message saying, “The target branch has been changed since this branch was created. Please resolve the conflicts before merging.” You can proceed to the resolution screen by selecting Resolve conflicts. Since the request cannot be merged until the conflicts are resolved, an agent working from an older copy will not overwrite newer changes.

Versions: Who changed what

While Merge Station handles “what’s coming in,” Versions is a record of “what has already come in.” Changes to notes, data channels, memory groups, and more are listed with their authors, and you can filter them by All, User, Agent, or Maestro. In this example, the writer agent finalizes a summary of the launch plan, the user adds a line to the pipeline, and Maestro merges review notes into an onboarding note.

When you filter by Maestro in Versions, only changes made by osFoundry’s main assistant remain. It’s the quickest way to check “What has the AI touched today?” Selecting an item displays details such as type, entity type, author, timestamp, and ID. In the desktop app, restore points are also created for notes, so you can roll back to that point.

The Review tab in Versions lists merge requests awaiting your review. You can filter them by status (Open, Approved, Merged, Closed), approve or reject them right there, or select “Open in Merge Station” to view more details.

For repository code, GitNest brings together changesets, checks, and review context in the same way.

Use case: Monday morning review

Over the weekend, three agents had been preparing for launch. On Monday morning, Sammy opened Merge Station and found three pending requests and one sandbox. According to the AI summary, the pricing-page request only affected two sections of a single note, so Sammy opened it first, read the before-and-after changes in the Changes tab, and approved it. The pipeline cleanup had already been approved, so it was merged. The onboarding checklist had a conflict because a team member had edited the same note on Friday, so Sammy resolved it before merging.

Next, Sammy opened Versions and filtered by Agent to review everything the agents had directly changed over the weekend. There was no need to open each note and search for the changes one by one.

Frequently asked questions

Can agents merge their own changes on their own?
Requests that require approval cannot be merged until someone approves them. Requests with conflicts must also be resolved first. Appropriate permissions are required to merge as well.

Can I check the contents before approving?
Yes. In the Changes tab, you can view the before and after versions of each item, and download the original and edited versions.

How can I find what the AI changed?
Open Versions and filter by Agent or Maestro. The creator, target type, and modification date are displayed for each item.

Is it free to use?
osFoundry is free for use on your own device. Features that process data on osFoundry's servers use credits.

The desktop app can be downloaded for free fromosfoundry.io/ja/download.