claude-containers
Self-hosted Docker container for running isolated, long-lived Claude Code sessions on a homelab box. One container per session, reachable via SSH or the Claude mobile app's Remote Control feature.
Ficha actualizada 22 sept 2026, 23:53 · upstream 22 sept 2026, 23:50 · release sin release detectada
Qué es claude-containers
Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.
This repository provides a self-contained Docker image that hosts multiple isolated, long-running Claude Code sessions simultaneously. Each session runs in its own container, making them completely independent and safe to run concurrently without interference. The architecture supports two primary access methods: SSH into a persistent tmux session for programmatic control, or the Claude mobile app's Remote Control feature for a graphical interface.
The system is designed for homelab environments where developers need multiple concurrent development sessions with full isolation. Each container mounts its own git repository as the workspace, allowing different projects to be developed simultaneously without file conflicts. The architecture separates authentication credentials from session configuration, enabling shared login tokens across containers while maintaining per-session state persistence.
Key design decisions include a pinned CLI version to prevent accidental token-based billing, an unattended autopilot mode for continuous-build workflows, and event-driven SCM observability through GitHub webhooks. The system also supports OpenTelemetry integration for cost tracking and Langfuse tracing, making it suitable for production-grade development workloads.
- Running multiple concurrent development sessions on a single homelab server
- Automated CI/CD pipelines triggered by git events without manual intervention
- Secure remote access to private repositories via SSH with persistent tmux sessions
- Cross-platform development workflow where mobile app and terminal commands run in parallel
- Continuous integration testing that requires multiple isolated environments per project
- Monitoring and debugging concurrent application deployments across different branches
- Each container is completely isolated with its own git workspace, preventing cross-contamination between projects
- SSH access allows direct programmatic control via tmux sessions without needing the mobile app
- The autopilot mode enables continuous-build workflows by consuming queued prompts from disk rather than a clock timer
- OpenTelemetry integration provides per-call cost and token usage tracking for subscription management
- Shared authentication credentials across containers while maintaining per-session state persistence in config volumes
- Requires Docker to be installed on the host machine, which may not be present on all homelab setups
- The autopilot mode requires a valid GitHub remote configured with proper permissions for webhook events
- Per-container git repositories are mounted at runtime and must be cleaned up manually or via cleanup scripts after use
- No built-in container orchestration (e.g., Kubernetes) is provided; manual scaling requires external tools like Docker Compose or Ansible
- The system relies on the user's GitHub account for authentication, meaning it cannot run in a completely isolated environment without credentials
Perfil de infraestructura
Estimación inicial derivada del repositorio y de los servicios detectados.
Despliegue detectado
Qué señales reales de instalación hemos encontrado.
To deploy this container, build the image with `make build` and authenticate via `make login`. For each project, launch with `./bin/claude-launch <project> --repo <git-url>` to start an interactive session. To run in autopilot mode, set environment variables like `CLAUDE_AUTOPILOT=1 CLAUDE_AUTOPILOT_CMD='/build-command'` and mount the git repository as a volume. For fleet management across multiple projects, use Docker Compose with separate volumes for each project's workspace and auth data. Always verify that your GitHub webhook configuration allows the container to write to `done/` and `failed/` directories before enabling autopilot queues.
Stack y dependencias
Componentes inferidos a partir de manifests, configuración y documentación.
Puede sustituir a
Relaciones detectadas por el análisis del repositorio y su categoría.
Experiencia real de la comunidad
Ayuda a contrastar la estimación automática con instalaciones reales.
Todavía no hay datos comunitarios para este proyecto.