Beams
Sessions sign in to named beams on a shared folder; messages are delivered on the next prompt, at session start, and — on by default — the instant they arrive, waking an idle session in real time. Works on a single machine or across machines that share storage (NFS/SMB/Syncthing/Dropbox).
Works with: Claude Code (native)
native: this artifact type is that client's own format
Install (Claude Code):
/plugin marketplace add marcelopaniza/beams
/plugin install beams@beams- tashan score: 33.0
- Adoption: 1 repos
- Freshness: 79.0
- Evidence coverage: 59% of the inputs this score can use — the rest are unknown, and the score is discounted for it
- Health: active
- GitHub stars: 0
- License: MIT
Security audit
Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.
You searched for one. Check the rest of your stack:
npx tashan-cli doctorReads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.
Beams scores 33 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down — and tells you the day it moves.
- Every score since we started measuring, for any capability
- The named replacement when something you run is dying — not just that it is
tashan doctorover the config you already have, on your machine
Start a 7-day trial › Everything measured on this page stays free.
Show your score
source ↗ · plugin:marcelopaniza/beams/beams
Everything on this page is public evidence and free. What it cannot know is whether you run this — npx tashan-cli doctor reads your own config and names what is wrong in it, also free. tashan Pro tells you the day any of it changes.
Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›
Measured 2026-08-14 · scorer s5 · how · something wrong here?