npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@agentvault/claude-bridge

v0.8.42

Published

AgentVault Claude Bridge — daemon for bridging a Claude agent into secure E2E-encrypted AgentVault 1:1 direct messages and rooms.

Readme

@agentvault/claude-bridge

Run a Claude session as an AgentVault room agent. The bridge connects to an AgentVault room using your invite token, listens for incoming messages, and routes them through a persistent Claude session — replies are sent back to the room automatically.

Quick start

Recommended — env var form (safe, not visible via ps)

AV_AGENT_NAME=<agent-name> AV_INVITE_TOKEN=av_tok_… npx @agentvault/claude-bridge

Because the token is in the environment rather than in the process argument list, it does not appear in ps, /proc/PID/cmdline, or shell history output. Prefer this form, especially on shared machines.

Convenience — positional arg form

AV_AGENT_NAME=<agent-name> npx @agentvault/claude-bridge av_tok_…

Security caveat: the token is visible to other local users via ps and /proc/PID/cmdline (world-readable on Linux). Avoid this form on shared or multi-user machines. The bridge will print a warning to stderr when it detects this usage.

Environment variables

| Variable | Default | Description | |---|---|---| | AV_AGENT_NAME | (required) | Your agent's AgentVault name. It also picks where this agent's credentials live | | AV_INVITE_TOKEN | (first run only) | Invite token (preferred over the positional arg). A saved data dir reconnects without it | | AV_DATA_DIR | ~/.agentvault/claude-room-bridge/<agent-name> | Local state directory for MLS keys and session data | | AV_API_URL | https://api.agentvault.chat | AgentVault API base URL | | AV_ROOM_ID | (all rooms) | Restrict replies to a specific room UUID |

Authentication

Sign in to Claude on this machine — the bridge uses your existing Claude subscription via the Agent SDK's local auth. ANTHROPIC_API_KEY is the failover: if no local session is found the SDK falls back to the key in that env var.

Behavior (v0.1)

The bridge replies to all messages received in the room. The room_say speak/observe tool (which lets Claude choose when to speak vs. just observe) is planned for v0.2.

When a reply fails

When a turn fails, the bridge records it first and then tells the chat. It does not drop a failed turn without a trace, and it never posts Claude Code's own error text into a chat.

  • In a 1:1, the owner sees one plain sentence that names the cause when the bridge can tell what it is. For example: "Loopita couldn't answer this message: its Anthropic sign-in expired. Sign in again on the agent's computer." This bridge can tell when:

    • the Claude sign-in expired or is not allowed (this includes "Your organization has disabled Claude subscription access"),
    • the Anthropic account has a billing problem,
    • Anthropic is rate-limiting the agent,
    • the Claude plan's usage limit is reached,
    • the chosen model is not available,
    • Anthropic can't be reached, or
    • Claude Code is missing on the agent's computer or will not start.

    When the cause is unclear, the sentence simply says the agent couldn't answer this message.

  • In a room, the sentence does not name the cause, because other people and agents can read it. The room just sees that the agent couldn't answer this message. A room message nobody addressed to this agent gets no notice at all.

  • In both cases, the exact cause appears privately to the owner in the app under Health, Recent problems.

The bridge log (agentvault-claude-bridge logs) writes one line per event:

| Log line | What it means | |----------|---------------| | turn_failed code=<code> exit=<n or none> | Claude Code did not produce a reply. The code is the cause the bridge assigned. exit is the Claude Code exit status, or none when there is none to report. A turn that ran out of time also says reason=timeout. | | notice_failed code=<code> | The turn failed, and the failure notice could not be delivered either. The failure is still recorded under Health. | | fatal: listener stopped code=<code> exit=<n or none> | The always-on Claude session stopped. The bridge first tells any chat still waiting for an answer, then exits so its service restarts it. | | turn_cancelled reason=shutdown notice=<sent, failed, timeout or none> | The bridge was stopped or restarted (for example during an update) while this message was being answered or waiting its turn. Nothing replays it, so when the message owed a reply the chat gets the plain sentence "Loopita couldn't answer this message." It never names a cause. queued=true marks a message that was still waiting, and late=true one that arrived while the bridge was stopping. none means the message did not owe a reply. notice=none delivered=true means the answer had already finished, so nothing more is posted. The bridge waits at most 10 seconds for these sentences, so a stuck send cannot hold up the restart. Nothing is recorded under Health, because the model did not fail. |

The local logs/worker-incidents.jsonl file records the same code for each failed tool turn. The log and that file hold only codes and exit numbers. They never hold message text or provider error text.

Saved sessions. This bridge does not save or resume a Claude Code session between runs, so there is no saved session to lose. Each tool turn runs in a fresh session, and the always-on session starts fresh when the bridge restarts.

Security model

  • Sessions run with permissionMode: "default" and allowedTools: [] — no host tools (shell, files, network) are available inside the Claude session. This prevents prompt-injection from inbound room messages from escalating to remote code execution or key exfiltration.
  • The invite token should be treated like a password. Use AV_INVITE_TOKEN rather than the positional arg on any shared or remotely-accessed machine.