start-inbox-monitor

Arms a session-scoped inbox monitor using native Codex, Claude, or Antigravity lifecycle tools.

Updated Jul 12, 2026
One-click install
npx skills add https://github.com/sumitake/agent-collab --skill start-inbox-monitor-sumitake
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: start-inbox-monitor
Source: https://github.com/sumitake/agent-collab/tree/main/plugins/agent-collab/skills/start-inbox-monitor
Command: npx skills add https://github.com/sumitake/agent-collab --skill start-inbox-monitor-sumitake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Cross-agent collaboration requires watching an inbox for new messages, but each host (Codex, Claude, Antigravity) has a different wake model, and hand-rolled polling loops, cron jobs, or duplicate monitors cause wasted model turns and unsafe lifecycle states. This Skill arms exactly one durable, session-scoped inbox monitor using the correct host-native mechanism. ## Core Features & Use Cases - Host-native lifecycle selection: Uses Codex long-running exec sessions, Claude's persistent Monitor tool, or Antigravity's asynchronous run_command instead of a universal polling loop. - Strict session and runtime validation: Resolves strong session identifiers per host, verifies the canonical installed monitor runtime with ownership and symlink checks, and refuses placeholder or cross-session IDs. - Typed result contract: Returns precise outcomes such as armed, already_armed, degraded_no_event_wake, startup_failed, sandbox_blocked, or stopped instead of generic success. - Legacy Codex goal migration: Fail-closed transcript analysis and decision tables for safely detaching or stopping pre-4.5.3 goal-based monitors. - Use Case: A user says "start the inbox monitor" in a Claude session; the Skill validates the session ID, launches the canonical inbox-polling-monitor via the Monitor tool, verifies the five-line startup output, and reports armed with the retained task ID. ## Quick Start Ask the agent to start the inbox monitor for the current session so new cross-agent messages trigger a notification.

Frequently Asked Questions about start-inbox-monitor

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

FAQPage Schema
How do I start an inbox monitor for cross-agent messages?▼

Invoke the start-inbox-monitor skill explicitly in your session. It resolves the current host and session ID, verifies the canonical installed monitor runtime, and launches the host-native monitor, returning a typed result such as armed or already_armed.

How does inbox monitoring differ between Codex, Claude, and Antigravity?▼

Codex uses a long-running exec_command session with a process lease, Claude uses its native Monitor tool with persistent: true, and Antigravity uses asynchronous run_command that wakes on task exit. Each adapter has its own startup proof and result mapping.

Can I use a cron job or polling loop instead of this monitor?▼

No. The skill explicitly forbids scheduled or recurring automation, cron, launchd jobs, heartbeat tasks, and inline polling loops. Monitoring must use the host-native lifecycle so the model is only woken by real events.

Why does the monitor report degraded_no_event_wake on Codex?▼

Codex returns degraded_no_event_wake when the local monitor process is live but no host-native event mechanism is proven to wake the model. A bare busy lease or clean startup alone never maps to armed without separate event-wake proof.

What happens if a second inbox monitor is already running?▼

The canonical monitor script acquires a shared session-scoped kernel lease, so a duplicate launch reports another monitor is running. Claude and Antigravity map this to already_armed, while Codex treats a bare busy lease as degraded_no_event_wake.

How do I stop the inbox monitor safely?▼

An explicit stop persists a durable stopped marker via the monitor-session-state script before terminating the native task or exec. The marker survives compaction and session rehydration, and only a new explicit start clears it.