Repository navigation
feat: choose agent harnesses during init and with configure-harnesses - #403
Merged
danielhanold merged 12 commits intoOct 7, 2026
Merged
Conversation
…ent harnesses later Pending paths come from git status filtered to the docket-managed paths, so a tracked surface removed this run (CLAUDE.md under --harnesses none) is listed. The Cursor dispatch rule is ignored by the managed .gitignore block, so its removal is not a reviewable change and is not listed.
…anned targets Review finding: init told the user to commit the gitignored Cursor rule and unchanged surface files because it echoed every planned surface target, so 'git add' on the pending list failed. Init now reads the surfaces pending review from git status, as configure-harnesses does.
…th check; edit multi-line flow harness lists Review findings fixed: - Pending review paths: init and configure-harnesses now derive them through the same function repository check uses, so the .gitignore is pending only when its managed block is not yet committed. An unrelated uncommitted .gitignore edit no longer lists .gitignore or raises a healthy repository to needs-review. - configure-harnesses refuses a needs-review repository whose primary checkout is proven off the integration branch, as it already did for an otherwise-healthy one; an unknown branch probe still admits. - The agent_harnesses edit replaces a flow list through its closing ] line, so a multi-line flow list is rewritten instead of refused.
- refuse a repeated none in --harnesses as listed more than once - omit the review-and-commit clause when no paths are pending - cover configure-harnesses claude clearing harnesses-unset in a private repo - repeat the configure-harnesses follow-up after the final upgrade step - move configure-harnesses after configure-tests --command in the glossary
danielhanold
deleted the
feat/choose-agent-harnesses-during-repository-init
branch
October 7, 2026 10:30
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docket repository initnow asks which coding agents get docket's dispatch instructions, and the newdocket repository configure-harnesseschanges that choice later. Both writeagent_harnessesto the repository config and refresh the instructions in one run.--harnesses claude,cursor/--harnesses noneon both commands; bad, repeated, or mixed tokens refused before any write.configure-harnessesworks on a dirty/behind/needs-review checkout (primary must still be on the integration branch).repository checkwarnsharnesses-unsetwhile no repository-level layer declares the key; fixtures and the Bash-upgrade guide now declare it.Review (deep tier) — dispositions
--harnesses none,noneacceptedagent_harnesses: []