Self-hosted · 14 Sep 2026 · CoS

Agent farm on four studio PCs

Escape Cursor usage caps by standing up a local agent farm. CopilotKit OpenBot is the company shell — talk to every agent from your phone. Eng ships PRs; VR Designer runs Blender by CLI; clients still come in via WhatsApp/Telegram. Paperclip is deferred. No public Docker or SSH.

OpenBot is HQ on your phone; World is what the team builds; Eng ships PRs; VR Designer runs Blender by CLI and sends you cool finds; you approve merges and taste.
For Zaydaan Mahomed Owner Chief of Staff Status 0 machines registered

Context

Why we’re doing this

Pain → fix. Same table as the plan SoT, tightened for the phone.

Cursor / cloud coding caps block Eng + Marketing

Fix Local farm + API coding models on your PCs

Need multi-role team (Eng, Marketing, VR)

Fix Named OpenBot agents with isolated computers

Need phone access + see what agents are doing

Fix OpenBot teammate UI over Tailscale; watch / take-wheel

Client bugs via WA/TG → Eng → PR → you

Fix OpenClaw/Hermes ingress → Eng bot (no unsupervised prod)

Want World/Quest as the immersive face

Fix Product track; later diegetic agent status in VR

Look like Eng/VR/Blender Twitter without lab spend

Fix Cheap digests + local craft tools; frontier only on hard 10%

Decisions locked

The stack — stop flipping

Company shell is OpenBot. Messaging ingress is OpenClaw. World is the product. Paperclip waits.

OpenBot HQ Eng Marketing VR Designer OpenClaw Paperclip deferred

Topology

Network diagram

Phone and laptop reach OpenBot over Tailscale. Client WhatsApp/Telegram hit OpenClaw, then Eng. Workers sit on PC-1/2/3.

Scroll horizontally on narrow screens · amber = day-one path

Hardware

Four PCs · roles

~16GB RAM each, ≥1TB storage, gaming GPUs for Blender/Unity local work.

PC-0

Orchestrator

Docker Compose OpenBot + supervisor; Tailscale; locked down (Docker socket).

MVP
PC-1

Eng worker

OpenHands/Aider, git, gh, repo sandboxes → PRs only. You merge.

MVP
PC-2

Marketing

CapCut VectCutAPI + FFmpeg chops. Day 2–3; skip Higgsfield v1.

PC-3

VR Designer

Blender CLI, Unity Quest path; Twitter/X/YouTube VR inspo digests.

MVP start: PC-0 + PC-1 first, then add PC-3 VR, then PC-2 Marketing.

People (bots)

Agent responsibilities

Eng PC-1

  • Repo access, branches, PRs via OpenHands/Aider + gh
  • Triggered by client tickets (OpenClaw), @mentions, CI failures
  • Notify you when PR is ready — you merge / deploy
  • No auto-merge to Production day one

Marketing PC-2

  • After Eng shell is alive
  • VectCutAPI self-host + FFmpeg; skip Higgsfield v1
  • Content library → drafts → Postiz (channels later)
  • World inspo board remains product work

VR Designer PC-3

  • Blender via headless CLI + Python (blender --background … --python)
  • Digests Twitter/X / YouTube VR / Blender → “3 cool things + why”
  • Helps Eng ship Consolider World + Quest assets
  • Lookdev / taste stays with you

OpenClaw / Hermes Ingress

  • Client WhatsApp / Telegram / later SMS → structured ticket → Eng
  • Optional auto-reply later; day one = notify you first

Chief of Staff This chat

  • Orchestrates plan, spend discipline, remote install/ops with your approvals
  • Once PCs are registered in Grok Bot — installs OpenBot remotely

Spend

Cost control + model routing

OpenBot + four PCs ≈ $0 software/hardware marginal. The bill is API tokens. Keep output high, bill low.

Soft cap day one: ~$5–10 / day total — raise deliberately

Do

  • Cheap models for triage, digests, tweet skims
  • Mid models for small PRs / Blender glue
  • Frontier only for hard architecture / nasty bugs
  • Batch VR inspo (1–2 digests/day)
  • Hard per-bot / daily $ caps + ping at limit
  • Local Blender / Unity / FFmpeg / VectCut on GPUs
  • One primary Eng API provider

