@voyager-crew/cli 0.4.0 → 0.5.1

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@voyager-crew/cli",
3
- "version": "0.4.0",
3
+ "version": "0.5.1",
4
4
  "description": "Ask ChatGPT from your terminal or your coding agent, through the Voyager browser extension",
5
5
  "keywords": [
6
6
  "chatgpt",
@@ -47,7 +47,7 @@
47
47
  },
48
48
  "devDependencies": {
49
49
  "@types/node": "^24.9.0",
50
- "@voyager-crew/bridge-protocol": "^0.4.0",
50
+ "@voyager-crew/bridge-protocol": "^0.5.0",
51
51
  "fflate": "0.8.2",
52
52
  "oxfmt": "^0.65.0",
53
53
  "oxlint": "^1.80.0",
@@ -98,6 +98,7 @@ ChatGPT sees nothing of your conversation, so the prompt carries everything. Pro
98
98
  - Say what it cannot see: callers outside the material, and the real defaults (timeouts, limits), so it does not rate severity from settings nobody uses.
99
99
  - In ordinary debugging or review work, avoid words like bypass, exploit, attack, inject, payload or crack; a safety check can take such a prompt for intrusion work and stop the turn halfway. Say workaround, trigger condition, defect or stress test.
100
100
  - When files should come back, ask for one ZIP.
101
+ - For a mathematics question (a proof, a derivation, an algorithm's correctness or bound), add `--preset math`. It opens the prompt with a research framing: a long session, depth before speed, every conclusion derived, verified or marked as a conjecture. `--preset <file>` opens it with a text file instead, for an opening the person wrote; `--dry-run` shows the combined prompt.
101
102
 
102
103
  ## Exit codes
103
104
 
@@ -107,11 +108,11 @@ ChatGPT sees nothing of your conversation, so the prompt carries everything. Pro
107
108
  | 2 | failed (bad input, or the page changed); `send-unverified`: the prompt may be sent | report `error.message`; never resend `send-unverified` |
108
109
  | 3 | needs a person (`login-required`, `challenge`, `approval-required`, `rate-limited`, …) | stop and tell the person what `error.code` asks of them |
109
110
  | 4 | wait timed out; job continues | `voyager job wait <jobId> --json` again; do not resend |
110
- | 5 | busy: another job runs (`error.details.activeJobId`) | wait for that job, or ask the person |
111
+ | 5 | busy: no room for this job (`error.details.activeJobId`, `maxJobs`, `conflict`) | wait for that job, or ask the person |
111
112
  | 6 | lost page or server (`detached`), the reply stalled (`reply-stalled`), or cancelled | tell the person; the prompt may already be in ChatGPT |
112
113
  | 7 | not paired, or the extension is offline | ask the person to pair or open the browser |
113
114
 
114
- Exactly one job runs at a time, and jobs are never queued. Each prompt is submitted **once**. After any exit other than 0, report to the person and let them decide; a second `voyager ask` with the same prompt would send it again. `send-unverified` means the page may have sent it, so the person checks ChatGPT first.
115
+ One job runs at a time unless the person turned on parallel jobs in the Voyager popup: then `voyager status --json` shows `maxJobs` above 1, and that many jobs, of this agent or others, run side by side, each in its own tab. Jobs are never queued. Two asks into the same conversation, or two `project` changes, never run together: the later one is `busy` with `error.details.conflict`. Jobs side by side also take turns at typing and clicking: a job held up by another job stuck past the time its step may take ends with exit 5 mid-job (`error.details.pageTurn`), and that step was never sent; if it was approving an app card, the prompt is already in ChatGPT, so do not ask again. With jobs side by side, follow up only with `--chat <the conversationId your ask returned>`; never `--continue`. Each prompt is submitted **once**. After any exit other than 0, report to the person and let them decide; a second `voyager ask` with the same prompt would send it again. `send-unverified` means the page may have sent it, so the person checks ChatGPT first.
115
116
 
116
117
  ## The browser tab
117
118