Skip to content

Agent does not ask for /ospx-continue #663

Closed

Description

@lucidfrontier45

Hello guys. I found the behaviour of agent changed. Below are the symptom and my wordaround.

Symptom

  • Expected Behaviour: Agent will wait and ask for /ospx-continue confirmation at each stage (Proposal -> Spec -> Design -> Task)
  • Actual Behaviour: Agent continues to write all of artifacts from proposal.md to tasks.md even if /ospx-ff is not invoked.

The actual behaviour slightly changes for each trial. Sometimes

Pattern 1

  1. I first give /ospx-new <change-name>
  2. agent responds with: Run /opsx-continue or just describe what this change is about and I'll draft it.
  3. I enter additional information for proposal
  4. agent starts to write proposal.md but also continues to write spec.md, design.md and task.md

Pattern2

  1. I first give /ospx-new <change-name>
  2. agent responds with: Run /opsx-continue or just describe what this change is about and I'll draft it.
  3. I enter additional information for proposal
  4. agent writes proposal.md and stops for waiting /ospx-continue
  5. I enter /ospx-continue
  6. agent writes the rest of artifacts without stopping.

Workaround

I first removed skills as they are redundant with commands.
Then I modified ospx-continue.md's Guardrails part to include a new line: Important: Never create multiple kinds of artifacts at once
By those two actions above symptom is mostly gone.

Environment

I'm not sure if it's the problem of OpenSpec, OpenCode or the models but last week I didn't encounter this symptom.

  • OpenSpec: 1.1.1
  • OpenCode: 1.1.51
  • Models I tried
    • Z.ai coding plan GLM 4.7
    • OpenCode Zen MiniMax M2.1 free
    • GitHub Copilot GPT-5 mini
  • OS: Windows 11

Activity

  1. kobe2000 commented on Mar 9, 2026

    @kobe2000

    I meet the same problem, opsx-continue will produce all artifacts.

  2. clay-good commented on Aug 5, 2026

    @clay-good
    Collaborator

    The step-wise workflow now instructs the agent to stop after every artifact. /opsx:new shows the first artifact's template and stops ("Do NOT create any artifacts yet"), and /opsx:continue is bounded to "Create ONE artifact per invocation … STOP after creating ONE artifact" — the same rule you added by hand as a workaround, now shipped in the default templates (src/core/templates/workflows/new-change.ts, continue-change.ts). If you want everything generated in one pass, that's the separate /opsx:ff (fast-forward) workflow. Please reopen if a current version still runs past one artifact.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions