My Homelab AI Dev Platform
Points and comments are a snapshot, not live.
A homelabber uses OpenCode Web UI with Git access for AI-assisted Docker compose management and GitOps deployments.
The author set up OpenCode Web UI as a persistent server on a VM, giving it its own Git user with SSH keys that can push branches but not directly to deploy. The workflow: OpenCode writes changes, author reviews and merges PRs, GitOps (Arcane) deploys. OpenCode has no access to actual services to limit blast radius. It connects to hosted models (Codex, DeepSeek, Kimi) and a local Gemma 4 12B via vibeproxy. The author uses this for container updates and healthchecks, but notes missing CI feedback because Forgejo Actions does not expose job logs through the public API.
What commenters are saying
Many commenters share similar AI-assisted homelab setups using tools like n8n, Forgejo action runners, and Kimaki. There is a side debate on whether using hosted models qualifies as a homelab; the author notes OpenCode can connect to any model. Several users discuss Forgejo API limitations and workarounds such as the tea CLI. One commenter points out the phenomenon of independent coincident discovery. Overall the thread is collaborative and technical.