@1presence/bridge 0.66.0 → 0.68.0

package/README.md

@@ -22,6 +22,27 @@ On first run, a browser window will open to sign in to your 1Presence account. Y
 
 Once connected, your 1Presence app on any device automatically routes to your local Claude Code session. When you stop the bridge, 1Presence falls back to platform mode.
 
+## Admin: running the bridge as another user
+
+If your 1Presence account is an **admin**, the sign-in screen shows a user picker
+instead of connecting immediately. Choose which 1Presence user this bridge runs
+as — it defaults to **you** — and click Connect. Picking another user lets you
+drive their account (their vault, connectors, and history) through your local
+Claude Code, which is handy for onboarding testers who don't run the bridge
+themselves. You never need their password; the picker mints a scoped token for
+the selected user server-side.
+
+The target user must have **Local Claude Code access** granted in the admin panel
+(the same permission that gates your own bridge and also lets bridge turns run
+free on your Claude subscription). The picker flags anyone who isn't eligible yet.
+
+### Multiple sessions at once
+
+Because every session is keyed by the connected user, you can run several bridges
+side by side — each in its own terminal, each impersonating a **different** user —
+and they won't interfere. Running two bridges for the *same* user at once is not
+supported (the second displaces the first).
+
 ## How it works
 
 The bridge connects outbound to the 1Presence gateway as a persistent WebSocket. When you send a message from the app, the gateway relays it to the bridge, which spawns a `claude` subprocess with your personal system prompt and all 1Presence tools (vault, Gmail, Drive, Calendar, MemPalace, and more) wired in via MCP. Responses stream back in real time.

package/dist/config.js

@@ -75,29 +75,37 @@ function detectClaudeDefaultModel() {
 }
 // The fixed menu — keep the option count small so the timeout default is easy
 // to glance at. Option 1's `model: null` means "let Claude Code pick" (no
-// `--model` flag passed to the subprocess).
-// NB on `[1m]` (1M-context Opus): the bridge always runs on the user's claude.ai
-// subscription (it strips ANTHROPIC_API_KEY — see claude.ts), and it is UNCONFIRMED
-// whether the 1M context window (a tier-gated API beta) is servable on subscription
-// auth. It is the default (see DEFAULT_OPTION_NUM below); if it proves unservable on
-// a given plan, the user can arrow to option 2 for the plain variant. (An earlier
-// every-turn `400 / "unknown"` was first blamed on this but was actually a tool-schema
-// bug that hit every model — see vault/Bugs.md.) `num` must stay contiguous 1..N in
-// array order — the jump-key handler maps a typed digit `n` to `idx = n - 1`.
+// `--model` flag passed to the subprocess). This is the DYNAMIC default: it
+// tracks whatever model Claude Code actually serves for the user's plan (the
+// probe above surfaces it as a live suffix — on most accounts today that's the
+// 1M-context Opus) and self-heals if a pinned id is ever unservable. The
+// remaining rows pin explicit ids for users who want a specific model.
+// `num` must stay contiguous 1..N in array order — the jump-key handler maps a
+// typed digit `n` to `idx = n - 1`.
+//
+// NB there is no way to *enumerate* the models available on subscription auth:
+// the `/v1/models` API needs an API key (the bridge strips ANTHROPIC_API_KEY —
+// see claude.ts) and the CLI exposes only the single default via the init event.
+// So this list is hand-maintained — add/remove ids here as the roster changes.
+// (We dropped the standalone `claude-opus-4-8[1m]` row: it duplicated option 1,
+// whose Claude Code default already resolves to the 1M Opus on subscription, and
+// pinning `[1m]` risked a hard failure where the null default degrades gracefully.
+// An earlier every-turn `400 / "unknown"` was once blamed on `[1m]` but was
+// actually a tool-schema bug that hit every model — see vault/Bugs.md.)
 const MODEL_OPTIONS = [
     { num: 1, model: null, label: 'Use Claude Code default' },
     { num: 2, model: 'claude-opus-4-8', label: 'claude-opus-4-8' },
-    { num: 3, model: 'claude-opus-4-8[1m]', label: 'claude-opus-4-8[1m]  (1M context — experimental on subscription)' },
-    { num: 4, model: 'claude-opus-4-7', label: 'claude-opus-4-7' },
+    { num: 3, model: 'claude-opus-4-7', label: 'claude-opus-4-7' },
+    { num: 4, model: 'claude-fable-5', label: 'claude-fable-5' },
     { num: 5, model: 'claude-sonnet-4-6', label: 'claude-sonnet-4-6' },
     { num: 6, model: 'claude-haiku-4-5', label: 'claude-haiku-4-5' },
 ];
 const PROMPT_TIMEOUT_MS = 10_000;
-// Default to the 1M-context Opus (`claude-opus-4-8[1m]`). The `[1m]` window is a
-// tier-gated API beta whose availability on subscription auth is unconfirmed (see
-// the NB above), but it's our preferred default — anyone can arrow to option 2 for
-// the plain variant if `[1m]` proves unservable on their plan.
-const DEFAULT_OPTION_NUM = 3;
+// Default to option 1 ("Use Claude Code default") — the dynamic choice that
+// follows whatever Claude Code serves for the user's plan (currently the 1M
+// Opus on most accounts) and degrades gracefully rather than pinning a possibly
+// unservable id. Users can arrow to a pinned model if they want one.
+const DEFAULT_OPTION_NUM = 1;
 function promptForModel(defaultModel) {
     return new Promise((resolve) => {
         const initialIdx = Math.max(0, MODEL_OPTIONS.findIndex((o) => o.num === DEFAULT_OPTION_NUM));

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@1presence/bridge",
-  "version": "0.66.0",
+  "version": "0.68.0",
   "description": "Run 1Presence on your Mac and use your Claude.ai Pro subscription from any device",
   "license": "Apache-2.0",
   "type": "module",