01 / Decide what your command center should know
Start with three questions you regularly ask about your work: what changed, what needs attention, and what should happen next. Connect only the data needed to answer those questions. Revenue, traffic, leads, projects, and content can each be separate modules rather than one giant integration.
Every panel should identify whether it is showing live data, demo data, stale data, or an error. A polished number without provenance is worse than an honest “not connected” state.
- Observe: collect a small set of trusted metrics.
- Ask: answer questions from those metrics and cite the source.
- Propose: recommend one bounded next action with reasoning.
- Approve: show the exact action before anything external happens.
- Learn: record the decision and outcome for the next review.
02 / Choose the prompt or the working code
The prompt below helps Codex or Claude Code build an original command center around your own tools. It starts with a short interview, keeps credentials server-side, and makes external actions propose-only until you approve them.
If you would rather begin with Keith’s working Orbit Mission Control code, join the free Keith AI community. The code and supporting AI resources are available inside the community so you can start from a real implementation instead of an empty folder.
Download the Mission Control code
Join Keith AI free, then use the community’s code and setup resources to build your version.
Join Keith AI on Skool03 / Keep the first version private and reversible
Run the first version locally or behind authentication. Use read-only API keys wherever possible, keep every secret on the server, and make demo data visually unmistakable. Do not expose a single-user dashboard to the public internet without an authentication and deployment review.
Voice is optional. A clear typed assistant with trustworthy answers is more valuable than speech layered over unreliable data. Add task execution only after the read-only experience works, and require a human approval record for every external action.
- Never send service keys, database credentials, or SSH keys to the browser.
- Do not let an AI call arbitrary shell commands or arbitrary URLs.
- Make retries idempotent so a timeout cannot create duplicate posts, emails, or payments.
- Keep an audit log of proposals, approvals, results, and failures.
- Use an original product name and visual design; “JARVIS-style” describes the interaction idea, not an affiliation.
Get the exact prompt.
Make it your own.
You’ve seen how it works. Unlock the copyable prompt and the remaining steps to try it yourself.
- Copy the build prompt
- Prove one honest workflow
New here? Create a free account