Multi-user support: separate authenticated logins for several devs on one instance

[valentin-converteo]

Use case

We run HolyClaude on a shared VPS and want several developers to each work on the same projects, each in their own session — not two humans in one session, just concurrent independent sessions on a shared codebase.

Today HolyClaude is single-user by design: one system user (claude), one connected Anthropic account, and the CloudCLI web UI on :3001 has no login/authentication layer — anyone who can reach the port has full access.

Current workaround

Running one container per person (different ports, separate ~/.claude and workspace volumes) + a shared git remote works, but there's no single authenticated entry point, and access control relies entirely on the network layer (Tailscale / reverse proxy).

Requested feature

Some form of native multi-user support, e.g.:

• Multiple named logins on the web UI, each mapped to its own session / Anthropic credentials
• Or first-class documentation + tooling for a multi-container "team" setup behind one authenticated gateway

Why it matters

Keeps rate limits, billing and audit separated per developer, while letting a team share one VPS and the same projects. Thanks for the great project! 🙏

[CoderLuii]

Thanks for writing this up properly, the workaround section especially.

Straight answer: HolyClaude is single-user by design today and I'm not going to pretend otherwise. There's no auth layer on :3001 at all, so the network layer is doing all of the access control, exactly as you describe.

The reason that's awkward to fix here: the web UI on :3001 is CloudCLI, which I ship rather than own. Multi-user login means an auth layer inside the UI, and doing that in HolyClaude means either forking someone else's project and maintaining that fork forever, or upstreaming a feature its maintainers may not want. Neither is a small call.

The hosted version (HolyCode Cloud) runs a UI I did write, with SSO already in front of every box, so auth is mine to change. That's why team support is planned there first. It's on the roadmap rather than in progress, and I'd rather say that than imply it's shipping next month.

What the hosted version gives you today: each developer gets their own machine with an authenticated login in front of it, so per-person auth, rate limits and billing are already separate without you running a gateway.

What it doesn't give you is the thing you actually asked for. One box per person plus a shared git remote is the same shape as your current workaround, just without the VPS to maintain. Several humans on one instance sharing a filesystem isn't there in either product yet.

If it's useful to try: https://app.holycode.cloud/billing?code=TRY3DAYS — 3 days free, card taken at checkout but not charged, cancel before it ends and you're not billed.

I've written this up in the roadmap either way. And if you get an authenticated gateway working in front of multiple containers, I'd genuinely take a PR documenting it.