feat(agentic-harness): always offer tool research and maintenance (v0…#9
Conversation
….2.0) harness-setup now treats tool research and tool maintenance as a standard part of the plan it presents — asked every run, not skipped until requested. Step 0 also explicitly accepts an optional user-provided starting context. The opt-in framing was the bug: the skill never *asked*, so a build could silently skip tool research. Fixed at the source — Step 1b is reframed from 'never automatic / on request' to 'always offered, run on acceptance'. The safeguard is unchanged: running happens only on an explicit yes, and each tool is still adopted only by a separate per-tool yes. Also: maintenance.md §7 makes tool-maintenance review an always-offered step on existing-harness flows; harness-review flags a missing tools registry as a finding; deliverable checklist asserts the user was asked. Minor bump to 0.2.0 (plugin.json, marketplace.json, repo README) with a changelog entry.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6dfe2228e2
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| 4. Present the plan and confirm it before generating. Tool research and tool maintenance are | ||
| part of a good harness, so make them part of the plan you present **every run** — don't | ||
| wait to be asked: | ||
| - **Always ask whether to run tool discovery** (Step 1b), on a new build or an extension. |
There was a problem hiding this comment.
This bullet still narrows the mandatory tool-discovery prompt to only “a new build or an extension,” even though Step 0 now says tool research should be presented every run and the branch list includes existing-harness apply-review-context and sync flows. In those review/sync scenarios the skill can still silently skip the discovery prompt, which is the behavior this change is meant to eliminate; include all Step 0 paths here or remove the narrowing.
Useful? React with 👍 / 👎.
1 participant
….2.0)
harness-setup now treats tool research and tool maintenance as a standard part of the plan it presents — asked every run, not skipped until requested. Step 0 also explicitly accepts an optional user-provided starting context.
The opt-in framing was the bug: the skill never asked, so a build could silently skip tool research. Fixed at the source — Step 1b is reframed from 'never automatic / on request' to 'always offered, run on acceptance'. The safeguard is unchanged: running happens only on an explicit yes, and each tool is still adopted only by a separate per-tool yes.
Also: maintenance.md §7 makes tool-maintenance review an always-offered step on existing-harness flows; harness-review flags a missing tools registry as a finding; deliverable checklist asserts the user was asked. Minor bump to 0.2.0 (plugin.json, marketplace.json, repo README) with a changelog entry.