Security News
The Hidden Blast Radius of the Axios Compromise
The Axios compromise shows how time-dependent dependency resolution makes exposure harder to detect and contain.
By Ahmad Nassri - Apr 01, 2026
New Research: Supply Chain Attack on Axios Pulls Malicious Dependency from npm.Details → →
VibePulse
A tiny dashboard that sits in your browser tab — tired of switching IDE tabs just to check which OpenCode sessions finished.
What It Does
- Kanban board — Auto-discovers OpenCode sessions, organizes them into Idle / Busy / Review / Done
- Remote Nodes — Connect multiple VibePulse instances to a single hub for a unified view
- Audio alerts — Makes a sound when sessions complete or need attention
- Zero setup — No manual card creation; auto-scans ports and processes
- Profile switcher — Flip between OMO presets without touching config files
Quick Start
Hub Mode (Default)
Run VibePulse locally to monitor your local OpenCode sessions and manage remote nodes.
npx vibepulse
Node Mode
Run VibePulse on a remote server to expose its OpenCode sessions to a hub.
npx vibepulse --serve
Node mode requires an access token for security. See Architecture for details.
Features
| Feature | Description |
|---|---|
| Hub & Node | Distributed architecture for monitoring multiple remote hosts |
| Real-time sync | SSE + polling for live session updates |
| Sticky states | 25s sticky window prevents status flickering |
| Offline snapshot | Shows last known state when a node is unreachable |
| IDE integration | Click to open workspace in VSCode / Antigravity |
| Config UI | Manage agent models and remote nodes through the interface |
Architecture
VibePulse uses a Hub-and-Node architecture to aggregate OpenCode sessions across different machines.
- Node: A VibePulse instance running with
--serve. It interacts directly with the local OpenCode SDK and exposes an API. - Hub: The primary VibePulse instance (default mode). It connects to one or more Nodes to collect session data.
Connecting a Remote Node
- Start the remote node:
VIBEPULSE_NODE_TOKEN=your-secret npx vibepulse --serve - Open your local VibePulse Hub.
- Click the Host Manager icon.
- Click Add Remote Node.
- Enter the Node URL (e.g.,
http://remote-server:3456) and the Access Token.
Development
git clone https://github.com/ChatTreeNet/VibePulse.git
cd VibePulse
npm install
npm run dev
Tech Stack
- Next.js (App Router) + TypeScript
- Tailwind CSS + @dnd-kit
- TanStack Query + @opencode-ai/sdk
License
MIT
FAQs
Real-time dashboard for monitoring and managing OpenCode sessions
We found that vibepulse demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Package last updated on 28 Mar 2026
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Related posts
Research
Supply Chain Attack on Axios Pulls Malicious Dependency from npm
A supply chain attack on Axios introduced a malicious dependency, plain-crypto-js@4.2.1, published minutes earlier and absent from the project’s GitHub releases.
By Socket Research Team - Mar 31, 2026
Research
TeamPCP Compromises Telnyx Python SDK to Deliver Credential-Stealing Malware
Malicious versions of the Telnyx Python SDK on PyPI delivered credential-stealing malware via a multi-stage supply chain attack.
By Socket Research Team - Mar 27, 2026