@1presence/bridge 0.80.0 → 0.81.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 +2 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -51,6 +51,8 @@ Conversations are stateful — the bridge maps each 1Presence conversation to a
|
|
|
51
51
|
|
|
52
52
|
Your OAuth tokens and vault data stay server-side — nothing sensitive is stored locally beyond the auth token.
|
|
53
53
|
|
|
54
|
+
On startup the bridge makes one request to the public npm registry (`registry.npmjs.org`) to check for a newer version, and self-updates via `npx` when one exists. The request carries no account data — it is the same anonymous lookup `npm view` performs — and if the registry is unreachable the bridge starts normally on the version you have. Beyond that check, the bridge talks only to the 1Presence gateway and your local `claude` install.
|
|
55
|
+
|
|
54
56
|
## Model
|
|
55
57
|
|
|
56
58
|
**Every start** the bridge asks which Claude model to use — the choice is held in memory for that run only and nothing is written to disk, so restarting always asks again. Pick "Use Claude Code default" to defer to your local Claude Code default, or pin one of the latest models per family: `claude-opus-5`, `claude-fable-5`, `claude-sonnet-5`, `claude-haiku-4-5`. If the prompt times out it auto-selects "Use Claude Code default", which tracks whatever model Claude Code serves for your plan.
|