Agent always ask what change I mean even if there is only one #679

Activity

1. 21st-connector commented on Feb 7, 2026

   

   21st-connectorbot

   on Feb 7, 2026 – with 21st - Connector

   Last edited by 21st-connector

   Contributor

   More actions

   Task completed.

   The enrichment comment has been posted on issue #679. Here's a summary of the findings:

   Root cause: The /opsx:continue skill template in src/core/templates/skill-templates.ts:416 has an explicit instruction: "Do NOT guess or auto-select a change. Always let the user choose." This forces the AI agent to always prompt the user, even when there's only one active change.

   Key inconsistency: The /opsx:apply skill template (line 529 of the same file) already implements auto-selection when only one change exists. The fix is straightforward — update the continue template's change selection logic (lines 404-416) to match the apply template's pattern.

   Related issues: #663 and #673 deal with other /opsx:continue behavioral quirks but are not duplicates.

   ---

   View full conversation

   Powered by 1Code
2. 21st-connector commented on Feb 7, 2026

   

   21st-connectorbot

   on Feb 7, 2026 – with 21st - Connector

   Contributor

   More actions

   Issue Analysis

   Root Cause

   The /opsx:continue skill template explicitly forbids auto-selection, even when only one change exists. In src/core/templates/skill-templates.ts:416:

   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
   

   This instruction (lines 404-416) tells the AI agent to always run openspec list --json, present options via AskUserQuestion, and wait for user input — regardless of how many changes are active.

   Inconsistency with /opsx:apply

   Notably, the /opsx:apply skill template already implements the exact behavior requested here. In src/core/templates/skill-templates.ts:525-532:

   If a name is provided, use it. Otherwise:
   - Infer from conversation context if the user mentioned a change
   - Auto-select if only one active change exists
   - If ambiguous, run `openspec list --json` to get available changes and use the AskUserQuestion tool to let the user select
   

   So /opsx:apply auto-selects when there's one change, but /opsx:continue always prompts. This inconsistency is likely unintentional.

   Suggested Fix

   Update the change selection logic in getContinueChangeSkillTemplate() (line 404-416 of src/core/templates/skill-templates.ts) to match the pattern used by getApplyChangeSkillTemplate():

   1. **Select the change**
   
      If a name is provided, use it. Otherwise:
      - Infer from conversation context if the user mentioned a change
      - Auto-select if only one active change exists
      - If ambiguous, run `openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select
   
      Always announce: "Using change: <name>" and how to override (e.g., `/opsx:continue <other>`).
   

   This would replace the current step 1 (lines 404-416) and remove the "Do NOT guess or auto-select" guardrail.

   Files to Modify

   • src/core/templates/skill-templates.ts — getContinueChangeSkillTemplate() function, lines 404-416. Update the change selection instructions to auto-select when only one active change exists.

   Related Issues

   • Agent does not ask for /ospx-continue #663 — Reports different /opsx-continue behavioral issues (agent not stopping between artifacts)
   • Clarify command (update existing artifacts before continue) #673 — Requests a way to update artifacts without triggering continue

   Both are related to the /opsx:continue workflow but address different aspects.
3. clay-good commented on Jul 28, 2026

   

   clay-good

   on Jul 28, 2026

   Collaborator

   More actions

   Fix up in #1468: the continue/update/verify/sync/archive workflows now select a change the way /opsx:apply has since #513 — use the given name, infer from conversation context, auto-select when only one active change exists, and only prompt when it's genuinely ambiguous (always announcing "Using change: " with how to override). The templates' "Do NOT guess or auto-select" instruction was the cause of the stall you described.
4. clay-good

   closed this as completedin #1468on Jul 28, 2026
5. pull

   added a commit that references this issue on Jul 28, 2026

   fix(templates): auto-select the only active change instead of always …

   ...

   This issue will close once commit fc886af is merged into the 'main' branch.

   fc886af