been ordering from REWE for years =) always wished the app was less annoying. all my programm skills - for what? lol. probs for reverse engineering the mTLS part, most people would have just given up.
how stable this is in practice? Internal APIs tend to break without warning when they update the app.
> Claude code hooks are blocking - performance degrades rapidly if you have a lot of plugins that use hooks
can confirm. ended up being really careful about what runs synchronously vs in the background.
IMHO the "sanitised optimism" thing others mention here is real too. had to add explicit verification steps because Claude kept reporting success when it just silenced the error. now I always make it prove things actually worked before moving on.
I setup the initial project to get claude started in a structure I like and there are some shared libs that I had written before AI lol
The constraints were built up over time as we did the project; claude.md also got pruned several times to move things around so it references other files as claude finds it needs that information
yea, I am looking into how I can maybe fine tune a model for a more data-oriented world view
Cool) I'm doing something similar atm for iOS simulators instead of macOS / same idea though, giving Claude direct access through MCP instead of going through computer use. The latency difference is huge when you skip the screenshot-parse-click loop.
tell me more about you handle tool discovery... With macOS scripting there could be a ton of possible actions. I ended up with 49 and already feel like thats a lot for the context window.
how stable this is in practice? Internal APIs tend to break without warning when they update the app.
reply