65+ terminals. Customer brings the brain.

ParviDefenders · ParviRange · Chefe 2665 · 21 Aug 2026

Ideia central

I never meant two windows. I said two doors (how a brain arrives). The swarm is 65+ terminals at once: a parent wave in a window, children waves in more windows, in parallel, fast. For us (the house), our LLM-Hub is fine. For ParviDefenders and ParviRange, we must ask the customer first: their own hub with several AIs, or one AI as the brain those agents run with to build tools. We do not silently plug our house hub into their machine.

House uses our LLM-Hub. Customer Defenders or Range must name their hub or one AI before Core opens the 65+ parent-and-child terminals.

Our house

FriendlyAI labus
Our LLM-Hubseveral AIs — OK for us
ParviClaw Coreopens the terminals

Customer — Defenders or Range

Install asks firstrequired. No silent house hub.
Their LLM-Hub (several AIs)orOne AI as the brain
Same Coreparent window → child windows
65+ live terminalsnot 2

O que foi entregue

  1. The mix-up — “two doors” = (1) a program in the window, (2) ask a model. Not two terminals.
  2. The swarm you described — parent wave in a terminal, spawn children waves in more terminals, all at once. That is the design. It should work at 65+.
  3. Your rule, recorded — house hub for us. Defenders / Range: customer names their hub or one brain before any wave.
  4. What the engine can do today (honest, not the sales story yet):
    Today in the engineWhat you just set
    Live terminals at oncedefault 64 (65th waits unless we raise it)65+ must work
    Children from one parentdefault 8parent keeps spawning children until the job is done, inside the 65+
    Paid “pro” license50 terminals — that would block 65+too low for this promise
    Brain on a customer installstill points at a hub URL; house is the defaultmust ask them first

65+ is the working number. 64 in the engine is one short. I did not shrink your swarm to two windows.

O que mudou no meio do caminho

Nothing invented. Your 2662 question was “who is coding.” This message is the product rule for whose brain and how many windows. Same Core. Two products (Defenders, Range) may not ride our house hub.

O que falta

Only you — two yes/no for the next build:

  1. Raise the engine so 65+ live terminals work out of the box (today 64; paid pro is 50 and would block you).
  2. Defenders / Range install: refuse to start waves until the customer names their hub (several AIs) or one AI as the brain. House keeps our hub.

If both are yes, that is the next change. No extra product. No Code-Hub as the pane brain.