checkpoint-mode

Pauses autonomous agent execution every N tasks for human review and approval.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/CYRUS-pinto/pi-bot --skill checkpoint-mode-cyrus-pinto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkpoint-mode
Source: https://github.com/CYRUS-pinto/pi-bot/tree/main/.agents/skills/loki-mode/agent-skills/checkpoint-mode
Command: npx skills add https://github.com/CYRUS-pinto/pi-bot --skill checkpoint-mode-cyrus-pinto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Fully autonomous agents can waste resources on wrong approaches, miss course corrections, and leave users disconnected from progress. This Skill implements selective autonomy by pausing work at configurable intervals so users can review summaries and approve continuation. ## Core Features & Use Cases - Configurable Pause Frequency: Pause after N tasks or M minutes using environment variables like LOKI_CHECKPOINT_FREQUENCY and LOKI_CHECKPOINT_TIME. - Checkpoint Summaries: Generates structured summaries of completed tasks, next actions, and resource usage (time, agents, cost) at each pause. - Signal-Based Approval: Writes checkpoint summaries to .loki/signals/ and waits for a CHECKPOINT_APPROVED signal file before resuming. - Use Case: When starting a novel project where the approach may need adjustment, enable checkpoint mode to review progress every 10 tasks, correct course early, and maintain an audit trail of approvals. ## Quick Start Set LOKI_AUTONOMY_MODE=checkpoint and LOKI_CHECKPOINT_FREQUENCY=10, then ask the orchestrator to run the project so it pauses for your approval after every ten completed tasks.

Frequently Asked Questions about checkpoint-mode

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

FAQPage Schema
How do I make an autonomous agent pause for review periodically?

Enable checkpoint mode by setting LOKI_AUTONOMY_MODE=checkpoint and configuring LOKI_CHECKPOINT_FREQUENCY for task count or LOKI_CHECKPOINT_TIME for minutes. The orchestrator pauses, writes a summary, and waits for your approval signal.

When should I use checkpoint mode vs perpetual autonomy?

Use checkpoint mode for novel projects, expensive operations, or learning phases where course correction matters. Use perpetual mode for well-defined PRDs, established patterns, overnight builds, and CI/CD pipelines needing full automation.

How does the checkpoint approval workflow work?

The orchestrator writes a CHECKPOINT_SUMMARY markdown file to .loki/signals/ and pauses execution. You review the summary and create a CHECKPOINT_APPROVED signal file, which the orchestrator detects to resume work.

What information is included in a checkpoint summary?

Each summary lists completed tasks, planned next actions, and resources used including elapsed time, agent counts by model tier, and estimated cost. Metrics are stored in .loki/metrics/checkpoint-mode/ for tracking.

Can I force checkpoints after specific phases?

Yes, set LOKI_CHECKPOINT_PHASES to a comma-separated list such as architecture,deployment. The orchestrator will always pause after those phases regardless of the task-count frequency setting.