@tryvoyager/cli 0.1.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/README.md ADDED
@@ -0,0 +1,67 @@
1
+ # voyager-cli
2
+
3
+ Go CLI for secure local Voyager setup.
4
+
5
+ ## Install
6
+
7
+ The production install path is Bun:
8
+
9
+ ```bash
10
+ bun add -g @tryvoyager/cli
11
+ ```
12
+
13
+ This installs the `voyager` binary globally. During `voyager init`, the CLI provisions its managed local runtime from the assets bundled inside the CLI package itself.
14
+
15
+ ## Commands
16
+
17
+ - `voyager init`
18
+ - `voyager doctor`
19
+ - `voyager uninstall`
20
+
21
+ ## `voyager init` flow
22
+
23
+ `voyager init` is interactive and defaults to Kernel managed-auth onboarding:
24
+
25
+ 1. Resolves backend URL from env (`VOYAGER_API_BASE_URL` or `VOYAGER_BACKEND_URL`) with fallback `https://d17l2ug4lrx6gk.cloudfront.net`
26
+ 2. Installs or reuses the managed local Voyager runtime under `~/.voyager/runtime/voyager/<version>/`
27
+ 3. Prompts for Codex/Cursor installation targets
28
+ 4. Reuses machine identity if present; otherwise creates a new local Voyager Auth identity
29
+ 5. Starts init assignment flow (always):
30
+ - CLI calls `POST /v1/onboarding/init/assignment/start` with signed request
31
+ - User completes Google sign-in in hosted URL/live view (if needed)
32
+ - CLI calls `POST /v1/onboarding/init/assignment/complete`
33
+ - Backend links canonical user identity, machine binding, and global Google profile
34
+ 6. Skips provider pre-consent during init (providers are onboarded on-demand after setup)
35
+ 7. Writes runner script at `~/.voyager/bin/voyager-mcp-runner`
36
+ 8. Installs MCP config for selected agents
37
+ - Codex install writes `~/.codex/config.toml` section `[mcp_servers.voyager]` with `tool_timeout_sec = 600`
38
+
39
+ If an existing machine binding and global profile are already valid, `voyager init` reuses them.
40
+
41
+ ## Security model
42
+
43
+ - Supabase service role/AWS secrets are never required in CLI.
44
+ - Bootstrap enrollment uses Kernel managed-auth assignment endpoints.
45
+ - Local secrets are stored in macOS Keychain (`com.voyager.cli`).
46
+ - `~/.voyager/identity.json` stores references/metadata, not raw secrets.
47
+
48
+ ## Runtime requirements
49
+
50
+ - End users only need the `voyager` binary.
51
+ - Go is only required to build the CLI from source (not to run it).
52
+ - Voyager installs its bundled local runtime into a managed directory under `~/.voyager/runtime/voyager/<version>/`.
53
+ - Bun is managed internally by the CLI for runtime installation and execution; end users do not need to install it themselves.
54
+ - First-time runtime provisioning does not require a second npm package fetch. A local `voyager-mcp` checkout is only used as a developer fallback when the bundled runtime assets are unavailable.
55
+ - Optional: `VOYAGER_SIGNED_AUTH_PROBE_PROVIDER` overrides the provider slug used by signed-auth probe checks (default `__signed_auth_probe__`).
56
+
57
+ ## Build from source
58
+
59
+ ```bash
60
+ /usr/local/go/bin/go build ./...
61
+ ```
62
+
63
+ ## Local dev run
64
+
65
+ ```bash
66
+ /usr/local/go/bin/go run . init
67
+ ```
package/bin/voyager ADDED
Binary file
package/package.json ADDED
@@ -0,0 +1,22 @@
1
+ {
2
+ "name": "@tryvoyager/cli",
3
+ "version": "0.1.1",
4
+ "description": "Voyager CLI for secure local MCP setup on macOS",
5
+ "license": "UNLICENSED",
6
+ "private": false,
7
+ "os": [
8
+ "darwin"
9
+ ],
10
+ "files": [
11
+ "bin/voyager",
12
+ "runtime-dist",
13
+ "README.md"
14
+ ],
15
+ "bin": {
16
+ "voyager": "./bin/voyager"
17
+ },
18
+ "scripts": {
19
+ "build:package": "bun scripts/build-package-cli.ts",
20
+ "prepack": "bun run build:package"
21
+ }
22
+ }