Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Claude Code mods (plugins with a hooks module), served as a local folder marketp
| --- | --- | --- |
| [goal-mode](goal-mode/) | 0.7.0 | Session goals, handed to Claude Code's own `/goal`: set by you (`/goal-mode set <condition> [--check <cmd>]`) or by Claude itself (nudged on outcome requests and approved plans); its own evaluator judges only the loop's queued goals |
| [harness](harness/) | 0.3.2 | The integrated harness: the user's Claude rules enforced at the tool call, session tooling and workflow automation (formerly house-rules) |
| [auto-claude](auto-claude/) | 0.3.0 | Unattended run of a repository on top of goal-mode's loop: plans the long-term goal and milestones, ships each (push, PR, CI, merge when green, then deploy where `.claude/auto-deploy.json` opts in), replans until the final check passes |
| [auto-claude](auto-claude/) | 0.4.1 | Unattended run of a repository on top of goal-mode's loop: plans the long-term goal and milestones, ships each (push, PR, CI, merge when green, then deploy where `.claude/auto-deploy.json` opts in), replans until the final check passes |
| [model-tier](model-tier/) | 0.11.0 | Routes each main-loop turn to fable, opus, sonnet or haiku and a reasoning effort by task complexity, with a `set_tier` tool the model calls to correct either |
| [refactor](refactor/) | 0.1.3 | Enforces the architecture a repo declares in `.claude/architecture.json` at Edit/Write (layer direction, forbidden imports), notes code smells with the refactoring.guru technique to apply, `/arch audit` for violations and import cycles |

Expand Down
2 changes: 1 addition & 1 deletion auto-claude/.claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "auto-claude",
"version": "0.3.0",
"version": "0.4.1",
"description": "Finishes a repository's work unattended: Claude plans the long-term end state and its milestones, goal-mode's loop builds each one in a worktree, and auto-claude ships it (push, PR, CI, merge when green), then replans until the final check passes.",
"author": {
"name": "unohee"
Expand Down
8 changes: 8 additions & 0 deletions auto-claude/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,12 @@ An unattended run of one repository. Give it an aim in one line, or none at all.

It depends on [goal-mode](../goal-mode/), which supplies the loop: one worktree per milestone, checks, the evaluator, stuck handling and guards.

## Starting anywhere

- **Not a git repository.** `/auto-claude start` in a plain directory runs `git init -b main`, adds secrets and noise to `.gitignore` (`.env*`, `*.pem`, `*.key`, `node_modules/`, `worktrees/`, `.claude/settings.local.json`), and makes one initial commit of what is there. Plan the empty case too: with no files, the first milestone is the scaffold.
- **Refused.** The home directory, `/`, a directory with more than 3000 files, and a directory that holds other repositories are not one project, so nothing is initialized there.
- **No `origin` remote** (a new repository, or an existing one). Milestones land in the repository's own default branch: the check, a rebase onto it, then `git push . HEAD:<branch>` with `receive.denyCurrentBranch=updateInstead`, which updates the checked-out files in place. There is no PR and no CI, and `.claude/goal-loop.base` is the branch itself. An existing repository must have a clean tracked tree to start.

## A run

1. **Plan.**
Expand Down Expand Up @@ -54,6 +60,8 @@ A repository opts in by committing `.claude/auto-deploy.json`:
- A `/goal-mode loop on` that starts nothing is retried with backoff. After 3 tries the person is told the loop's reply.
- A run still planning gets a reminder every 15 minutes that lists what the plan files lack. After 3 reminders the run stops.
- A shipping error that repeats is reported once.
- A tick that fails 3 times in a row (an unwritable `.claude/goal-loop.gate`, say) is reported once with its error, and `stalled: every tick fails` stays in `/auto-claude status` until a tick gets through.
- **Idle nudge.** A run on the `run` phase where nothing was started, shipped or merged for 15 minutes is reported to the person with its cause (the `stalled:` reason, or "idle N min"), again 30 minutes later, and once more, 3 nudges in all (`idleNudges` in the record; any progress resets the count). When the loop is the idle one, the nudge also clears the `loop on` backoff so the grant is asked at once. A goal being built is waiting, not idle. So is a PR whose CI is pending, or whose mergeability GitHub has not decided, for up to 90 minutes: after that the wait is a stall (a check queued for an offline self-hosted runner never finishes), named `PR #N has waited M min for CI` in the nudge and in `stalled:`. The session model is not prompted.
- `/auto-claude status` ends with a `stalled:` line when the run is not moving. It names the cause and gives the evidence: an orphaned owner (when it last ticked), a granted start the loop does not take (its last `loop on` reply), overdue planning (what the plan files lack), or a shipping error that repeats (its note and count).
- A run whose owning session has gone quiet for 10 minutes is reported as orphaned in other sessions, and `/auto-claude resume` picks it up there.
- Only the owning session receives the unattended rules.
Expand Down
Loading
Loading