HN Showcase
Back to browse
GitHub Repository

Multi-account switching and Slack remote access for Claude Code

22 starsJavaScript

Claude-Nonstop – Auto Account Switching and Slack Remote in Claude Code

by rchaz·Feb 20, 2026·1 point·3 comments
Visit ProjectView on HN

AI Analysis

●●●BangerSolve My ProblemBig BrainShip It

Automatic account failover + Slack remote access for Claude Code, no servers.

Strengths
  • •Solves a real pain: rate limits mid-session now trigger seamless account migration instead of blocking work.
  • •Slack integration is genuinely useful—control Claude remotely, get real-time progress in a dedicated channel.
  • •Zero-infrastructure approach (tmux + Node.js hooks, no servers) makes setup and deployment friction-free.
Weaknesses
  • •macOS-only testing limits immediate utility for Linux-heavy teams; Windows support unclear.
  • •Requires 2+ paid Claude accounts, which is a financial and logistical barrier for most users.
Target Audience

Developers using Claude Code heavily across multiple projects; teams with multiple Claude subscriptions

Similar To

Claude Code CLI · Anthropic Multi-Account Workarounds

Post Description

I run Claude Code across multiple projects daily. Two problems kept getting in the way: being stuck in the terminal waiting for agents to finish, and burning through rate limits midweek while manually switching between accounts.

claude-nonstop fixes both. Every session gets a dedicated Slack channel with completion notifications and near real-time progress updates. When you hit a rate limit, it migrates the session to the next best account and resumes automatically.

Node.js, tmux, Claude Code hooks, Slack Socket Mode. No servers, no public URLs.

Similar Projects