unattended

Switches the agent to autonomous mode for long-running tasks with guardrails, logging, and notifications.

1|1|Updated Nov 25, 2024
One-click install
npx skills add https://github.com/joeledwardson/dev-setup --skill unattended-joeledwardson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unattended
Source: https://github.com/joeledwardson/dev-setup/tree/main/configs/claude/skills/unattended
Command: npx skills add https://github.com/joeledwardson/dev-setup --skill unattended-joeledwardson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you step away from a coding session, a default assistant stalls on every ambiguity, asking questions nobody is there to answer. This Skill flips the default stance from "ask if unsure" to "act if unsure, log what you chose", so research and long-running tasks keep moving while you are away. ## Core Features & Use Cases - Autonomous operating mode: Picks the less-destructive option when ambiguous, records the decision in a monthly dev log, and keeps working instead of pausing. - Guardrails and time-boxing: Stops for credentials, destructive operations on shared state, paid resources, scope explosions, and repeated failures; enforces budgets like ~2 hours per bug and ~1 day per architectural experiment. - Review and notification loop: Triggers /review-code and /review-docs after changes (max two cycles), commits in small logical units, and sends push notifications via ntfy.sh at semantic milestones. - Use Case: You kick off a multi-hour refactoring before leaving for the day. The agent plans first, works through the task list, writes tests, commits incrementally, logs decisions to docs/dev-log/YYYY-MM.md, and pings your phone only when it finishes or genuinely needs you. ## Quick Start Type /unattended to switch the current session into autonomous mode for your long-running task.

Frequently Asked Questions about unattended

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

FAQPage Schema
How do I run an AI coding agent unattended on long tasks?

Invoke /unattended explicitly to switch the session into autonomous mode. The agent then acts on ambiguity instead of asking, logs every decision to a monthly dev log, commits in small units, and notifies you via ntfy.sh when it finishes or hits a blocker.

When does unattended mode stop and ask for user input?

It stops for credentials or 2FA, destructive operations on shared state like force-pushes, anything costing real money, scope explosions beyond the original task, truly ambiguous intent, and after the same approach fails three or more times.

Does unattended mode auto-activate on long tasks?

No. The Skill is marked disable-model-invocation and only loads on an explicit /unattended command. It never activates automatically, so normal interactive sessions keep the default ask-if-unsure behavior.

How does the agent prevent code bloat during autonomous sessions?

It enforces spec-first development, mandatory spec comments on exported functions, a 3-caller rule before creating helpers, a ~250-line file length trigger, stdlib-first reuse, and an end-of-session git diff deletion pass before committing.

What notifications does unattended mode send to my phone?

It posts to an ntfy.sh topic at semantic milestones: batch start, task completion, blockers, stops requiring user input at high priority, non-obvious autonomous decisions, and finishing all tasks. Titles lead with project and hostname for scannability.