OpenCode is already hireable — expand More

Hey {{firstName}},

Two things operators keep asking about landed cleanly this week on the community side — and the stable core cut from early September is still the one you should be on if you self-host.

OpenCode is not a waitlist item. It is a built-in local adapter today. Onboarding still ranks Claude Code and Codex first (product ranking, tracked in #4158) — so expand More Agent Adapter Types, pick OpenCode, set a real provider/model from opencode models, hit Test → Passed, then give it one cheap heartbeat. Multi-provider catalogs and OpenAI-compatible gateways are the natural fit; Paperclip stays the control plane (secrets, budgets, heartbeats).

If you have not taken v2026.831.x yet: company skills finally reach every agent run (deterministic manifest + MCP list + Enable for agents), Kimi Code is first-class, onboarding dropped the mission step, and 831.1 unsticks first-run org creation so Continue no longer soft-loops duplicate orgs. Node.js 24.11+ is the floor for source/Docker — check before you pull.

Shipped

• OpenCode on Paperclip: hire the multi-provider adapter — four-check path, published this week
• Paperclip v2026.831.1 — onboarding org-step fix (in-place on 831.0)
• Paperclip v2026.831.0 — skills at runtime · Kimi Code · settings surface control · sandbox bridge · Node 24

This week’s move: prove opencode models on the host that runs Paperclip, hire one OpenCode agent from More, green Test, one heartbeat. Self-hosters: Node ≥ 24.11 → 831.1, then enable one company skill and confirm the run instructions show the manifest. Building hardware-adjacent agents? Try the CAD listing.

Quiet forum week — no new threads to spotlight. Ship something useful? Reply — next issue picks it up.

Cheers,

Aron 📎