The problem with zsh, as with a lot of open source tools is bad defaults. If only zsh had a better out of the box experience then OMZ wouldn't be needed. I used maintain a lot of configs, over 10 years I just keep forgetting what did I set up. I don't want to be bothered with this anymore.
that's one of the reasons why we open-sourced everything, we don't store the code, and you can verify that :)
we're just running claude code on your codebase in an ephemeral container, only thing we save is your generated plan
Yeah, it should work for clis, even now. For larger codebases we just need to get two things right:
- create good plans with the adequate tradeoffs for the type of service
- make sure to have enough lints and tests to verify the completion end to end, either with browser, or with typechecking or like for c++ - complex static analysis.
We're constantly iterating on setup instructions and our repository analyzer, and during the integration we have a set of linters to prevent the model to generate completely broken code - it checks types, compiler errors for starters.
The scope of the integration is explicitly limited, we make sure that the model doesn't do extra stuff.
reply