You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
I first give /ospx-new <change-name>
agent responds with: Run /opsx-continue or just describe what this change is about and I'll draft it.
I enter additional information for proposal
agent starts to write proposal.md but also continues to write spec.md, design.md and task.md
Pattern2
I first give /ospx-new <change-name>
agent responds with: Run /opsx-continue or just describe what this change is about and I'll draft it.
I enter additional information for proposal
agent writes proposal.md and stops for waiting /ospx-continue
I enter /ospx-continue
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.
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.
Activity
kobe2000 commentedon Mar 9, 2026
I meet the same problem,
opsx-continuewill produce all artifacts.clay-good commentedon Aug 5, 2026
The step-wise workflow now instructs the agent to stop after every artifact.
/opsx:newshows the first artifact's template and stops ("Do NOT create any artifacts yet"), and/opsx:continueis 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.