long-horizon-recovery

Maintains resumable multi-session agent work using local state files and compact checkpoints.

3|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/marcmarti9/agentit --skill long-horizon-recovery-marcmarti9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: long-horizon-recovery
Source: https://github.com/marcmarti9/agentit/tree/main/skills/long-horizon-recovery
Command: npx skills add https://github.com/marcmarti9/agentit --skill long-horizon-recovery-marcmarti9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running AI agent work loses all progress when a chat session ends or context limits are hit, forcing expensive reconstruction of decisions, constraints, and next steps. This Skill keeps substantial multi-session work resumable through private local state and checkpoints, without leaking working notes into the repository. ## Core Features & Use Cases - Local Continuity State: Records goals, constraints, complexity, risk, selected skills/tools, verification evidence, and next actions in .agentit/STATE.md and JSON checkpoints. - Checkpoint Commands: Provides agent-facing commands like agentit continuity init and agentit continuity checkpoint to snapshot milestones at meaningful moments. - Resume Protocol: Defines a fresh-session procedure that re-verifies recorded assumptions and explicitly re-selects non-core skills, references, workers, and MCPs instead of trusting stale context. - Use Case: An agent working on a multi-day refactoring hits a context limit mid-task; a new session reads the local state file, verifies the branch and evidence, rebuilds the task decision, and continues from the recorded next actions. ## Quick Start Ask the agent to initialize continuity state for the current substantial task and create a checkpoint before handing off to a new session.

Frequently Asked Questions about long-horizon-recovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume an AI agent task after the session ends?▼

Read the local `.agentit/STATE.md` file before re-asking resolved questions, verify recorded assumptions against the current repository, then build a fresh task decision and continue from the recorded next actions. Previous skill or MCP selections are historical evidence, not automatic activation.

When should I create a continuity checkpoint for agent work?▼

Checkpoint after the material task decision and review, after scope-changing user decisions, after expensive milestones, before provider or machine handoffs, and before stopping due to context limits or errors. Trivial work should not get continuity ceremony.

Where is Agentit continuity state stored?▼

State lives in `.agentit/STATE.md` and `.agentit/checkpoints/*.json` by default, kept local and private. It should not be committed to the repository unless the project explicitly chose a tracked team-status document.

What should not be stored in agent continuity state?▼

Never persist secrets, credentials, raw transcripts, or private chain-of-thought. Record only decisions, evidence, and consequences, along with concrete next actions, blockers, and the latest verification evidence.

Does a resumed session automatically keep previously selected skills and MCPs?▼

No. A resumed session starts from the three-skill core and must explicitly re-select every non-core skill, reference, worker, and MCP that remains justified by the fresh current task decision.