@sma1lboy/rove 0.9.74 → 0.9.75

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.
@@ -219,7 +219,7 @@ turn either. These five carry almost all traffic:
219
219
 
220
220
  ```text
221
221
  add --repo(REQ) --prompt --title --command --count --agents --activate
222
- send --prompt(REQ) --task-id --tab --command --plain
222
+ send --prompt|--prompt-file(REQ) --task-id --tab --command --plain
223
223
  get-task --task-id(REQ) list (no flags)
224
224
  collect --group <groupId> | --task-ids <csv> | --repo
225
225
  ```
@@ -263,10 +263,14 @@ rove api add --repo "$PWD" --agents claude:2,codex:1 --prompt "<prompt>"
263
263
  # From inside a Rove task this auto-prefixes [ROVE PEER] provenance
264
264
  # (sender + reply command); --plain sends verbatim.
265
265
  #
266
- # SINGLE-QUOTE a prompt containing backticks, or your shell runs them as
267
- # command substitution and the words vanish from the message you send. In
268
- # double quotes `rove api send` becomes the OUTPUT of running that command.
269
- rove api send --task-id <id> --prompt "<complete next turn>"
266
+ # A prompt with backticks, $vars, or quotes goes through --prompt-file, NEVER
267
+ # a double-quoted --prompt: in double quotes `rove api send …` is command
268
+ # substitution the shell RUNS it and ships its output, and the words vanish.
269
+ # Single quotes block $ROVE_TASK_ID too, so there is no quoting that fits both.
270
+ rove api send --task-id <id> --prompt "<complete next turn>" # plain text only
271
+ rove api send --task-id <id> --prompt-file - <<'EOF' # anything else
272
+ <turn — backticks, $vars, quotes, multi-line, all verbatim>
273
+ EOF
270
274
 
271
275
  # Reply home: no --task-id inside a dispatched task = the dispatcher's tab.
272
276
  rove api send --prompt "succeeded: <one line> (branch <final branch>)"
@@ -17,9 +17,9 @@ Every `--repo` resolves relative paths against `$PWD` and wants the git toplevel
17
17
  These five carry almost all traffic. Nothing here should ever need `schema`.
18
18
 
19
19
  ```text
20
- add --repo(REQ) --prompt --title --command --count --agents
20
+ add --repo(REQ) --prompt|--prompt-file --title --command --count --agents
21
21
  --branch --base-branch --status --pin --activate
22
- send --prompt(REQ) --task-id --tab --command --plain
22
+ send --prompt|--prompt-file(REQ) --task-id --tab --command --plain
23
23
  get-task --task-id(REQ)
24
24
  list (no flags)
25
25
  collect --task-ids <csv> | --repo
@@ -79,8 +79,8 @@ needs numbers, not when you want to know what a task is doing.
79
79
  ## drive
80
80
 
81
81
  ```text
82
- send --prompt(REQ) --task-id --tab --command --plain
83
- dispatch --task-id(REQ) --prompt(REQ) --tab
82
+ send --prompt|--prompt-file(REQ) --task-id --tab --command --plain
83
+ dispatch --task-id(REQ) --prompt|--prompt-file(REQ) --tab
84
84
  note --task-id(REQ) --text(REQ)
85
85
  note-list --repo(REQ)
86
86
  pane-open --command --task-id --tab --direction[right|down] --placement[split|tab] --title
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "$schema": "https://json.schemastore.org/package.json",
3
3
  "name": "@sma1lboy/rove",
4
- "version": "0.9.74",
4
+ "version": "0.9.75",
5
5
  "description": "Rove — the agent multiplexer for your terminal. Run coding agents on parallel tasks with isolated worktrees and persistent sessions.",
6
6
  "keywords": [
7
7
  "terminal",