Vigil Agent Hook Deployment and Sleep Hold Configuration (Onboarding)

Vigil Agent Hook Deployment and Sleep Hold Configuration (Onboarding)

1. 01

   Confirm the client Mac runs macOS 14 or later and that the developer's agent stack is one of Claude Code, Codex, Cursor, Gemini CLI, Copilot CLI, pi, or OpenCode.

   Vigil has no Windows or Linux build, so a mixed-OS client team needs a per-machine decision before you quote any deployment hours.

2. 02

   Purchase the Vigil license at $3.99 one-time and activate the key on the first Mac.

   One license key activates two Macs, which covers a two-developer pod without a second purchase. The 30-day refund window is the client's exit if the hook test fails.

3. 03

   Install the lifecycle hooks for the client's primary agent and verify the menu bar dashboard registers the session.

   Start with one agent only. Confirm the dashboard shows the working state before adding a second agent, otherwise you cannot tell which hook is misconfigured.

4. 04

   Set the configurable grace period to match the client's expected input-wait window.

   The hold releases when the agent finishes, fails, or waits too long. A grace period shorter than the client's real review pause will drop the sleep hold mid-session.

5. 05

   Run a supervised agent session and watch the menu bar dashboard move through working, waiting, and idle states.

   Track multiple sessions and sub-agents during this run so the client sees how nested agent activity appears in the dashboard before they rely on it unattended.

6. 06

   Document the hook configuration and timeout thresholds in the client handoff file.

   Record which agent each hook belongs to and the grace period value chosen. The client's next developer hire inherits a written config instead of a guess.

7. 07

   Train the client on menu bar controls and session monitoring, then close the onboarding retainer line.

   The Vigil Solo Dev Setup offer prices this work at $700 across 6h of setup for a solo practitioner or freelance developer.