Has anybody been doing anything fun with Claude Code plus Maslow?
Wes wrote:
Has anybody been doing anything fun with Claude Code plus Maslow?
not that has been reported. We have copilot tied in to github so that it
attempts to solve issues that are posted. It has worked pretty well
David Lang
Here is a video with an overview of how that process works:
1 Like
Yes, its about 85% complete. I just need time to finish it.
1 Like
Awesome. I will check into this soon.
1 Like
Quick progress update on the Claude Code experiment.
The biggest milestone today: Claude Code drove a full firmware downgrade end-to-end. The v1.15 → v1.20 upgrade I did earlier had broken Apply Tension on my machine (full writeup in [25745]). Today I had Claude Code:
- Inventory what was on the controller — partition layout, files in littlefs, network state, settings dump
- Back up the live maslow.yaml, config-bak.yaml, preferences.json, and index.html.gz over HTTP before touching anything
- OTA-flash the v1.15 firmware bin via POST /updatefw
- Diagnose a soft-brick after the flash (turned out: power-cycle once, comes right back)
- Restore the matching v1.15-era maslow.yaml (a v1.20 yaml on v1.15 firmware was the second issue I had to clear)
- Run Retract/Extend/Apply Tension and read the live measurement log to confirm we were back to “Ready to Cut”
- Review the gcode for my next cut before I pressed play
After all that, I just ran two cuts back-to-back from the same template file — both came out perfect. First clean cuts on the rebuild.
Made some more progress. Now I have Claude automatically grabbing the newest toolpath in my downloads folder that I export from Krabscam. It analyzes it for potential issues based on the current context and what I’ve been doing. It sends it to the Maslow and automatically starts cutting.First attempt went perfectly. Fingers crossed it continues to work. I’ll keep you posted.