Workspace
One current folder. New, Open, Browse. Every live Bot and every linked IDE works in this folder only.
Coming soon
Agent Control
The missing arm between a phone chat and the tools on your PC. Grok Bot stays the manager. Agent Control is the house: one current folder, linked IDEs (integrated development environments), a live terminal on Build, and a ping when the work is done.
Each install is a house. The plane listens on that computer only — 127.0.0.1, not the public internet. There is no hosted submit URL and no stadium server. The PC must be on.
Live capture
Pair with agentctl pair, set a workspace, then submit a job. The plane listens on 127.0.0.1 only. Closing the window does not start a new plane. Finish text is five blocks: did, analyzed, sits, next, problems. The Bot that sent the work gets PROGRESS, then FINISHED, then a confirm.
The loop
Phone to desk to done
01
Install Agent Control on the PC that has your IDEs.
02
Link Grok Bot as the manager. Link the IDEs you already own.
03
From the phone, say what to do. The house runs it on the open folder.
04
When the turn finishes, the bot that sent the work is told.
Build
Live house terminal. Type here. Grok Build jobs attach to this same session.
Jobs
Idle, working, done, blocked. Submit returns accepted at once.
Channel
Hand-offs between live managers and the desk.
Plan
This ask only. An older auto-plan drops when a new job starts.
Handoff
Did, analyzed, sits, next, problems. Notes at the bottom are yours.
Managers
Each paired Grok Bot and how this house wakes that same chat.
Backends
Scan, Connect, or Skip each IDE already on the PC.
Memory
Spec for the current ask, constraints, decisions. Past jobs are marked not this assignment.
A house, not a host
Wake local IDEs from Grok Bot. The PC must be on. This is not a Linear clone, not a Slack clone, and not a multiplayer cloud. It is the missing arm between a manager chat and the tools already on the desk.
Coming soonContact