From efaf1912458b3d2067cb0de8b437355b4b26b257 Mon Sep 17 00:00:00 2001 From: davidtaoweiji Date: Thu, 9 Apr 2026 14:24:32 +0800 Subject: [PATCH] added streaming support --- .opencode/command/opsx-apply.md | 149 +++++++++ .opencode/command/opsx-archive.md | 154 +++++++++ .opencode/command/opsx-explore.md | 170 ++++++++++ .opencode/command/opsx-propose.md | 103 ++++++ .../skills/openspec-apply-change/SKILL.md | 156 +++++++++ .../skills/openspec-archive-change/SKILL.md | 114 +++++++ .opencode/skills/openspec-explore/SKILL.md | 288 ++++++++++++++++ .opencode/skills/openspec-propose/SKILL.md | 110 ++++++ mini_agent/agent.py | 239 ++++++++++--- mini_agent/cli.py | 168 +++++++--- mini_agent/config.py | 6 +- mini_agent/config/config-example.yaml | 60 ---- mini_agent/llm/anthropic_client.py | 181 +++++++++- mini_agent/llm/base.py | 25 +- mini_agent/llm/llm_wrapper.py | 22 +- mini_agent/llm/openai_client.py | 144 +++++++- .../add-streaming-support/.openspec.yaml | 2 + .../changes/add-streaming-support/design.md | 91 +++++ .../changes/add-streaming-support/proposal.md | 28 ++ .../specs/streaming-responses/spec.md | 56 ++++ .../changes/add-streaming-support/tasks.md | 60 ++++ .../changes/examine-workflow/.openspec.yaml | 2 + openspec/changes/examine-workflow/README.md | 3 + tests/test_streaming.py | 315 ++++++++++++++++++ 24 files changed, 2486 insertions(+), 160 deletions(-) create mode 100644 .opencode/command/opsx-apply.md create mode 100644 .opencode/command/opsx-archive.md create mode 100644 .opencode/command/opsx-explore.md create mode 100644 .opencode/command/opsx-propose.md create mode 100644 .opencode/skills/openspec-apply-change/SKILL.md create mode 100644 .opencode/skills/openspec-archive-change/SKILL.md create mode 100644 .opencode/skills/openspec-explore/SKILL.md create mode 100644 .opencode/skills/openspec-propose/SKILL.md delete mode 100644 mini_agent/config/config-example.yaml create mode 100644 openspec/changes/add-streaming-support/.openspec.yaml create mode 100644 openspec/changes/add-streaming-support/design.md create mode 100644 openspec/changes/add-streaming-support/proposal.md create mode 100644 openspec/changes/add-streaming-support/specs/streaming-responses/spec.md create mode 100644 openspec/changes/add-streaming-support/tasks.md create mode 100644 openspec/changes/examine-workflow/.openspec.yaml create mode 100644 openspec/changes/examine-workflow/README.md create mode 100644 tests/test_streaming.py diff --git a/.opencode/command/opsx-apply.md b/.opencode/command/opsx-apply.md new file mode 100644 index 00000000..94b8c1ee --- /dev/null +++ b/.opencode/command/opsx-apply.md @@ -0,0 +1,149 @@ +--- +description: Implement tasks from an OpenSpec change (Experimental) +--- + +Implement tasks from an OpenSpec change. + +**Input**: Optionally specify a change name (e.g., `/opsx-apply add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes. + +**Steps** + +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: " and how to override (e.g., `/opsx-apply `). + +2. **Check status to understand the schema** + ```bash + openspec status --change "" --json + ``` + Parse the JSON to understand: + - `schemaName`: The workflow being used (e.g., "spec-driven") + - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others) + +3. **Get apply instructions** + + ```bash + openspec instructions apply --change "" --json + ``` + + This returns: + - Context file paths (varies by schema) + - Progress (total, complete, remaining) + - Task list with status + - Dynamic instruction based on current state + + **Handle states:** + - If `state: "blocked"` (missing artifacts): show message, suggest using `/opsx-continue` + - If `state: "all_done"`: congratulate, suggest archive + - Otherwise: proceed to implementation + +4. **Read context files** + + Read the files listed in `contextFiles` from the apply instructions output. + The files depend on the schema being used: + - **spec-driven**: proposal, specs, design, tasks + - Other schemas: follow the contextFiles from CLI output + +5. **Show current progress** + + Display: + - Schema being used + - Progress: "N/M tasks complete" + - Remaining tasks overview + - Dynamic instruction from CLI + +6. **Implement tasks (loop until done or blocked)** + + For each pending task: + - Show which task is being worked on + - Make the code changes required + - Keep changes minimal and focused + - Mark task complete in the tasks file: `- [ ]` → `- [x]` + - Continue to next task + + **Pause if:** + - Task is unclear → ask for clarification + - Implementation reveals a design issue → suggest updating artifacts + - Error or blocker encountered → report and wait for guidance + - User interrupts + +7. **On completion or pause, show status** + + Display: + - Tasks completed this session + - Overall progress: "N/M tasks complete" + - If all done: suggest archive + - If paused: explain why and wait for guidance + +**Output During Implementation** + +``` +## Implementing: (schema: ) + +Working on task 3/7: +[...implementation happening...] +✓ Task complete + +Working on task 4/7: +[...implementation happening...] +✓ Task complete +``` + +**Output On Completion** + +``` +## Implementation Complete + +**Change:** +**Schema:** +**Progress:** 7/7 tasks complete ✓ + +### Completed This Session +- [x] Task 1 +- [x] Task 2 +... + +All tasks complete! You can archive this change with `/opsx-archive`. +``` + +**Output On Pause (Issue Encountered)** + +``` +## Implementation Paused + +**Change:** +**Schema:** +**Progress:** 4/7 tasks complete + +### Issue Encountered + + +**Options:** +1.