Repository navigation
Home
DockerCatAgent is a self-hosted Claude Code terminal environment with persistent home/workspace and optional SSH, vault and MCP access. The foundation source is on main following PR #1, but there is no published release, registry image or production approval.
These navigation pages are maintained as reviewed source in the repository and published separately under the synchronization procedure. The repository guides remain canonical, and validation evidence separates implemented features from pending account and host acceptance.
- Read Getting Started for requirements, full-context installation, authentication and a first session.
- Review Architecture and Security before granting filesystem or account access.
- Choose Remote Operation and Integrations only if those optional features are needed.
- Use Maintenance and Recovery for updates, volume safety, logs and troubleshooting.
| Section | Topics |
|---|---|
| Getting Started | Introduction, requirements, installation, login, first Claude session, image updates |
| Architecture | Image, Compose overlays, persistent volumes, runtime identities, filesystem/network boundaries, authentication lifecycle |
| Remote Operation | SSH keys/host identity, localhost/VPN, tmux observation, mobile clients, callbacks, connection failures |
| Integrations | Obsidian mount/write risks, Mem/headless OAuth, tool/account scopes, personal instructions, future MCP recipes |
| Maintenance | Rebuild/update, state, draft backup/restore, resource limits, diagnostics, upgrade/recovery |
| Development | Source layout, build, CI/tests, local acceptance, contribution, security reports, decisions |
| Security | Threat model, credentials, privileges, disclosure and residual risk |
| Roadmap | Milestones, dependencies, foundation gates, exploratory work and non-goals |
A successful version check or CI build does not validate a real Claude/Mem account, ARM64 hardware, Portainer deployment, remote mobile client or recovery of credentials. Use the acceptance matrix, GitHub issues and the merged foundation PR #1 for implementation history and the remaining acceptance scope.
No license has been selected. Owners must approve licensing and any later release/distribution. See contributing and private security reporting.
Procedures live in the reviewed canonical repository guides. Wiki pages provide navigation and do not add runtime capabilities. Security reporting · Roadmap