@wular/coder 0.2.6 → 0.2.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/cli.js +129 -126
- package/package.json +1 -1
- package/plugins/agents/skills/coder/SKILL.md +1 -1
- package/plugins/claude/.claude-plugin/plugin.json +1 -1
- package/plugins/claude/skills/handle/SKILL.md +1 -1
- package/plugins/cursor/.cursor-plugin/plugin.json +1 -1
- package/plugins/cursor/skills/coder/SKILL.md +1 -1
package/package.json
CHANGED
|
@@ -29,7 +29,7 @@ If `coder` is not on PATH, install it yourself without asking (`npm install -g @
|
|
|
29
29
|
- Compose one self-contained task text (goal, relevant paths, constraints) and dispatch it. It backgrounds by default: the runtime does a startup check and prints a task id (or errors / hands off, see exit codes):
|
|
30
30
|
|
|
31
31
|
```bash
|
|
32
|
-
coder task run "<task text>"
|
|
32
|
+
coder task run --system "<standing instructions>" "<task text>"
|
|
33
33
|
```
|
|
34
34
|
|
|
35
35
|
Fetch the answer with `coder task result <task-id> --wait` - it blocks until the task finishes, then prints only the final result (keeps your context clean). Only use `--wait` when your harness can run it in a **background shell** (so it does not block you); without one, poll `coder task result <task-id>` (no `--wait`) until it is done. Or skip the two steps and block on the run itself with `--wait` on `coder task run`.
|
|
@@ -28,7 +28,7 @@ If `coder` is not on PATH, install it yourself without asking (`npm install -g @
|
|
|
28
28
|
- Compose one self-contained task text (goal, relevant paths, constraints) and dispatch it. It backgrounds by default: the runtime does a startup check and prints a task id (or errors / hands off, see exit codes):
|
|
29
29
|
|
|
30
30
|
```bash
|
|
31
|
-
coder task run "<task text>"
|
|
31
|
+
coder task run --system "<standing instructions>" "<task text>"
|
|
32
32
|
```
|
|
33
33
|
|
|
34
34
|
Fetch the answer with `coder task result <task-id> --wait` - it blocks until the task finishes, then prints only the final result (keeps your context clean). Run it as a **background Bash call** so it does not block you and you are re-invoked on completion:
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "coder",
|
|
3
3
|
"displayName": "Coder",
|
|
4
|
-
"version": "0.2.
|
|
4
|
+
"version": "0.2.8",
|
|
5
5
|
"description": "Delegate coding tasks to supervised Coder subagents running on Codex, Claude, or any OpenAI-compatible model. Your main context stays clean.",
|
|
6
6
|
"author": {
|
|
7
7
|
"name": "muzam1l"
|
|
@@ -29,7 +29,7 @@ If `coder` is not on PATH, install it yourself without asking (`npm install -g @
|
|
|
29
29
|
- Compose one self-contained task text (goal, relevant paths, constraints) and dispatch it. It backgrounds by default: the runtime does a startup check and prints a task id (or errors / hands off, see exit codes):
|
|
30
30
|
|
|
31
31
|
```bash
|
|
32
|
-
coder task run "<task text>"
|
|
32
|
+
coder task run --system "<standing instructions>" "<task text>"
|
|
33
33
|
```
|
|
34
34
|
|
|
35
35
|
Fetch the answer with `coder task result <task-id> --wait` - it blocks until the task finishes, then prints only the final result (keeps your context clean). Only use `--wait` when you can run it in a **background terminal** (so it does not block you); if you can't, poll `coder task result <task-id>` (no `--wait`) until it is done. Or skip the two steps and block on the run itself with `--wait` on `coder task run`.
|