Hey! Suggesting Claude Nexus for the list.
What: A self-hosted blueprint for running Claude Code across a fleet of machines from a single browser dashboard. Three pages — Operations (live sub-agent dataflow graph + topology), Browse (full-text search across every Claude session from CLI, VS Code extension, Desktop, and in-browser chat), and Chat (xterm.js + WebSocket SSH proxy to any host with cross-device session resume).
Why it fits this list: It targets the specific pain of running Claude Code on more than one machine at a time. Sub-second JSONL-to-UI sync via watchdog/inotify, 4-layer duplicate-open guard for cross-device resume, real-time graph of Task-spawned sub-agents with per-node token usage. Repo is intentionally documentation + recipes + minimal skeletons (not turnkey app), so readers vibe-code their own version that fits their fleet topology.
Stats:
- 6 deep-dive recipes + 4 runnable skeletons
- Full README in English + 繁體中文
- Tested on a Proxmox + 8 Ubuntu/Windows/Pi VM homelab
- MIT licensed, no SaaS, no telemetry, no per-seat licensing
Suggested entry (Agents & Orchestration or Workflows section):
- [Claude Nexus](https://github.com/henryopen/claude-nexus) - Self-hosted control plane for running Claude Code across a fleet of machines. Real-time sub-agent dataflow graph, cross-device session resume, full-text search across every Claude client. Documentation-first blueprint.
Author: Henry (@henryopen)
Hey! Suggesting Claude Nexus for the list.
What: A self-hosted blueprint for running Claude Code across a fleet of machines from a single browser dashboard. Three pages — Operations (live sub-agent dataflow graph + topology), Browse (full-text search across every Claude session from CLI, VS Code extension, Desktop, and in-browser chat), and Chat (xterm.js + WebSocket SSH proxy to any host with cross-device session resume).
Why it fits this list: It targets the specific pain of running Claude Code on more than one machine at a time. Sub-second JSONL-to-UI sync via watchdog/inotify, 4-layer duplicate-open guard for cross-device resume, real-time graph of
Task-spawned sub-agents with per-node token usage. Repo is intentionally documentation + recipes + minimal skeletons (not turnkey app), so readers vibe-code their own version that fits their fleet topology.Stats:
Suggested entry (Agents & Orchestration or Workflows section):
Author: Henry (@henryopen)