AI ToolsKR

I Wanted Claude Code Running 24/7 on a Server — So I Built VibeCheck

Close your laptop, Claude Code dies. VibeCheck runs it headlessly on your server so you can access from any browser, anywhere. MIT open source.

I Wanted Claude Code Running 24/7 on a Server — So I Built VibeCheck

I Wanted Claude Code Running 24/7 on a Server — So I Built VibeCheck

Close your laptop, Claude Code session dies. Anthropic's Remote Control is the same — it's a local process.

"Put it on a server, access from my phone, keep it running even when the laptop is off."

That one sentence is why I built VibeCheck. It's open source (MIT).

Why I Built It

I tried Anthropic's Remote Control. Being able to see a Claude session from your phone is nice, but close the laptop and the session dies. If WiFi drops for more than 10 minutes, it times out. And you only get one session.

It's called "Remote" Control, but your computer has to stay on.

Anthropic also offers a cloud option (claude --remote), but it can't use your local environment — no local MCP servers, no environment variables, no local DB. It clones your GitHub repo and works from there, which doesn't fit projects that depend on local setup.

Remote ControlClaude on the WebVibeCheck
Runs onYour computerAnthropic cloudYour server
Laptop can sleepNoYesYes
Local files/MCPAvailableNot availableAvailable
Parallel sessions1 onlyMultipleMultiple
Access viaclaude.ai/appclaude.aiAny browser

There was no option that kept the local environment while letting you close the laptop. So I built one.

🔒

Sign in to continue reading

Create a free account to access the full content.

Related Posts