Claude AI Used to Set Up Proxmox Home Server via SSH
A developer documented using Claude AI over SSH to fully configure a Proxmox VE 9.1 home server running on an Intel i7-6700K with 64GB RAM. The AI handled the entire setup conversationally in one session.
Storage Configuration
Claude performed storage cleanup by identifying and removing stale NFS mount points and orphaned Proxmox storage entries (vm_disks, vm_disks_boot, vmdisk1). It formatted three NTFS drives (2x 4TB HDDs + 1x 1TB SSD) as ext4, adding them to Proxmox storage with proper fstab entries using UUIDs. The AI installed parted when needed and converted the two 4TB HDDs into a ZFS mirror pool called photos_store using disk-by-id paths, later renaming it from "tank" to "photos_store" via export/import.
Security Hardening
Claude conducted a security audit finding 67 pending security updates, which it applied including a kernel upgrade from 6.17.4 to 6.17.9. It flagged disabled firewall, SSH root login with password, and lack of fail2ban. The AI installed and configured fail2ban with two jails: sshd (bans after 3 failed attempts for 1 hour) and proxmox (protects web UI login). It also addressed a CPU vulnerability (gather_data_sampling) by updating Intel microcode, though this was limited by Skylake hardware constraints.
Docker and Immich Deployment
First attempt installed Docker directly on the Proxmox host with ZFS-backed storage datasets for Immich (separate datasets for uploads, database, model-cache with optimized recordsizes). Permission issues arose with the vectorchord Postgres image requiring privileged: true and API worker getting EACCES on node spawn due to Docker's security profile. After realizing this setup was invisible to Proxmox UI, Claude removed Docker from the host, created an Ubuntu Server 24.04 VM (4 CPU, 16GB RAM, 64GB disk on SSD), set up NFS to share the ZFS pool, installed Docker in the VM, and deployed Immich successfully with all four containers healthy.
Fan Control
To address server noise, Claude installed lm-sensors and fancontrol, found the NCT6793D chip blocked by ACPI, added acpi_enforce_resources=lax kernel parameter, dealt with boot issues, and set all 6 motherboard fan channels to 30%. Discovering the AMD Vega 64 GPU fan was the primary noise source, it set GPU fan to ~16% (1011 RPM) from 100% (4700 RPM), creating a systemd service to persist settings across reboots.
📖 Read the full source: r/ClaudeAI
👀 See Also
Claude AI Diagnoses Zigbee Network Issue, Recommends Switching from deCONZ to Zigbee2MQTT
A user reported that Claude AI identified a deCONZ issue where switching scenes triggered over 80 ZCL-attribute read commands that overwhelmed a Conbee 2 adapter. Claude recommended migrating to Zigbee2MQTT, which resolved years of unreliable lighting behavior.
Building Persistent Memory for Claude with Four Markdown Files
A developer built a system to overcome Claude's session-based context limitation using four markdown files loaded via project context: Protocol, CONVERGEHERE, Daily Capture, and Continuity. The system maintains context across sessions by having Claude read all files at boot and update Continuity and CONVERGEHERE at session close.
Lessons from Running 14 AI Agents in Production: Organizational Gaps, Not Technical Bugs
A digital marketing agency running 14 AI agents for daily operations found that when agents break, the problem is almost never the agent itself but the organizational environment. They developed an Organizational Operating System (OOS) and a tool called OTP to identify structural gaps, improving their Coordination Score from 68 to 91 out of 100.
OpenClaw on AWS Lightsail: Cost Breakdown and Configuration Lessons
A developer spent $100 in a week running OpenClaw on AWS Lightsail with Claude Sonnet 4.6 via Bedrock, discovering that sandbox settings, token management, and prompt size significantly impact functionality and costs.