remote-triggerslisted

# Remote Triggers Create and manage remote agent triggers that execute on schedules and survive session exit. ## When to Use - **Persistent schedules**: Tasks that must run even after the session ends - **Cross-session automation**: Recurring code reviews, automated deploys, health checks - **Scheduled agents**: Run specific prompts on cron schedules in the background - **Team automation**: Set up shared triggers that benefit the whole team ## How It Differs from CronCreate | Feature | CronCreate | RemoteTrigger | |---------|-----------|---------------| | Survives session exit | No (session-only, in-memory) | Yes (server-side routine) | | Runs while REPL idle | Yes | Yes (server-side) | | Lifetime | Recurring jobs auto-expire after 7 days | No documented expiry; removed only at https://claude.ai/code/routines | | Minimum interval | Any (5-field cron, per-minute) | **1 hour** — `*/30 * * * *` is rejected | | Timezone | User's local time | **UTC** | | Runs where | The user's local session | Isolated cloud session with its own git checkout — no local files, services, or env vars | | Setup complexity | Low | Medium (needs `environment_id` + a full `job_config`) | | Requires auth | No | Yes — OAuth injected in-process by the tool, never exposed | **Rule of thumb**: Use CronCreate for in-session monitoring. Use RemoteTrigger for anything that must persist. For sub-hourly or event-driven watching, use neither — see `Monitor` in the `scheduled-tasks` skill. ## Tool: RemoteTrig