agentwire-scheduler

Orchestrates overnight Docker builds and automated deployments for Bitbucket repositories.

19|6|Updated Dec 31, 2025
One-click install
npx skills add https://github.com/dotdevdotdev/agentwire-dev --skill agentwire-scheduler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentwire-scheduler
Source: https://github.com/dotdevdotdev/agentwire-dev/tree/main/.claude/skills/agentwire-scheduler
Command: npx skills add https://github.com/dotdevdotdev/agentwire-dev --skill agentwire-scheduler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of coordinating overnight AI agent sessions, gating tasks by repository changes, dependencies, and time windows, so work can be prepared during the day and dispatched automatically during off-hours.

Core Features & Use Cases

  • Gate-based task dispatch: skip tasks when git commits or diffs haven't changed or external conditions fail.
  • Flexible scheduling: define every/everyday at not_before/not_after, with delays, cooldowns, and dependencies.
  • Overnight session orchestration: prepare, queue, and dispatch Claude sessions across projects with workflow-backed tasks.
  • One-time and max_runs: limit how many times a task runs and auto-disable after completion.

Quick Start

Set up your first overnight task by configuring scheduler.yaml and then start the dispatcher to run it overnight.

Frequently Asked Questions about agentwire-scheduler

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

FAQPage Schema
How do I schedule Claude agent sessions to run automatically overnight?

You can schedule overnight agent sessions by configuring a scheduler.yaml file to define tasks and then starting the dispatcher to automatically dispatch queued Claude sessions during off-hours across multiple projects.

Can I gate automated task dispatch based on git repository changes?

Yes, you can gate task dispatch using git_commit and git_diff rules, which automatically skip scheduled tasks when repository commits or diffs have not changed or when external conditions fail.

What scheduling rules are available for automating session orchestration with tmux?

Session orchestration supports flexible schedule definitions including every, at, after, delay, cooldown, not_before, not_after, and except, allowing precise control over when queued tasks are dispatched.

How do I limit a scheduled task to run only once or a specific number of times?

You can limit task executions using one-time scheduling and max_runs settings, which automatically disable the task after it completes the specified number of runs.

Does overnight task scheduling require any external dependencies or tools?

No external dependencies are required. The scheduler uses a dedicated overnight queue stored under ~/.agentwire and manages session orchestration through tmux session management without additional components.