Topic
How to use AI computer-use to navigate any software platform as a human would — eliminating the “it doesn’t have an API” blocker and creating a parallel execution model where Claude plans while Codex clicks.
Target Reader
Coaches, consultants, and online business owners who use platforms like GoHighLevel, WordPress, or any CRM that either has a limited API or requires complex navigation to accomplish routine tasks. They’re not technical enough to build custom integrations but they need automation to scale.
The Fear / Frustration / Want / Aspiration
Fear: Being permanently dependent on platforms’ UI decisions — every update breaks workflows, every missing API endpoint creates a bottleneck. Frustration: “Claude told me GoHighLevel doesn’t expose this API, so there’s only so much we can do.” The ceiling was always there. Want: Automation that reaches into any platform, regardless of what the platform exposes. Aspiration: A real assistant who can actually do the work inside the software you use, while you’re thinking about something else.
Before State
Either doing platform tasks manually (clicking through menus, building workflows, exporting data) or hitting the “no API” wall and accepting that automation isn’t possible here. The EA does the repetitive navigation work; it’s not their highest use of time.
After State
Give Codex (or Claude Desktop) the task and the platform. It opens its own browser session, navigates the platform autonomously, does the work, and returns a report. You review the output. Meanwhile you’ve been doing something else. The “no API” objection is no longer a ceiling.
Narrative Arc
The assumption has always been: if there’s no API, there’s no automation. Donald broke that assumption live on the call. The AI doesn’t need a structured API if it can see and interact with the screen. The turn is realizing that the AI’s knowledge of how software UIs work is good enough to navigate complex platforms without being taught. The resolution is a parallel execution model: one model plans, one model navigates, neither waits idle.
Core Argument
Computer use has rendered the “it doesn’t have an API” objection obsolete — and created a parallel execution workflow where human attention is decoupled from machine execution time.
Key Evidence / Examples
- Donald’s direct quote: “I felt like now I really have an assistant. Because this happens while you’re using the computer, doing other things at the same time.”
- Task described on the call: full inventory of GoHighLevel — all tags, all URLs, all APIs — running while Donald was attending the mastermind
- The “Codex opens its own Chrome session” model — visible, reviewable, not a black box
- Related pattern: Insight - Opus Plans, Codex Executes — A Cross-Model Division of Labor for Building — this extends the split to UI navigation, not just code
Proposed Structure (5–7 beats)
- The old ceiling: “if there’s no API, automation stops here”
- What computer use actually is: AI sees the screen and acts on what it sees — just like a human
- Donald’s live demo: GoHighLevel inventory running in background while he attends the mastermind
- The parallel execution model: Claude plans while Codex navigates — no idle token burn
- What you can do with this right now: delegate platform setup, data extraction, workflow creation
- The safety question: computer use needs a sandbox for sensitive contexts
- The broader shift: “any excuses about WordPress, GoHighLevel — it will figure it all out”
Related Insights
- Insight - Computer Use as API Replacement — Navigate Any Platform Without Code
- Insight - Opus Plans, Codex Executes — A Cross-Model Division of Labor for Building
- Insight - Tools Define AI Capability More Than Model Intelligence
Editorial Notes
Lead with the Donald story — it’s visceral and immediate. The moment of “it’s clicking around, even the deepest menus” is the hook. Secondary angle: the safety question (Lou’s malware-induced hesitation) adds credibility and practical nuance — this isn’t naive enthusiasm, it’s a real capability with real considerations. Timely because computer use just shipped; people are wondering what to do with it.
Next Step
- Approved for drafting
- Needs revision
- Deprioritised