moirai.to · An October open-source project.
Moirai discovers local agent sessions, translates their portable context into a
canonical transcript, writes the destination's native session representation,
and can launch the destination harness. Messages, tool calls and results,
reasoning that the source explicitly stored, images, artifacts, usage, workspace
metadata, and ancestry survive when the destination can represent them.
It is a local-first Go library and CLI with a typed TypeScript SDK. The
open-source tools require no Moirai account, daemon, hosted service, or
credential collector.
Ordinary chats, too
Moirai also handles plain system / user / assistant conversations. Import
OpenAI-style chat JSON or discover Concord's saved chats, preserve message order
and model information, and create portable .moirai archives—all locally.
moirai list --format concord
moirai convert conversation.json --from chat --to simple --out canonical.json
moirai archive create conversation.json --from chat --out conversation.moirai
moirai continue conversation.moirai --with chat
The chat destination saves local JSON without starting a process. The Concord
destination stages a new import file and opens the app's confirmation dialog on
macOS; it never rewrites the app's live database. See chat formats and setup
for the required Concord build, exact round-trip contract, and degradation warnings.
Free and hosted versions
Use Moirai locally to switch harnesses, or use the optional Cloud service to
keep session files online. Local conversion never requires an account or upload.
The website is moirai.to; Cloud is currently a restricted
pilot, not open registration or a paid subscription.
Open source: free and local
The CLI, Go library, canonical schema, and TypeScript SDK in this repository
are free and open source. They discover and convert sessions on the same
machine without sending them to October. You can:
- continue a session in another supported harness;
- create portable, integrity-checked
.moirai archives;
- move an archive to another machine using storage or transport you control;
- build integrations directly on the Go and TypeScript APIs; and
- keep working without an account, hosted dependency, or usage plan.
This local version is the foundation of Moirai, not a limited client for the
hosted product. It remains useful on its own and keeps session data under the
user's control.
Private Cloud backups (restricted pilot)
The pilot backs up original Codex and Claude Code files, separately from
converted .moirai archives. Uploads are explicit, encrypted in storage, and
accessible only to their owner through the service. Original files are not
redacted and can contain secrets; storage encryption is not end-to-end encryption.
- Chunked uploads resume interrupted transfers.
- Each successful upload is downloaded and SHA-256 checked against the original.
- Restores create a new file without overwriting an existing one.
- Local sessions are never automatically deleted.
Approved pilot accounts can open their backups.
The dashboard lists files and backup status; it is not yet a conversation reader.
The pilot uses a separate moirai-sync companion maintained with the private
backend, not a command included in the public CLI release. It backs up files
under selected session directories, not project repositories or a whole computer.
Keep local originals until you have independently checked a restored copy.
Cloud sharing client
This public repository contains the core library, CLI, TypeScript SDK, and local
sharing preparation. The hosted backend, landing page, dashboard, and deployment
configuration are maintained separately in a private repository. The CLI can
connect to a configured Moirai service. The current pilot runs at
https://moirai-cloud.onrender.com; moirai.to serves the public website.
Only approved accounts can sign in to the pilot. Local functionality requires
no hosted account. Shared checkpoints below are separate from original-file backups.
Prepare and inspect an archive locally before publishing:
moirai login --server https://moirai-cloud.onrender.com
moirai publish 'SESSION_ID#12-38' --from claude_code --preview-out reviewed.moirai
moirai publish reviewed.moirai --visibility private --yes
moirai invite PUBLICATION_ID --login teammate
The preparation step strips workspace metadata and persisted thinking, omits
local media references, and redacts recognizable token patterns. Inspect the
entire prepared archive: tool output, metadata, and inline media can still contain
sensitive material. Uploads are explicit, immutable, and private by default.
Use --visibility unlisted for anyone-with-the-link access or public for public
access. The default expiry is seven days; --expires 0 disables expiry.
On another machine:
moirai pull https://YOUR_MOIRAI_ORIGIN/s/PUBLICATION_ID --out session.moirai
moirai continue session.moirai --with codex --dry-run
moirai continue session.moirai --with codex
moirai publish DERIVED_FILE --parent PUBLICATION_ID --yes
Prepare the destination repository separately. Continuing creates a fresh native
session and surfaces compatibility warnings. moirai unpublish ID --yes revokes
future service access; moirai cloud-delete ID --yes deletes the live archive.
Neither operation can recall downloaded copies or independent forks.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
