MOLT — carry work across harnesses
Alias for the MOLT continuity system: cross-harness-state +
session-handoff. MOLT keeps durable, harness-agnostic work state as plain
Markdown inside a repo's .agents/ folder, so the next session — any agent,
any machine that syncs the repo — resumes from files, not from a chat
transcript.
When to use it
- Starting or ending significant work in a repo.
- The user says save progress, update the state, journal this, resume from state, what were we doing, or pause this task.
- Switching agents or machines mid-task (including running out of credits) and continuity must survive.
How it works
Load cross-harness-state for the file contracts and session-handoff
when pausing mid-task:
.agents/STATE.md— NOW: current task + latest progress, with verification evidence per bullet. Read it first on resume..agents/JOURNAL.md— HISTORY: dated one-line decisions, newest first..agents/handoffs/— deep recovery docs, one per paused task, created viasession-handoff(scaffold, validate, check staleness on resume).
Rules: save at every phase boundary or stop point, so a credit-out loses
at most one phase. Commit .agents/ together with related code and push
before switching agents — a handoff file alone does not transfer
uncommitted code. Never write secrets into state files; reference them by
name only.
Provenance
Adapted from the MOLT system (README + harness-agnostic agent prompt +
AGENTS stanza + STATE.md templates). The _molt/ folder holds the source
system; this skill is the library's alias for it.