host-schedule

Schedule one-off or recurring commands from container sessions via the host bridge.

6|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/verkyyi/always-on-claude --skill host-schedule
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: host-schedule
Source: https://github.com/verkyyi/always-on-claude/tree/main/scripts/runtime/claude-home/skills/host-schedule
Command: npx skills add https://github.com/verkyyi/always-on-claude --skill host-schedule

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Schedule one-off or recurring commands from always-on-claude container sessions through the host scheduling bridge. The host validates requests, submits them to atd, and later runs the command back inside the claude-dev container.

Core Features & Use Cases

  • Schedule tasks to run later on the host via the always-on-claude bridge.
  • Use cases include after-hours automation, nightly checks, and recurring jobs using atd/cron style scheduling.
  • This workflow enables seamless off-hours automation directly from a container session.

Quick Start

Use the repo-managed aoc-schedule CLI to schedule a command on the host bridge with a one-off or cron schedule.

Frequently Asked Questions about host-schedule

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

FAQPage Schema
How do I schedule a container task to run after-hours from an always-on session?

The host scheduling bridge uses the aoc-schedule.sh script to submit validated commands to atd, which later executes them inside the claude-dev container. This enables seamless after-hours and overnight automation directly from an always-on container session.

Can I run recurring cron jobs from inside a claude-dev container?

Yes, you can run recurring cron jobs from inside a claude-dev container by submitting cron-style schedules through the host bridge. The host validates requests and enqueues them via atd to execute at specified intervals.

What is a host scheduling bridge and how does it work for container automation?

A host scheduling bridge allows container sessions to queue commands on the host system. The host validates requests, submits them to atd, and executes commands back inside the container later, enabling off-hours automation without keeping the session active.

Do I need atd or cron configured on the host to schedule container commands?

Yes, the host scheduling bridge relies on atd to queue and execute scheduled commands. The host must have atd running to process validated scheduling requests submitted from the always-on-claude container session.

Are there guardrails preventing unauthorized actions when scheduling tasks on the host?

Yes, the host scheduling bridge enforces safe host operations with guardrails to prevent unauthorized actions. All commands submitted from the container session are validated before being passed to atd for execution.