@voyager-crew/cli 0.3.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 +24 -3
- package/README_ZH.md +15 -3
- package/dist/cli.mjs +678 -196
- package/package.json +4 -3
- package/skills/voyager/SKILL.md +28 -13
package/README.md
CHANGED
|
@@ -29,7 +29,8 @@ and ChatGPT sees an ordinary chat from your own browser.
|
|
|
29
29
|
npm install -g @voyager-crew/cli
|
|
30
30
|
```
|
|
31
31
|
|
|
32
|
-
2. Install the Voyager extension, version 2.1.0 or later
|
|
32
|
+
2. Install the Voyager extension, version 2.1.0 or later (2.2.0 for `--approve-apps` and for saving the
|
|
33
|
+
files a reply offers):
|
|
33
34
|
[Chrome](https://chromewebstore.google.com/detail/iifacdnjakkhjjiengaffnegbndgingi) ·
|
|
34
35
|
[Edge](https://microsoftedge.microsoft.com/addons/detail/voyager/gibmkggjijalcjinbdhcpklodjkhhlne) ·
|
|
35
36
|
[Firefox](https://addons.mozilla.org/firefox/addon/gemini-voyager/). In its popup, open
|
|
@@ -73,6 +74,10 @@ voyager ask --no-wait "…" # prints a job id
|
|
|
73
74
|
voyager job wait <id> --timeout 10m # exit 4 means still running: wait again, never resend
|
|
74
75
|
```
|
|
75
76
|
|
|
77
|
+
A Pro turn that builds, runs or renders things in ChatGPT's sandbox can lose its connection
|
|
78
|
+
after about 80 minutes, and then delivers nothing. `--timebox 70` asks it to wrap up at 70
|
|
79
|
+
minutes and hand over what it has, finished and unfinished work apart, in one ZIP.
|
|
80
|
+
|
|
76
81
|
## Projects
|
|
77
82
|
|
|
78
83
|
A ChatGPT project keeps files that every chat in it can read, so a codebase or a paper goes
|
|
@@ -104,6 +109,11 @@ a restriction: the app writes wherever its GitHub installation allows, without a
|
|
|
104
109
|
repository, voyager stops with exit code 3; add the repository at
|
|
105
110
|
[github.com/settings/installations](https://github.com/settings/installations).
|
|
106
111
|
|
|
112
|
+
Before some app actions, such as writing a file to Drive, ChatGPT stops the reply on a card that asks
|
|
113
|
+
"Allow ChatGPT to use Google Drive?". voyager then stops with exit code 3 and the conversation link, where
|
|
114
|
+
you answer it. With Voyager 2.2.0 or later, pass `--approve-apps always` to have the extension click "Always allow" for you, or
|
|
115
|
+
`--approve-apps once` for "Allow once". The card can come back after "Always allow".
|
|
116
|
+
|
|
107
117
|
## Using it from an agent
|
|
108
118
|
|
|
109
119
|
Claude Code, Codex and any other agent that can run shell commands can use Voyager CLI. Install
|
|
@@ -117,8 +127,19 @@ npx skills add voyager-crew/voyager-cli
|
|
|
117
127
|
exit code means, how to wait for a long job without sending the prompt twice, and how to follow
|
|
118
128
|
up with `--chat` and the conversation id it got rather than `--continue`.
|
|
119
129
|
|
|
120
|
-
One job runs at a time
|
|
121
|
-
|
|
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.
|
|
122
143
|
|
|
123
144
|
## Good to know
|
|
124
145
|
|
package/README_ZH.md
CHANGED
|
@@ -26,7 +26,7 @@ Voyager CLI 是 [Voyager](https://github.com/voyager-crew/voyager) 浏览器插
|
|
|
26
26
|
npm install -g @voyager-crew/cli
|
|
27
27
|
```
|
|
28
28
|
|
|
29
|
-
2. 安装 Voyager 插件,需要 2.1.0
|
|
29
|
+
2. 安装 Voyager 插件,需要 2.1.0 或更高版本(`--approve-apps` 和保存回复里的文件需要 2.2.0):
|
|
30
30
|
[Chrome](https://chromewebstore.google.com/detail/iifacdnjakkhjjiengaffnegbndgingi) ·
|
|
31
31
|
[Edge](https://microsoftedge.microsoft.com/addons/detail/voyager/gibmkggjijalcjinbdhcpklodjkhhlne) ·
|
|
32
32
|
[Firefox](https://addons.mozilla.org/firefox/addon/gemini-voyager/)。打开插件弹窗,进入
|
|
@@ -65,6 +65,8 @@ voyager ask --no-wait "…" # 输出一个任务 id
|
|
|
65
65
|
voyager job wait <id> --timeout 10m # 退出码 4 表示还在跑:接着等,千万别重发问题
|
|
66
66
|
```
|
|
67
67
|
|
|
68
|
+
Pro 在 ChatGPT 沙箱里做构建、运行、渲染这类重活时,大约 80 分钟后连接可能会断,断了就什么都不交。`--timebox 70` 让它到 70 分钟就收尾,把手上的东西交出来:成品和半成品分开,打成一个 ZIP。
|
|
69
|
+
|
|
68
70
|
## 项目
|
|
69
71
|
|
|
70
72
|
ChatGPT 的项目可以存放文件,项目里的每个对话都能读到。代码库或论文传一次就行,不用每次提问都附上。
|
|
@@ -94,6 +96,10 @@ voyager ask --repo owner/name "CI 为什么挂了?" # 让 ChatGPT 的 Gi
|
|
|
94
96
|
安装能写到哪里,它就能写到哪里,而且不会先问你。读不到仓库时,voyager 以退出码 3 停下,去
|
|
95
97
|
[github.com/settings/installations](https://github.com/settings/installations) 把仓库加上就行。
|
|
96
98
|
|
|
99
|
+
做某些操作之前(比如往 Drive 写文件),ChatGPT 会在回答里停下,弹一张卡问「允许 ChatGPT 使用 Google Drive 吗?」。
|
|
100
|
+
这时 voyager 以退出码 3 停下,并给出对话链接,你去那里点。插件 2.2.0 及以上,加 `--approve-apps always` 就由插件替你点「始终允许」,
|
|
101
|
+
`--approve-apps once` 点「允许一次」。点过「始终允许」,这张卡之后也可能再出现。
|
|
102
|
+
|
|
97
103
|
## 给 agent 用
|
|
98
104
|
|
|
99
105
|
Claude Code、Codex 以及任何能运行终端命令的 agent 都能用 Voyager CLI。先装上教它们怎么用的 skill:
|
|
@@ -105,8 +111,14 @@ npx skills add voyager-crew/voyager-cli
|
|
|
105
111
|
[`skills/voyager/SKILL.md`](skills/voyager/SKILL.md) 就是写给它们看的:JSON 输出、每个退出码的含义、怎么等长任务而不把问题发两遍,以及接着问时用
|
|
106
112
|
`--chat` 加上次拿到的对话 id,而不是 `--continue`。
|
|
107
113
|
|
|
108
|
-
|
|
109
|
-
|
|
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)` 等),以页面最近一次报告的为准。
|
|
110
122
|
|
|
111
123
|
## 须知
|
|
112
124
|
|