Don’t

  • Frontier models for “summarize 20 tweets”
  • Always-on agents with nothing to do
  • Stack Cursor on-demand and OpenHands on same work
  • Live Twitter doomscroll loops
  • Unbounded “keep retrying until it works”
  • Pay APIs for work your PCs already do
  • Three overlapping coding bills
JobTier
WA triage, digests, inspo skim Cheap Flash / mini / Haiku-class
PR review, small fixes, script glue Mid
Hard Eng / Unity / WebXR Frontier escalate
Image/video gen v1 Skip VectCut + FFmpeg

Execution

Phase roadmap 0 → 6

Phase 0 blocks everything. Register PC-0 first.

Your one-time prep

Pick PC-0 (always-on-ish, Docker-capable). Install Grok Bot desktop. Enable Local execution. Register under Computers. Leave the app running; message CoS: “PC-0 is ready.” Optional now: Tailscale on PC-0 + phone.

0 machines registered — not done yet

OpenBot MVP (PC-0 + phone)

  1. CoS installs Docker, clones tagged OpenBot, Compose up
  2. Auth + model API keys with spend caps
  3. Create bots: Eng, VR Designer (Marketing stub OK)
  4. Verify phone UI over Tailscale

Eng coding loop (PC-1)

  1. Register PC-1; install OpenHands/Aider + gh
  2. Wire Eng bot → PC-1 runner
  3. Test: fake ticket → branch → PR → you merge

VR Designer (PC-3)

  1. Register PC-3; Blender (+ Unity for Quest)
  2. Headless scripts + daily inspo digest skill
  3. First real World/Quest asset tasks

Ingress + Marketing

OpenClaw/Hermes WA/TG → Eng tickets. PC-2 VectCut + FFmpeg; Marketing bot live. Postiz linking when Marketing resumes.

World as ops mirror

Agent status APIs into Consolider World. Diegetic “Eng working / PR ready.” Quest parity where it matters.

Only if needed

Revisit Paperclip for queues / spend governance. Raise daily API caps after a week of real usage data.

Definition of done

Success criteria

  • Phone HQ — message Eng + VR from phone via OpenBot on Tailscale
  • Eng loop — ticket → PR link in chat; no prod push without you
  • Cost — under daily cap; digests on cheap models
  • VR craft — headless Blender lands a glTF/cleanup without GUI
  • Inspo — short “3 cool things” digest without a frontier bill
  • Safety — no public Docker/SSH; merges gated

Out of scope

Explicit non-goals (day one)

Unsupervised Production deploys 70B local coding models on 16GB Higgsfield / heavy AI video v1 OpenBot as product UI (World stays) Public LAN / internet SSH All four PCs before PC-0 + PC-1

Hard rules

Security & access

No public exposure

Do not port-forward SSH, Docker socket, or OpenBot to the open internet.

Grok Bot local exec

Register each PC → Computers + Local execution; leave app running; approve commands.

Tailscale mesh

Private mesh between the four PCs + your phone. Never the public internet as the front door.

PC-0 locked down

Supervisor needs Docker socket → dedicated, trusted machine. Secrets encrypted in OpenBot admin.

Pin tagged releases

OpenBot is early — expect sharp edges. Prefer self-host Intelligence; pin a tagged release.

Names

Glossary

Names we kept mixing — keep this straight.

CopilotKit OpenBot
Self-hosted coworker platform (AG-UI, per-bot computer). This is the HQ.
OpenClaw
Messaging ingress (WhatsApp/Telegram) — not the company OS. Formerly confused with “OpenBot.”
Paperclip
Company/org job router — deferred until OpenBot proves weak on queues / spend caps.
Hermes
Agent/coding runtime family — Eng uses OpenHands/Aider practically.
Consolider World
Your 3D/VR CRM product (world.lutho.app). Product track; later diegetic agent mirror.

Immediate next action

Your next step

Register PC-0. Then CoS installs OpenBot.

1
You — register PC-0

Install Grok Bot → Local execution on → Computers → leave app running → reply “PC-0 is ready.”

2
CoS — installs OpenBot

Docker + tagged OpenBot + Eng/VR bots + spend caps; then register PC-1 for the coding loop.