@voyager-crew/cli 0.2.0 → 0.4.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 +34 -1
- package/README_ZH.md +28 -1
- package/dist/cli.mjs +825 -134
- package/package.json +4 -3
- package/skills/voyager/SKILL.md +41 -12
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
|
|
@@ -57,6 +58,11 @@ Every ask uses GPT-6 Pro in chat mode unless you pick another effort, and leaves
|
|
|
57
58
|
Voyager never switches ChatGPT to Work mode. The reply lands in `~/.voyager/jobs/<id>/output/`,
|
|
58
59
|
and `--json` prints its path along with the conversation link.
|
|
59
60
|
|
|
61
|
+
Files the reply offers (a CSV, a chart, a zip ChatGPT made) are saved beside it in `files/`,
|
|
62
|
+
with `-2`, `-3`… added when a name repeats; `--no-files` leaves them in ChatGPT. A file that
|
|
63
|
+
cannot be downloaded is reported without failing the command, since the reply itself was
|
|
64
|
+
saved: `voyager read <link>` tries again later.
|
|
65
|
+
|
|
60
66
|
### Long answers
|
|
61
67
|
|
|
62
68
|
Pro can think for hours. `ask` waits as long as ChatGPT is still working on the reply, and
|
|
@@ -68,6 +74,10 @@ voyager ask --no-wait "…" # prints a job id
|
|
|
68
74
|
voyager job wait <id> --timeout 10m # exit 4 means still running: wait again, never resend
|
|
69
75
|
```
|
|
70
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
|
+
|
|
71
81
|
## Projects
|
|
72
82
|
|
|
73
83
|
A ChatGPT project keeps files that every chat in it can read, so a codebase or a paper goes
|
|
@@ -81,6 +91,29 @@ voyager project files "Thesis"
|
|
|
81
91
|
voyager project remove "Thesis" old-notes.md # immediate and permanent; asks first
|
|
82
92
|
```
|
|
83
93
|
|
|
94
|
+
## Google Drive and GitHub
|
|
95
|
+
|
|
96
|
+
ChatGPT's own Google Drive and GitHub apps can read your files directly, with no upload through the page. Connect them in ChatGPT first.
|
|
97
|
+
|
|
98
|
+
```sh
|
|
99
|
+
voyager ask --drive ./paper.pdf "Summarize the method" # puts it on Drive and links it in the prompt
|
|
100
|
+
voyager ask --repo owner/name "Why does CI fail?" # ChatGPT's GitHub app reads the repository
|
|
101
|
+
```
|
|
102
|
+
|
|
103
|
+
`--drive` packs like `--attach` but has no 64 MiB limit (files over 20 MiB inside a folder are still left out), and uploads with [rclone](https://rclone.org/drive/):
|
|
104
|
+
set `VOYAGER_DRIVE_REMOTE` (or `"driveRemote"` in `~/.voyager/config.json`) to a folder on a Google Drive
|
|
105
|
+
remote, such as `gdrive:Voyager`, on the same Google account ChatGPT's Drive app uses. The files stay there.
|
|
106
|
+
|
|
107
|
+
`--repo` asks ChatGPT to commit only to a new `chatgpt/*` branch, so you review before merging. That is a request, not
|
|
108
|
+
a restriction: the app writes wherever its GitHub installation allows, without asking. If it cannot reach the
|
|
109
|
+
repository, voyager stops with exit code 3; add the repository at
|
|
110
|
+
[github.com/settings/installations](https://github.com/settings/installations).
|
|
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
|
+
|
|
84
117
|
## Using it from an agent
|
|
85
118
|
|
|
86
119
|
Claude Code, Codex and any other agent that can run shell commands can use Voyager CLI. Install
|
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/)。打开插件弹窗,进入
|
|
@@ -52,6 +52,10 @@ voyager read <链接|id> # 保存某个对话的最
|
|
|
52
52
|
默认用聊天模式下的 GPT-6 Pro,除非你另选思考强度;问完保持在这个选择上。Voyager 不会把 ChatGPT
|
|
53
53
|
切到「工作」模式。回答保存在 `~/.voyager/jobs/<id>/output/`,加 `--json` 会输出文件路径和对话链接。
|
|
54
54
|
|
|
55
|
+
回答里给出的文件(ChatGPT 生成的 CSV、图表、zip 等)会存到旁边的 `files/` 里,重名的依次加 `-2`、`-3`;
|
|
56
|
+
加 `--no-files` 就不下载。某个文件下载失败只会报告,不会让命令失败,因为回答本身已经保存:之后可以用
|
|
57
|
+
`voyager read <链接>` 再取一次。
|
|
58
|
+
|
|
55
59
|
### 很长的回答
|
|
56
60
|
|
|
57
61
|
Pro 可能要想好几个小时。只要 ChatGPT 还在写,`ask` 就一直等;连续 20 分钟完全没动静才算失败。想先拿回终端,就先提交、之后再取:
|
|
@@ -61,6 +65,8 @@ voyager ask --no-wait "…" # 输出一个任务 id
|
|
|
61
65
|
voyager job wait <id> --timeout 10m # 退出码 4 表示还在跑:接着等,千万别重发问题
|
|
62
66
|
```
|
|
63
67
|
|
|
68
|
+
Pro 在 ChatGPT 沙箱里做构建、运行、渲染这类重活时,大约 80 分钟后连接可能会断,断了就什么都不交。`--timebox 70` 让它到 70 分钟就收尾,把手上的东西交出来:成品和半成品分开,打成一个 ZIP。
|
|
69
|
+
|
|
64
70
|
## 项目
|
|
65
71
|
|
|
66
72
|
ChatGPT 的项目可以存放文件,项目里的每个对话都能读到。代码库或论文传一次就行,不用每次提问都附上。
|
|
@@ -73,6 +79,27 @@ voyager project files "论文"
|
|
|
73
79
|
voyager project remove "论文" old-notes.md # 立即删除且无法恢复,会先确认
|
|
74
80
|
```
|
|
75
81
|
|
|
82
|
+
## Google Drive 和 GitHub
|
|
83
|
+
|
|
84
|
+
ChatGPT 自带的 Google Drive 和 GitHub 应用可以直接读你的文件,不用再经过网页上传。先在 ChatGPT 里连上它们。
|
|
85
|
+
|
|
86
|
+
```sh
|
|
87
|
+
voyager ask --drive ./paper.pdf "总结一下方法部分" # 放到 Drive 上,把链接写进提示
|
|
88
|
+
voyager ask --repo owner/name "CI 为什么挂了?" # 让 ChatGPT 的 GitHub 应用读这个仓库
|
|
89
|
+
```
|
|
90
|
+
|
|
91
|
+
`--drive` 的打包方式和 `--attach` 一样,但没有 64 MiB 的限制(文件夹里超过 20 MiB 的单个文件仍会被跳过),用 [rclone](https://rclone.org/drive/) 上传:
|
|
92
|
+
把 `VOYAGER_DRIVE_REMOTE`(或 `~/.voyager/config.json` 里的 `"driveRemote"`)设成某个 Google Drive remote 上的文件夹,
|
|
93
|
+
比如 `gdrive:Voyager`,而且要和 ChatGPT 的 Drive 应用是同一个 Google 账号。文件会一直留在那里。
|
|
94
|
+
|
|
95
|
+
`--repo` 会要求 ChatGPT 只往一个新的 `chatgpt/*` 分支提交,你看过再合并。这只是要求,不是限制:它的 GitHub
|
|
96
|
+
安装能写到哪里,它就能写到哪里,而且不会先问你。读不到仓库时,voyager 以退出码 3 停下,去
|
|
97
|
+
[github.com/settings/installations](https://github.com/settings/installations) 把仓库加上就行。
|
|
98
|
+
|
|
99
|
+
做某些操作之前(比如往 Drive 写文件),ChatGPT 会在回答里停下,弹一张卡问「允许 ChatGPT 使用 Google Drive 吗?」。
|
|
100
|
+
这时 voyager 以退出码 3 停下,并给出对话链接,你去那里点。插件 2.2.0 及以上,加 `--approve-apps always` 就由插件替你点「始终允许」,
|
|
101
|
+
`--approve-apps once` 点「允许一次」。点过「始终允许」,这张卡之后也可能再出现。
|
|
102
|
+
|
|
76
103
|
## 给 agent 用
|
|
77
104
|
|
|
78
105
|
Claude Code、Codex 以及任何能运行终端命令的 agent 都能用 Voyager CLI。先装上教它们怎么用的 skill:
|