Thanks for the suggestion! CLI tools can be simple to deploy and setup but are limited in the long run. Running the logic server side allows us to perform way m

Thanks for the suggestion! CLI tools can be simple to deploy and setup but are limited in the long run. Running the logic server side allows us to perform way more validation, such as GitHub Actions, linting, and pre-commit hooks. You can do this in your terminal, but it's not as easily parallelized and the process is not as easily persisted. There are definitely some tradeoffs to be made. Also, the onboarding flow for GitHub Apps is significantly smoother and is a familiar interface for many people. We built a CLI-installed tool previously and there were a ton of versioning and environment-related problems etc, with 3 OS's to support. Unfortunately, it becomes harder to focus on building the best tool for our users if our focus is too broad. To your last point, you can pry into our codebase and our blogs to see what we do under the hood; "Watch the magic happen" is just referring to the simplicity of our installation process. Also, we only store the logs for debugging and they only get persisted 30 days (which is also how long OpenAI stores them for). We gave a lot of thought to designing our search engine that doesn't store any code in plaintext. Check it out here: https://docs.sweep.dev/blogs/search-infra https://docs.sweep.dev/blogs/search-infra