juno-code 1.0.51 → 1.0.53

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/README.md CHANGED
@@ -30,6 +30,23 @@ juno-code init --task "Your task description" --subagent claude
30
30
  juno-code init --task "Your task description" --subagent pi
31
31
  ```
32
32
 
33
+ ### Shell Completion (Tab Autocomplete)
34
+
35
+ ```bash
36
+ # Install completion for your current shell
37
+ juno-code completion install
38
+
39
+ # Or explicitly target a shell
40
+ juno-code completion install bash
41
+ juno-code completion install zsh
42
+ juno-code completion install fish
43
+
44
+ # Check status
45
+ juno-code completion status
46
+ ```
47
+
48
+ After installation/reload, `juno-code c<TAB><TAB>` suggests available subcommands.
49
+
33
50
  ---
34
51
 
35
52
  ## The Ralph Method: Where It All Started
@@ -200,6 +217,22 @@ literal text with `backticks`
200
217
  EOF
201
218
  ```
202
219
 
220
+ ### Prompt-time command substitution (per iteration)
221
+
222
+ `juno-code` also supports explicit prompt-time shell substitutions that run inside the working directory on **every engine iteration**:
223
+
224
+ - `!'command'`
225
+ - `!\`\`\`command\`\`\``
226
+
227
+ Examples:
228
+
229
+ ```bash
230
+ juno-code claude -i 3 -p "Summarize git status: !'git status --short'"
231
+ juno-code claude -i 2 -p "Recent commits:\n!```git log -n 5 --oneline```"
232
+ ```
233
+
234
+ This avoids relying on your shell’s one-time backtick expansion and keeps command output fresh across retries/iterations.
235
+
203
236
  ## CLI Reference
204
237
 
205
238
  ### Core Commands
@@ -516,6 +549,30 @@ Orchestrate N concurrent juno-code processes with queue management, structured o
516
549
  ./.juno_task/scripts/parallel_runner.sh --stop-all
517
550
  ```
518
551
 
552
+ #### Dedicated Example: SEO landing-page batch in tmux panes
553
+
554
+ Use this pattern when you want to generate many related content tasks in parallel while keeping live visibility per worker pane:
555
+
556
+ ```bash
557
+ ./.juno_task/scripts/parallel_runner.sh \
558
+ -s pi \
559
+ -m zai/glm-5 \
560
+ --kanban-filter "--tag SEO_LANDING_PAGES --limit 200 --status backlog,in_progress,todo" \
561
+ --parallel 5 \
562
+ --tmux panes \
563
+ --prompt-file ./tmp_prompt/content_gen.md
564
+ ```
565
+
566
+ What each flag does:
567
+
568
+ - `-s pi -m zai/glm-5`: run workers with Pi on a specific model.
569
+ - `--kanban-filter "..."`: dynamically pull task IDs from kanban (here: only `SEO_LANDING_PAGES`, up to 200, only open statuses).
570
+ - `--parallel 5`: execute up to 5 tasks concurrently.
571
+ - `--tmux panes`: split workers into panes for side-by-side monitoring.
572
+ - `--prompt-file ./tmp_prompt/content_gen.md`: keep a reusable, versioned instruction template instead of long inline prompts.
573
+
574
+ Tip: keep the filter string quoted so it is passed as one argument to `parallel_runner.sh` and then correctly forwarded to `kanban.sh`.
575
+
519
576
  #### Output & Extraction
520
577
 
521
578
  - **Per-task JSON**: `{output_dir}/{task_id}.json` with exit code, wall time, extracted response