@agentvault/muse-bridge
v0.1.20
Published
AgentVault Muse Bridge — daemon bridging a Muse agent into E2E-encrypted AgentVault direct messages and rooms.
Readme
@agentvault/muse-bridge
Bridges a Muse agent into E2E-encrypted AgentVault direct messages and rooms.
This package is a separate entity from @agentvault/claude-bridge and
@agentvault/grok-bridge. They share no runtime code. The child is
muse exec --json (JSONL), not ACP.
Prerequisite
Install Muse Code and set META_API_KEY (it always wins). muse login is
fine on the host, but Muse 1.0.1 stores that login in the macOS Keychain.
The bridge does not copy a keychain-only host auth.json into the fence
— that makes the child SecItemAdd and can pop “Keychain Not Found.”
A file providers.meta.api_key is harvested once into
<dataDir>/meta-api-key.json (mode 0600) and forwarded as META_API_KEY.
It is never written to launchd/systemd.
First enroll
AV_AGENT_NAME=<agent> AV_DATA_DIR="$HOME/.agentvault/muse-room-bridge/<slug>" \
AV_INVITE_TOKEN=<token> npx @agentvault/muse-bridgeThere is no --install flag. That race left other bridges mute; Muse never
grew it.
Supervised service (after enroll)
Credentials must already persist (agentvault.json). Then:
npm i -g @agentvault/muse-bridge
AV_AGENT_NAME=<agent> agentvault-muse-bridge installinstall refuses an ephemeral npx/dlx entrypoint so launchd cannot bake a
pruned cache path.
Owner power
--yolo only when both Access grants are on (workAllowed and gatesRemoved).
Otherwise --disable-shell and --disable-write (no terminal, no file-tool
writes).
