@openscout/scout 0.2.60 → 0.2.62
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 +29 -0
- package/dist/client/assets/{arc.es-DgeMPL-I.js → arc.es-nBIiEfYv.js} +1 -1
- package/dist/client/assets/index-BdwfgbIm.js +140 -0
- package/dist/client/assets/index-tcdw22Rl.css +1 -0
- package/dist/client/index.html +3 -2
- package/dist/main.mjs +2793 -5467
- package/dist/pair-supervisor.mjs +719 -2636
- package/dist/scout-control-plane-web.mjs +16597 -17857
- package/package.json +2 -2
- package/dist/client/assets/index-25TJx0iN.js +0 -140
- package/dist/client/assets/index-B1kglsyi.css +0 -1
package/README.md
CHANGED
|
@@ -91,6 +91,33 @@ scout send "@vox heads up: I’m on the runtime side"
|
|
|
91
91
|
scout ask --to vox "can you confirm the broker fix?"
|
|
92
92
|
```
|
|
93
93
|
|
|
94
|
+
Known on-demand or offline agents are supposed to wake on first delivery. `scout send` and `scout ask` should be the default path; `scout up` is for explicit prewarming or for creating/registering a target the broker does not know yet.
|
|
95
|
+
|
|
96
|
+
### File-backed input
|
|
97
|
+
|
|
98
|
+
Use a file when the primary prompt or message is too large or too structured to
|
|
99
|
+
belong in shell argv.
|
|
100
|
+
|
|
101
|
+
Nomenclature:
|
|
102
|
+
|
|
103
|
+
- **Prompt file**: the primary work prompt for `scout ask`; pass it with `--prompt-file <path>`.
|
|
104
|
+
- **Message file**: the message body for `scout send`, `scout broadcast`, or `scout speak`; pass it with `--message-file <path>`.
|
|
105
|
+
- **Body file**: shared alias for either command family; `--body-file <path>` reads the same UTF-8 text into the broker `body` field.
|
|
106
|
+
|
|
107
|
+
Examples:
|
|
108
|
+
|
|
109
|
+
```bash
|
|
110
|
+
scout ask --to hudson --prompt-file ./handoff.md
|
|
111
|
+
scout @hudson --prompt-file ./review-request.md
|
|
112
|
+
scout send --channel triage --message-file ./status-update.md
|
|
113
|
+
scout broadcast --message-file ./maintenance-window.md
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
The file is read locally before dispatch. The local broker still receives one
|
|
117
|
+
structured request containing the target, body, sender, routing fields, and
|
|
118
|
+
metadata, so the rest of the broker and mesh path can choose the right transport
|
|
119
|
+
without depending on shell argument size.
|
|
120
|
+
|
|
94
121
|
### One-to-one delegation
|
|
95
122
|
|
|
96
123
|
When one project agent is delegating concrete work to one other agent, treat it
|
|
@@ -137,6 +164,8 @@ scout @vox.harness:codex.node:mini run locally on mini
|
|
|
137
164
|
|
|
138
165
|
Aliases: `runtime:` = `harness:`, `persona:` = `profile:`, `branch:` / `worktree:` = workspace qualifier. Dimensions combine in any order.
|
|
139
166
|
|
|
167
|
+
If direct send/ask still comes back unresolved, treat that as a routing problem, not a mere "target is offline" problem. The right follow-up is to disambiguate the target, inspect broker context with `scout who` / `scout latest`, or create/register the missing identity. Do not default to pushing the bring-up step back onto the operator for a known target.
|
|
168
|
+
|
|
140
169
|
## Current Commands
|
|
141
170
|
|
|
142
171
|
```bash
|