Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All practitioners. Leaders and teams have 2 accounts; GILD prints their sentiment from 20.
Engineering leaders and teams
6 sources. These accounts focus on team rollout, shared rules and Warp Drive, admin controls, usage cost, and what changes when Warp moves from one engineer to a team.
Individual builders
69 sources. These accounts focus on the terminal itself, the agent's results, cost per month, and whether Warp hosts or replaces the other agents each builder runs.
All practitioners
75 sources. This gives the broadest market read, but combines work settings that can produce materially different conclusions.
75 sources from practitioners, by the context they work in. Filled rows count for this group.
- Individual practitionerSolo developers and independent builders69 sources, counted here
Emphasizes The terminal, command help, and whether the agent finishes the task
- Very small team2 to 10 engineers2 sources, counted here
Emphasizes Version-control support and scheduled cloud agents
- Professional team11 to 50 engineers, or a named company's team1 sources, counted here
Emphasizes Merged work and cost per change
- Technical leadershipLeaders setting adoption across teams3 sources, counted here
Emphasizes Admin controls and whether engineers keep using it
- Organization-wideEnterprise or company-wide rolloutNo sources from this setting yet
What changes with scale. Nearly every public account describes one engineer's own use: they judge Warp first as a terminal, then on whether its agent or the agents they run inside it finish the work. The six team and organization accounts concern Perforce support, failed cloud agent runs, Thoughtworks' wait for the product to stabilize, Every's parallel Claude Code agents inside Warp, Espressif's embedded debugging with Warp's agent, and remote editing over SSH at a company starting its rollout; no public account covers a finished team rollout.