KingCoding
Run Claude, Codex in parallel from one dashboard
111 followers
Run Claude, Codex in parallel from one dashboard
111 followers
A desktop app to run Claude Code, Codex tasks in parallel. Register your projects, dispatch tasks to any AI agent, and monitor everything from one dashboard. AI auto-reviews results and captures verification screenshots. King Mode lets you describe a goal and the AI plans, executes, and adapts automatically. Built by a solo dev who got tired of losing track of AI agents across terminal tabs. Your job: set direction, grant permissions, receive results. 🚀
This is the 2nd launch from KingCoding. View more
KingCoding
Launched this week
A Mac app to run Claude Code and Codex on your desk — drive them from your phone or a second PC. Dispatch tasks, review progress, approve work from anywhere, all synced to one session. No more git-pulling between machines. King Mode turns a goal into a full plan and ships it, auto-reviewing with verification screenshots. Built by a solo dev tired of losing AI agents across terminal tabs. Your job: set direction, grant permissions, receive results. 🚀
Free Options
Launch Team
PocketCorder
@iritec_jp Love this "death by terminal tabs” is painfully relatable 😅
Also really like the idea of having a control layer rather than just more tools, that feels like where things are heading.
I have actually launched today as well (Global Sponsor Hub, completely different space, international hiring), so I know how intense this day is!
Just checked yours out, really interesting concept
Congrats on the launch, Shingo.
"Built using itself" is always a good sign. If it couldn't survive its own development process, that would be telling.
The terminal tab problem is real, and the Discord integration for remote approval is a genuinely practical solution rather than a gimmick.
My skepticism is around King Mode:
"AI creates a plan, executes, and adapts if something goes wrong" is where most autonomous coding pipelines quietly go off the rails on anything non-trivial.
What does "adapts" actually mean when it hits a real blocker? Does it stop and ask, or keep going?
PocketCorder
@ryanwmcc1 Thanks — right question to push on.
Short version: King Mode doesn't try to be clever about blockers. It stops and asks.
What matters more than "adapts" is what happens before execution: at project start, King Mode confirms purpose, target, and non-goals with you, then builds the plan against that fixed spec. Most pipelines derail because they're executing against a vague ask — we front-load that. PM behavior is also configurable per project (non-goals, decision principles, approval policy), so the "decide myself vs. ask" line shifts per context.
Then "adapts" means: fixes its own mistakes, re-plans on scope drift, and on real blockers (ambiguous spec, a call only you can make, same error repeating) it stops, summarizes what's stuck, and pings you on Discord if wired up. It also tracks questions already asked so it can't retry the same dead end.
Where it's weak: judging "blocker vs. solvable hiccup" is an LLM call and not perfect. We bias toward asking and tune from there.