@voyager-crew/cli 0.4.0 → 0.5.0
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 +13 -2
- package/README_ZH.md +8 -2
- package/dist/cli.mjs +551 -183
- package/package.json +2 -2
- package/skills/voyager/SKILL.md +2 -2
package/README.md
CHANGED
|
@@ -127,8 +127,19 @@ npx skills add voyager-crew/voyager-cli
|
|
|
127
127
|
exit code means, how to wait for a long job without sending the prompt twice, and how to follow
|
|
128
128
|
up with `--chat` and the conversation id it got rather than `--continue`.
|
|
129
129
|
|
|
130
|
-
One job runs at a time
|
|
131
|
-
|
|
130
|
+
One job runs at a time, unless you turn on **Run jobs in parallel** in the **Local bridge** card of
|
|
131
|
+
the Voyager popup (a Voyager release later than 2.2.1) and choose there how many run at once, from
|
|
132
|
+
2 to 10. Then that many jobs run side by side, each in its own ChatGPT tab, so several agents can
|
|
133
|
+
ask at once and their replies are awaited together; typing and clicking still take turns. A job
|
|
134
|
+
waits for its turn as long as the other job's step may take (a large upload, up to 10 minutes),
|
|
135
|
+
and stops as busy (exit 5) before its own step only when that job is stuck past it. Two asks
|
|
136
|
+
into the same conversation, or two project changes, never run together: the later one is refused
|
|
137
|
+
as busy (exit 5). `"maxParallelJobs": 2` in `~/.voyager/config.json` keeps it to fewer jobs; each
|
|
138
|
+
running job is a Pro request of its own. `voyager status` says how many jobs may run now and which
|
|
139
|
+
one is acting on its page.
|
|
140
|
+
|
|
141
|
+
Every result also names your ChatGPT plan (`Pro Lite ($100)`, `Pro ($200)`, …) as the page last
|
|
142
|
+
reported it.
|
|
132
143
|
|
|
133
144
|
## Good to know
|
|
134
145
|
|
package/README_ZH.md
CHANGED
|
@@ -111,8 +111,14 @@ npx skills add voyager-crew/voyager-cli
|
|
|
111
111
|
[`skills/voyager/SKILL.md`](skills/voyager/SKILL.md) 就是写给它们看的:JSON 输出、每个退出码的含义、怎么等长任务而不把问题发两遍,以及接着问时用
|
|
112
112
|
`--chat` 加上次拿到的对话 id,而不是 `--continue`。
|
|
113
113
|
|
|
114
|
-
|
|
115
|
-
|
|
114
|
+
默认同一时间只跑一个任务。在 Voyager 弹窗的 **本地桥接** 卡片里打开 **并行运行任务**(2.2.1 之后发布的
|
|
115
|
+
Voyager 版本),并在那里选好同时跑几个(2 到 10 个)后,这么多任务同时进行,各用自己的 ChatGPT 标签页:几个
|
|
116
|
+
agent 可以同时提问,回复一起等;输入和点击仍会轮流进行。轮到自己之前,任务会一直等到另一个任务的那一步
|
|
117
|
+
允许用完的时间(大文件上传最长 10 分钟);只有那个任务超时卡住,才在自己这一步之前按 busy 停下(退出码 5)。往同一个对话里的两次提问、两次项目改动不会同时进行,后来的那个按 busy 拒绝(退出码 5)。
|
|
118
|
+
想少跑几个,在 `~/.voyager/config.json` 里写 `"maxParallelJobs": 2`;每个在跑的任务都是一次单独的 Pro 请求。
|
|
119
|
+
`voyager status` 会显示现在最多能同时跑几个,以及哪个任务正在操作页面。
|
|
120
|
+
|
|
121
|
+
每次的结果里还会带上你的 ChatGPT 套餐(`Pro Lite ($100)`、`Pro ($200)` 等),以页面最近一次报告的为准。
|
|
116
122
|
|
|
117
123
|
## 须知
|
|
118
124
|
|