Review what belongs in the bundle
Choose the conversations, instructions, skills, and approved configuration that should travel.
Features
Move the context. Keep control.
Mallard packages selected project sessions and agent resources for deliberate transfer—not an entire profile, repository, or credential store.
Project sessions
Carry the reasoning with the project.
Resume selected Codex sessions on another machine and keep project-specific instructions close to the work they shaped.
Preview before applying
Fetch and verify a remote bundle, inspect the restore plan, then explicitly approve local changes.
History
Connect conversation to change.
Git projects map sessions to commits. Non-Git projects use reviewed snapshots through the same portable workflow.
Git-aware activity
Understand which session contributed to a commit and recover the decisions hidden behind the final diff.
session→commitRepository optional
Use Mallard with prototypes, research folders, and other projects that do not have Git history.
session→snapshotStorage
Choose where bundles live.
Connect the same project to multiple targets while keeping each target’s reviewed base independent.
Simple and inspectable
Use a filesystem location for manual transfer, backup, or team-shared storage.
Your account, your policies
Store bundles in a user-owned compatible object store with named machine-local profiles.
Managed option later
A planned authenticated service, clearly separate from the first release.