4 ms·
Show HN: Claude-Nonstop – Auto Account Switching and Slack Remote in Claude Code
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.
- kay_o 8mo agoDo you need proxies for this? I was permanently banned immediately after hitting the limit on my first paid account using claude-nonstop. An internal investigation of suspicious signals associated with your account indicates a violation of our Usage Policy. As a result, we have revoked your access to Claude.
- rchaz 8mo agoNo proxies needed. Claude Nonstop runs the official claude binary — it doesn't extract tokens, modify requests, or do anything detectable as different from normal CLI usage. It's the same as manually running claude with a different CLAUDE_CONFIG_DIR, which is how Claude Code's own profile system works. That ban message is the same one Anthropic sends for a range of violations (third-party OAuth tools, VPN/proxy usage, chargebacks, account sharing). If you were using any other tools that access Claude outside the official CLI, that's the more likely cause.
- kay_o 8mo agoClaude support has responded to my appeal such that this was the cause. Automating consumer plans is forbidden by terms of service unless you are paying per token via API. Running claude official CLI with the automation to resume until the 5 hour session resets and immediately continuing is banable. Using multiple accounts to bypass limit in one is covered in this.