paperclip: hire ops and deploy agents (opencode_local) #64

New issue

Open

opened 2026-10-25 12:06:21 +00:00 by lab · 0 comments

lab commented

2026-10-25 12:06:21 +00:00

Owner

Context

Wire the two agents into a Paperclip company. Paperclip spawns
opencode run itself; it does not talk to the server on ct253.

Steps

Create one company with a goal covering the homelab repos.
Agent ops
- adapter opencode_local, model from opencode models on ct254
- cwd: /srv/paperclip/work/homelab
- env.KUBECONFIG: /srv/paperclip/.kube/ops-config
- instructionsFilePath: /srv/paperclip/work/homelab/lxc/paperclip/agents/ops.md
- Forgejo token: read + PR review only, stored as a Paperclip secret ref
Agent deploy
- same adapter, separate cwd (own clone to avoid lock contention)
- env.KUBECONFIG: /srv/paperclip/.kube/deploy-config
- instructionsFilePath: /srv/paperclip/work/homelab/lxc/paperclip/agents/deploy.md
- Forgejo token: code read/write, secret ref
Write both instruction files. They should carry the repo's rules: IaC
changes via PR, no direct kubectl apply, one service per folder, always
reference the cluster skills.
Set heartbeat concurrency to 1 in the instance settings.

Done when

both agents run one heartbeat against the repo and leave a comment
ps aux during a run shows opencode run ... --model <id>
the run's env carries the right KUBECONFIG

## Context Wire the two agents into a Paperclip company. Paperclip spawns `opencode run` itself; it does not talk to the server on `ct253`. ## Steps 1. Create one company with a goal covering the homelab repos. 2. Agent `ops` - adapter `opencode_local`, model from `opencode models` on ct254 - `cwd`: `/srv/paperclip/work/homelab` - `env.KUBECONFIG`: `/srv/paperclip/.kube/ops-config` - `instructionsFilePath`: `/srv/paperclip/work/homelab/lxc/paperclip/agents/ops.md` - Forgejo token: read + PR review only, stored as a Paperclip secret ref 3. Agent `deploy` - same adapter, separate `cwd` (own clone to avoid lock contention) - `env.KUBECONFIG`: `/srv/paperclip/.kube/deploy-config` - `instructionsFilePath`: `/srv/paperclip/work/homelab/lxc/paperclip/agents/deploy.md` - Forgejo token: code read/write, secret ref 4. Write both instruction files. They should carry the repo's rules: IaC changes via PR, no direct `kubectl apply`, one service per folder, always reference the cluster skills. 5. Set heartbeat concurrency to 1 in the instance settings. ## Done when - both agents run one heartbeat against the repo and leave a comment - `ps aux` during a run shows `opencode run ... --model <id>` - the run's env carries the right `KUBECONFIG`