Warp is now open-source

Original Article ↗ Hacker News Discussion ↗

Warp, a Rust-based terminal that has pivoted into an “agentic development environment,” has been open-sourced, prompting both enthusiasm and skepticism. Many welcome the chance to retain its polished terminal UX without being locked into proprietary AI features, while others question the VC-backed company’s motives, pointing to past login requirements, extensive telemetry, and a perceived shift toward monetizing LLM-based agents. The conversation also contrasts Warp with other terminals and AI coding tools, with some users hoping the new license enables community forks that strip out AI, tracking, and bloat.

Business model and open-source move

  • Many see open-sourcing as driven by business survival and competition, not altruism.
  • Several speculate funding and AI compute costs are pressuring Warp to shift work and innovation to the community.
  • Others view the blog’s framing (“open-sourcing to build a successful business, agent/orchestrator is the real product”) as refreshingly candid and strategically sensible.

Terminal vs. AI/agent focus

  • Early users recall Warp as a novel Rust terminal with REPL-like UX, rich input, and collaboration features, predating the LLM hype.
  • Current positioning emphasizes an “agentic development environment”; some are confused whether Warp is a terminal, an agent harness, or both.
  • Stated competitors are agentic AI tools (Claude Code, Cursor, Codex, GitHub experiments), not classic terminals like Ghostty.
  • Some think integrating agent harness + terminal is overkill; others find integrated workflows appealing.

Privacy, telemetry, and trust

  • A major thread criticizes that Warp “calls home” extensively: version checks, LLM model lists, telemetry/event logging, and Sentry crash reports, with a persistent UUID.
  • One commenter notes telemetry can be disabled but was re-enabled on restart due to a bug; Warp staff acknowledge this and link to a fix, emphasizing options to disable telemetry/crash reporting, an in-app network log, and that OSS builds have none.
  • Several argue that any unsolicited network activity from a terminal is unacceptable, and that previous login requirements and heavy telemetry damaged trust.

User experience: positives and negatives

  • Fans highlight:
    • Strong default UX: multiline editing with familiar shortcuts, separate input/output blocks, rich autocomplete, “visual” terminal behavior.
    • Good rendering performance and polish out of the box.
  • Critics cite:
    • Bloat and constant AI/agent prompts compared to lightweight terminals.
    • Need to repeatedly disable new AI features after updates.
    • Large app size (~850 MB) and occasional bugs (e.g., black window, AI account auto-disabling).

Desire for non-AI / forked versions

  • Multiple users want a lightweight, no-AI, no-login, no-telemetry Warp—essentially “just a good terminal.”
  • Some explicitly hope the open-source release enables forks that rip out AI/cloud/monetization and perhaps rewind to earlier, simpler designs.

Comparisons and alternatives

  • Ghostty, Alacritty, libghostty-based projects, tmux/zellij integrations, and other agent harnesses (Claude Code, OpenCode, etc.) are frequently mentioned.
  • Opinions differ on stability and usability vs. Ghostty; some find Warp more usable, others prefer Ghostty’s minimalism.

Naming and nostalgia

  • Several older users initially mistook the title as referring to open-sourcing OS/2 Warp, leading to mild disappointment and jokes about name reuse.