unattended plugins

by Orwa Mahmoud

Accountable, time-bounded Codex shifts. Hand it your punch list, or let it research the product and ship complete improvements until quitting time. Progress stays on disk through compaction and resume. The morning is reviewable commits or artifact receipts, a shift log, and the decisions that were made. When you are done reviewing the run, archive it dated so the live session stays lean.

by Jason Matthew

Plan by day, land by night, triage in the morning. `plan` turns an idea into a plan the loop can land unattended (self-contained `# Task N` sections, empty Open Questions, one Codex pass, opened as a PR). `init` scaffolds the overnight landing loop into the current repo — loop/land.sh, a quiet verifier, two PreToolUse guards the generator cannot loosen, a merge script that waits for CI and re-reads the kill switch — and proves it with a preflight and a dry run. `morning` reads the journal and the land:blocked PRs and says what needs a human. The loop itself is committed in your repo, not in this plugin: it runs `claude -p --setting-sources project`, where installed plugins never load.

by fulin

goal 引擎啟動器與 quota 排程，兩個 skill：goal（推導可測量完成條件→確認或逾時自動採納→以 claude -p 子程序跑官方 /goal 引擎做到完成，長任務壓縮不忘目標、隨時可終止，有 wtf plugin 就用其格式回報）；delaylocal（把 prompt 排到 5h quota 重置後在本機無人值守執行，goal/plain/fast-path 三模式，完成發 LINE 通知）。plugin 名取 goal2 以避開內建 /goal。

by Andrew Vasilyev

Plans an unattended run from the [unattended] table a repository declares: prints the command that would start it with its posture and budget, and writes the snapshot of deny rules that holds its authority. It starts nothing and keeps nothing in context on every turn.

by Mingyang Bao

Unattended server & long-running task supervision — health checks, anomaly detection, auto-repair, multi-channel alerting. One YAML config per project, zero code changes to adopt.

by Phillip Gutowski

Run a manifest of independent tasks through the compound-engineering pipeline, one fresh headless Claude Code process per task, serially and unattended.

by Job Schepers

The unattended lane, stacked on delivery: the nineteen schedule-* skills that run with nobody watching, plus init and update, plus the catalog of triggers that fires them. Seventeen schedulable entry points that pick their own input and run a flow, a review, a check, a sweep, or a report — devbook validate, devbook verify, devbook update, instruction review, issue sweep, merge review, morning brief, package update, performance review, review, security review, tech update, week starter, weekly cost analysis, weekly retro, weekly update, and what's new — and fourteen trigger definitions naming a target, a cadence, the plugins that target needs, and the prompt for a local routine that runs unattended on this machine, never a cloud session. delivery-schedule:init creates them through whatever scheduler the live session exposes and stamps the selection under components.schedule, and delivery-schedule:update keeps them level with it; schedule-status reads their runs and logs; schedule-run fires one now. One capability, two host names: Routines in Claude Code, Automations in the GitHub Copilot app. Depends on delivery and names devbook: a trigger whose target is not enabled is reported and skipped, never scheduled.

by Job Schepers

The unattended lane, stacked on delivery: the eleven schedule-* skills that run with nobody watching, plus install, plus the catalog of triggers that fires them. Nine schedulable entry points that pick their own input and run a flow or a review — bug fix, merge review, package update, performance review, review, security review, week starter, weekly cost analysis, and what's new — and six trigger definitions naming a target, a cadence, the plugins that target needs, and the prompt for a cloud session that starts with nothing but the repository. delivery-schedule:install creates or updates them through whatever scheduler the live session exposes and records the selection under components.schedule; schedule-status reads their runs and logs; schedule-run fires one now. One capability, two host names: Routines in Claude Code, Automations in the GitHub Copilot app. Depends on delivery and names devbook: a trigger whose target is not enabled is reported and skipped, never scheduled.

by Job Schepers

The fan-out lane: a backlog turned into parallel work across sessions and worktrees — the one thing a flow may never do. fleet-issue-sweep triages a repository's open issues for relevance and for collision with work in flight, proposes the stale ones for closure, and dispatches up to five independent worker sessions, one issue and one worktree each, then waits them out and writes the brief. fleet-resolve-issue is what each worker runs: one issue to a pull request when the change proves itself, or to a parked worktree with a handoff brief when a human has to look. fleet-morning-brief re-reads a past sweep from its manifest and worker result files. An L1 extension over delivery: it owns no flow and holds no gate, and trades Personal Validation for a pull request nobody merges unread.

by Phillip Gutowski

Run a manifest of independent tasks through a native plan, build, review, verify, record pipeline, one fresh headless Claude Code process per task, serially and unattended.