Optimized OpenClaw Development Workflow
My new favorite way to work with OpenClaw: 1. Tell it we're working on app improvements, it should just take notes 2. Run through user flows, send screenshots with notes as I find issues 3. It builds a list of work, adds its own hypotheses 4.
@nateliason shared their OpenClaw setup on X.
My new favorite way to work with OpenClaw: 1. Tell it we're working on app improvements, it should just take notes 2. Run through user flows, send screenshots with notes as I find issues 3. It builds a list of work, adds its own hypotheses 4. Writes up a full report on what to do 5. I say "Go" and it kicks off Codex agents to attack the different pieces, opening separate PRs 6. Claude reviews & improves the PRs on Github 7. Claw makes a doc of everything we did + what to test 8. Next time I test, I start with that list to make sure everything worked
Setup
Requires an always-on machine (Mac Mini, Hetzner VPS, etc.) running OpenClaw with a Claude API key. Integration with the mentioned services via their respective APIs or CLI tools.
Requirements
- OpenClaw or Clawdbot
- Always-on machine (Mac Mini, VPS, etc.)
- Claude API Key