When one project moves between Claude Code, Codex and other coding agents, each of them keeps its own history, in its own format and its own place. AgentSync MAX collects those histories under the project they belong to, where you, and an agent you point to them, can find what earlier sessions did.
History that follows the project
The sync engine links sessions from Claude Code, Codex, Antigravity, OpenCode, Cline and Junie to the project they ran in, and keeps each provider's history in its native form under the project's .agent-state/ folder. Formats and restore capabilities differ by provider, and Junie's history is collected but not restored. Aider can write its history into the project directly. One provider still cannot resume another provider's session, and an agent does not read all of the history automatically.
Missions in one workspace
The desktop app runs missions with the coding agent CLIs you have installed and signed in to, in the project you choose. It shows each mission's live output, activity and history, and the file differences it made. A project with a clean Git baseline has its changes tracked with Git. An ordinary folder, or a worktree with uncommitted changes, gets a local checkpoint instead, so Git is not required for every project. Authentication, permissions, model availability and billing stay with each provider's CLI.
A second agent can check the work
Validation is optional, and its switch is off each time the app starts. When you turn it on, a completed mission that changed files can be checked by another configured agent or model. A blind check runs in a temporary copy without the selected history, Git metadata, dependency folders and recognized secret files, and its findings go to a register where a person decides what holds. A reported fix stays a claim until someone has checked it.
Reports and project memory
Status, recovery-audit and session-metadata reports can be opened without the desktop app. An optional, bounded local index of recent project sources is kept on disk, with a RAM cache in the process. With context sharing on, a mission that writes can start from a short entry that links recent missions, findings and session metadata to their sources. The entry points to the records and does not summarize decisions, and agents started outside AgentSync MAX do not find it by themselves.
Boundaries
- AgentSync MAX is a source preview: desktop 4.26.2 and sync engine 4.25.1. It comes as source, with no signed installer or binary release. Some of its interface text is still Norwegian, and it has been used in one owner's workflow, which does not validate it across other machines, teams or provider versions.
- Native history can contain prompts, source code, terminal output and secrets. Keep
.agent-state/, missions, checkpoints, local settings and generated reports out of public Git. - A synchronized copy is not a tested backup, and a checkpoint is rollback data with a retention limit. Keep an independent backup and test restoring it. AgentSync MAX supplies no encryption, cloud sync or guarantee of recovery.
- A blind check reduces the context an agent is given. It is not an operating-system sandbox: each agent CLI keeps its own permissions, authentication and network access.
- The optional external watch uses the AI SENSE Heartbeat
and Webhook capture APIs to record when a process stops sending heartbeats. It is on by default in a new profile and is switched off in the desktop settings, separately from the sync adapters. Local sync, memory and missions do not depend on it.
Build and start it
The sync engine runs on PowerShell 7 or later and has Windows, macOS and Linux paths. The desktop app is Windows-first and builds with Rust and Cargo on the MSVC toolchain, Microsoft C++ Build Tools, WebView2, Node.js and Pester 5 or later. Read the installation guide first: the public configuration starts with every agent adapter disabled, you set the project root and enable the adapters you want, and the first runs belong in a disposable project. From the repository root:
pwsh -NoProfile -File ./Build-AgentSync-Max.ps1 -Publish
pwsh -NoProfile -File ./Start-AgentSync-Max.ps1The build runs the test gates before it builds. -Publish copies the verified executable into the local desktop/dist folder and uploads nothing. The source, the installation guide and the security notes are at github.com/aisenseapi/AgentSyncMax, under the MIT license. Bug reports are welcome there with a minimal, sanitized reproduction, without complete agent sessions or private project data.