Add a Beeper installer wired to the shipped device-auth flow

[Miyamura80]

What

Adds scripts/install-beeper.sh, an agent-friendly helper that wires Beeper into the Edison Watch MCP gateway on macOS. Rebased onto current main, so it targets the shipped browser/device-authorization flow (stdiod #16 + backend scoped device authorization) rather than the old API-key + step-up path.

Why it changed shape since the first draft

Two things landed / were found after the first version:

1. Device authorization shipped. edison-stdiod login is now a browser/device OAuth flow (no API-key paste), and server add submits a device-scoped request for admin approval. The old machinery this script carried (api-key login, POST /servers/{name}/env token bind, STEP_UP_REQUIRED handling, 409 remove+re-add) no longer applies and is removed.
2. Beeper serves MCP only from the Desktop app. The headless beeper Server exposes no MCP endpoint (github.com/beeper/cli issue #20); @beeper/desktop-mcp wraps the Desktop app's endpoint, enabled once under Settings > Developers > MCP. A fully unattended install is therefore not possible today, so the script automates the Edison side and prints the exact human steps for the rest instead of pretending they are automatable.

What the script does

Automated:

• Install prerequisites (npx, edison-stdiod).
• edison-stdiod login --backend <url> device authorization (idempotent via the persisted client credential; --no-open for headless, --relogin to force).
• edison-stdiod install to supervise the daemon.
• edison-stdiod server add beeper --command npx --arg=-y --arg=@beeper/desktop-mcp (submits for approval; server list is the idempotency check).

Printed as explicit action: lines (the human-gated steps):

• Enable MCP in Beeper Desktop and link chats there.
• Approve the beeper server once in the dashboard.
• Set BEEPER_ACCESS_TOKEN on that server in the dashboard. The script discovers a reusable token and prints it masked; under device auth the child's env is delivered by the backend, so the script does not fabricate an env endpoint.

Agent-friendly throughout: every input is a flag or UPPER_SNAKE env var, --dry-run / --yes / --json / --verbose, TTY-aware colors, resource+verb subcommands (install, doctor, status, token, mcp-url, uninstall), and fail-fast errors that print the exact fix.

Also

• Removes docs/headless-server-add.md: it proposed a device-pairing token to get past the step-up gate, which is exactly what the shipped device-authorization flow does. Superseded.
• The earlier README platform edit was dropped during rebase; current main already covers platform support and the new login flow.

Test plan

• bash -n + repo AI-writing hook pass
• install --dry-run exercises the full flow and exits 0
• End-to-end on macOS: Beeper Desktop MCP enabled, device auth approved, server approved in dashboard, token set, tool call round-trips

🤖 Generated with Claude Code

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[cubic-dev-ai]

2 issues found across 2 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="scripts/install-beeper.sh">

<violation number="1" location="scripts/install-beeper.sh:84">
P2: `uninstall --dry-run` fails with the non-interactive confirmation error instead of previewing the uninstall. Treating dry-run as an automatic confirmation would preserve the documented “change nothing” preview behavior.</violation>
</file>

<file name="README.md">

<violation number="1" location="README.md:116">
P3: The README now advertises Linux and Windows supervisors, but `edison-stdiod install --help` still describes `install` as a macOS LaunchAgent command. Updating the CLI help with this documentation change would keep the advertised interface and the runnable help output consistent.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

P2: uninstall --dry-run fails with the non-interactive confirmation error instead of previewing the uninstall. Treating dry-run as an automatic confirmation would preserve the documented “change nothing” preview behavior.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At scripts/install-beeper.sh, line 84:

<comment>`uninstall --dry-run` fails with the non-interactive confirmation error instead of previewing the uninstall. Treating dry-run as an automatic confirmation would preserve the documented “change nothing” preview behavior.</comment>

<file context>
@@ -0,0 +1,452 @@
+
+confirm() {
+  [ "$ASSUME_YES" -eq 1 ] && return 0
+  [ "$INTERACTIVE" -eq 0 ] && die "refusing to run a confirming action non-interactively: $1" \
+    "pass --yes to proceed, or --dry-run to preview"
+  printf '%s [y/N] ' "$1" >&2; read -r ans; [ "$ans" = "y" ] || [ "$ans" = "Y" ]
</file context>

[cubic-dev-ai]

P3: The README now advertises Linux and Windows supervisors, but edison-stdiod install --help still describes install as a macOS LaunchAgent command. Updating the CLI help with this documentation change would keep the advertised interface and the runnable help output consistent.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At README.md, line 116:

<comment>The README now advertises Linux and Windows supervisors, but `edison-stdiod install --help` still describes `install` as a macOS LaunchAgent command. Updating the CLI help with this documentation change would keep the advertised interface and the runnable help output consistent.</comment>

<file context>
@@ -112,7 +113,7 @@ TLDR: `edison-stdiod --help` (and `edison-stdiod <command> --help` for any subco
 | --- | --- |
 | `login` | Persist credentials + backend URL to `~/.config/edison-stdiod/config.toml` (mode `0600`). Merges on re-run, so you can rotate the API key without re-supplying the backend URL. |
-| `install` | Register the OS supervisor unit (macOS LaunchAgent) so the daemon starts at login and restarts on crash. Requires `login` first. |
+| `install` | Register the OS supervisor unit (LaunchAgent on macOS, systemd `--user` unit on Linux, Scheduled Task on Windows) so the daemon starts at login and restarts on crash. Requires `login` first. |
 | `uninstall` | Stop and remove the supervisor unit. Pass `--purge` to also delete the persisted config and logs. |
 | `run` | Run the daemon in the foreground (normally invoked by the service unit). Reads config or accepts `--backend` / `--api-key` / `--device-id` / `--label` flags (also via `EDISON_*` env vars). |
</file context>

[cubic-dev-ai]

All reported issues were addressed across 1 file (changes from recent commits).

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 1 file (changes from recent commits).

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Re-trigger cubic</sub>

[cubic-dev-ai]

All reported issues were addressed across 1 file (changes from recent commits).

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Re-trigger cubic</sub>

[cubic-dev-ai]

1 issue found across 1 file (changes from recent commits).

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="scripts/install-beeper.sh">

<violation number="1" location="scripts/install-beeper.sh:606">
P2: Binding exposes a discovered or environment-supplied Beeper credential in curl's process arguments while the request runs. Stream the JSON body through stdin instead of passing it to `--data`.</violation>
</file>

<sub>Tip: Review your code locally with the cubic CLI to iterate faster.

Re-trigger cubic</sub>

[cubic-dev-ai]

P2: Binding exposes a discovered or environment-supplied Beeper credential in curl's process arguments while the request runs. Stream the JSON body through stdin instead of passing it to --data.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At scripts/install-beeper.sh, line 606:

<comment>Binding exposes a discovered or environment-supplied Beeper credential in curl's process arguments while the request runs. Stream the JSON body through stdin instead of passing it to `--data`.</comment>

<file context>
@@ -579,6 +580,44 @@ cmd_token() {
+  local code
+  code="$(curl -s -o /dev/null -w '%{http_code}' -m 60 --connect-timeout 5 -X POST "$url" \
+    -H "Authorization: Bearer ${EW_API_KEY}" -H "Content-Type: application/json" \
+    --data "$(printf '{"env":{"BEEPER_ACCESS_TOKEN":"%s"}}' "$tok")" 2>/dev/null || true)"
+  [ -z "$code" ] && code="000"
+  case "$code" in
</file context>

Suggested change

	--data "$(printf '{"env":{"BEEPER_ACCESS_TOKEN":"%s"}}' "$tok")" 2>/dev/null || true)"
	--data-binary @- < <(printf '{"env":{"BEEPER_ACCESS_TOKEN":"%s"}}' "$tok") 2>/dev/null || true)"