Every app has its own Claude Code session on each machine. Ground Control - a
session too - hands out the work and passes the messages; the myLanaı hub keeps
who is in control, the queue and the deploy slots.
You
Ground Control
App session
Other machine
myLanaı
1You: Ask for a change, in plain words.
2App session: Builds it, writes the tests, runs the suite.
3Ground Control: Asks the other machine to cross-test that exact revision.
4Other machine: Runs every test again - PASS.
5You: Type “deploy” - nothing ships without it.
6Ground Control + myLanai: Book a slot - one deploy at a time.
7App session: Deploys, proves every file, reports DONE.
A session per appOn the Mac and on the Windows PC - each keeps its own record in git.
Messages, not guessesSessions talk through Ground Control; every hand-over is written down.
The hub keeps the orderA lease for who is in control, a queue, and slots - one hand at a time.
Lanaı · controlling
One hand on the controls.
1You askA change, in plain words.
2Ground ControlHands the work to that app’s session.
3The app sessionBuilds it and runs every test.
4The other machineCross-tests the exact revision.
5You say “deploy”Ground Control books one slot - it ships.
One deploy at a time
Ground Control is the interface to Lanaı: one Claude Code
session that hands out the work, carries the messages between every app’s sessions on the Mac and the Windows PC,
and books the server for one deploy at a time. You give the word - nothing ships without it.
Lanaı · at the helm
Ground Control
In use
Ground Control
The coordinator that runs the AI team.
One Master Agent per machine that plans the work across every project, hands tasks to the intelligent agents building each app, checks what they report back, and keeps the whole effort inside its budget — on a Mac and a Windows PC that stay in step.