@1presence/bridge 0.66.0 → 0.67.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 +21 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -22,6 +22,27 @@ On first run, a browser window will open to sign in to your 1Presence account. Y
|
|
|
22
22
|
|
|
23
23
|
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.
|
|
24
24
|
|
|
25
|
+
## Admin: running the bridge as another user
|
|
26
|
+
|
|
27
|
+
If your 1Presence account is an **admin**, the sign-in screen shows a user picker
|
|
28
|
+
instead of connecting immediately. Choose which 1Presence user this bridge runs
|
|
29
|
+
as — it defaults to **you** — and click Connect. Picking another user lets you
|
|
30
|
+
drive their account (their vault, connectors, and history) through your local
|
|
31
|
+
Claude Code, which is handy for onboarding testers who don't run the bridge
|
|
32
|
+
themselves. You never need their password; the picker mints a scoped token for
|
|
33
|
+
the selected user server-side.
|
|
34
|
+
|
|
35
|
+
The target user must have **Local Claude Code access** granted in the admin panel
|
|
36
|
+
(the same permission that gates your own bridge and also lets bridge turns run
|
|
37
|
+
free on your Claude subscription). The picker flags anyone who isn't eligible yet.
|
|
38
|
+
|
|
39
|
+
### Multiple sessions at once
|
|
40
|
+
|
|
41
|
+
Because every session is keyed by the connected user, you can run several bridges
|
|
42
|
+
side by side — each in its own terminal, each impersonating a **different** user —
|
|
43
|
+
and they won't interfere. Running two bridges for the *same* user at once is not
|
|
44
|
+
supported (the second displaces the first).
|
|
45
|
+
|
|
25
46
|
## How it works
|
|
26
47
|
|
|
27
48
|
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.
|