warp

A simple solution is to use a git hook that asks for confirmation if it is too big, with a suggestion to ask the user to have the agent split it up. For OSS, my suggestion is to accept issues and specs do the implementation yourself. Warp.dev has a decent model of this in Github: https://github.com/warpdotdev/warp/blob/master/CONTRIBUTING....

Warp engineer here - Warp is open source as well if there's anything we can do to improve the default experience. Otherwise, it's available to fork and customize: https://github.com/warpdotdev/warp

I don't know anything about that (I didn't know what Warp was until yesterday, still kinda don't know, as it seems to be a terminal plus AI and I don't know what that actually means). But, alacritty's license seems to allow proprietary forks. The license requires copyright notice to follow the code and that seems to be present: https://github.com/warpdotdev/warp/blob/6d7a01cc9727472a1bcb... I dunno if they adhered to the license previous to open sourcing, though, as you have to include it somewhere in the actual binary distribution, as well, and some folks don't do that. And, that's also shitty and unethical.

Warp founder here. It's cool to see the community excitement here. Note that we are going to add bring-your-own-model directly into Warp. Would love interested folks to weigh in on the discussion here: https://github.com/warpdotdev/warp/discussions/9619

please https://github.com/warpdotdev/Warp/issues/7182

The AI features are not fully open, and there are some forking attempts to fix that. https://github.com/warpdotdev/warp/issues/9303

For transparency, the issue with telemetry turning back on after an app restart was a very bad bug introduced yesterday that only affected new users; this is P0 for us to fix and we’ll have a new release out in the next few hours with a fix. The PR is here https://github.com/warpdotdev/warp/pull/9438/ if you want to follow along. To add more color to some of your points in the post above: * We give users the option to disable telemetry before sending any back to our servers. * We use Sentry for crash reporting, this can be disabled. * Yes, we record telemetry with the option to disable. The events are in our source code (as you point out) and also on our website. * We have a network log in app that you can open and view _any_ request we make, including requests to send telemetry. * If you compile the OSS build it has no telemetry or crash

From other comments in the thread, login is no longer required so you should be able to just not login on your work machine https://github.com/warpdotdev/warp

> Does it call home? Absolutely, in heaps. The very moment you start Warp, it sends 5 HTTP requests, (1 version check, 1 LLM model list, 3 telemetry events). The former two go to app.warp.dev, the latter 3 go to warpianwzlfqdq.dataplane.rudderstack.com and include a persistent UUID, your operating system and version, Warp version, and the tracked event name and its properties. All of this happens before you even see the window. After you're done clicking 'No' to all the SaaS nags, you can turn off telemetry in the settings, but for some reason it gets turned back on when you restart the terminal. While the terminal is running, it calls home whenever you trip one of the events listed in this 7000-line long file: https://github.com/warpdotdev/warp/blob/d0f045c01bacbd845a63.... Besides all the hosts listed earlier, it also makes requests to