wake

Resume a stalled autonomous loop from its loop file and restart its cron heartbeat.

4|Updated Jun 9, 2026
One-click install
npx skills add https://github.com/laicluse/agent-fieldkit --skill wake-laicluse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wake
Source: https://github.com/laicluse/agent-fieldkit/tree/main/packages/autonomous/skills/wake
Command: npx skills add https://github.com/laicluse/agent-fieldkit --skill wake-laicluse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Autonomous agent loops can stall when a session ends, a cron job is lost, or the loop auto-stops after idle polls. This Skill revives those paused loops so long-running missions continue without manual reconstruction of their state. ## Core Features & Use Cases - Loop Revival: Reads the loop file in .autonomous/, checks the recorded cron_job_id liveness, and restores a fresh heartbeat via the keepalive and cron skills. - State Summary: Reports the loop's phase, last log entries, uncommitted changes, open PRs, and pending operator input before resuming work. - Safe Resumption: Acquires a concurrency lock before running one iteration so the fresh cron cannot fire the same iteration in parallel. - Use Case: After a Claude session restarts or context is compacted mid-mission, invoke wake with the loop file path to bring the stalled rover back to life and hand control back to its cron. ## Quick Start Ask the agent to wake the stalled loop by passing the path to its loop file in the .autonomous directory so it resumes with a fresh heartbeat.

Frequently Asked Questions about wake

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

FAQPage Schema
How do I resume a stalled autonomous agent loop?▼

Invoke the wake skill with the path to the loop file in the .autonomous directory. It reads the recorded state, checks cron liveness, restores a heartbeat if the session is interactive, and runs one iteration of the current phase.

What happens to the cron job when a loop is woken?▼

Wake re-decides keep-alive for the new session. Interactive sessions get a fresh cron scheduled at the active cadence, while persistent processes record none and drive the next iteration directly without a heartbeat.

Can wake recover a loop after context compaction?▼

Yes. After compaction, conversation summaries usually contain phase words like SURVEY, DRIVE, INSPECT, or STANDBY. If those appear alongside a loop file, wake is the preferred path over manual takeover.

Does wake modify the loop's plan or push changes?▼

No. Wake never modifies the loop's Plan or Context sections, which serve as the loop's memory, and it performs no pushes. It only summarizes state and runs one locked iteration locally.

Why does wake fail when no loop file path is given?▼

Wake is designed to be invoked only via the rover entry point, which always passes a path. A missing argument is treated as a caller bug and surfaced to the operator rather than guessing which loop to revive.