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 explaining the setup. We’re looking to implement multi-user support in HolyCode.cloud, our hosted project, where we own the web UI and can build the account and permission model ourselves. It isn’t available yet, and we don’t have a release date to share.

HolyClaude currently uses CloudCLI’s single-user interface. Adding separate developer accounts and isolated sessions would require broader changes than we’re planning for this container. I’m closing this discussion here because that work is being considered for HolyCode.cloud, not because the feature has been delivered. For self-hosting today, separate containers with their own credentials and workspaces remain the approach.