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

This might be useful (maybe) to the author: I am in a group (probably small, but I don’t think negligeble) that gave up on Warp because it doesn’t support standard or custom command completions [0] Some lesson must surely be drawn from this about incremental adoption. [0] https://github.com/warpdotdev/Warp/issues/1811

Actually not really. I spent at least an hour trying to get OpenCode to use a local model and then found a graveyard of PRs begging for Ollama support or even the ability to simply add an OpenAI endpoint in the GUI. I guess the maintainers simply don't care. Tried adding it to the backend config and it kept overwriting/deleting my config. Got frustrated and deleted it. Sorry but not sorry, I shouldn't need another cloud subscription to use your app. Claude code you can sort of get to work with a bunch of hacks, but it involves setting up a proxy and also isn't supported natively and the tool calling is somewhat messed up. Warp seemed promising, until I found out the founders would rather alienate their core demographic despite ~900 votes on the GH issue to allow local models https://github.com/warpdotdev/Warp/issues/4339. So I deleted the

Classic AI hype update! Fine they are basically doing their own interface language on toolsets that we already have access to, and maybe that particular design language will fit the sweet spot for some folks. Does it add anything actually new...not really, maybe keeping your hands on the keyboard more, meh. Meanwhile a real user accessibility issue of not allowing font size changes to the embedded UI elements has dozens of requests for them to fix since 2022 has never been touched. Maybe they can get their AI agent to fix their own platform for them. Since it is a closed source platform that as far as I can tell, since there is no option to use your own AI API keys sends all your AI content through their own servers. Ref: Support changing font size/type for UI text (tabs, settings, command palette, resource center, etc.) #1443 https:/

https://github.com/warpdotdev/Warp https://www.warp.dev/blog/how-warp-works Warp terminal – no more login required (49 days ago) https://news.ycombinator.com/item?id=42247583 Show HN Warp.dev (3 years ago) https://news.ycombinator.com/item?id=30921231 Show HN llmterm https://news.ycombinator.com/item?id=42498901 https://github.com/timschmidt/llmterm

Note: it does seem at least some development happens in the open https://github.com/warpdotdev/Warp > We are planning to first open-source our Rust UI framework, and then parts and potentially all of our client codebase. The server portion of Warp will remain closed-source for now. https://github.com/warpdotdev/Warp/discussions/400 None of the server bits will be open, ever, but some of the UI code will be? Better than nothing.