IM.codes vs Paseo vs Warp
Up to four tools, row by row. We do not guess: a cell we have not checked says so.
How they differ
Paraphrased from each maker’s own description. Select a line for the quote.
- · also Paseo
- · also Warp
- · also IM.codes
- · also Paseo
Checked for Paseo and Warp, not yet for IM.codes: Price (Paseo: ; Warp: )
Checked for Warp, not yet for IM.codes and Paseo: Model providers (, , , SpaceXSI (Grok)), Bring your own key ()
Checked for IM.codes and Paseo, not yet for Warp: Agents it runs (IM.codes: , , , , , ; Paseo: , , )
Checked for IM.codes, not yet for Paseo and Warp: Editors and systems (, , )
Same for all 3 (3): Parallel agents · Agent teams · Review & diffs
- Parallel agents · ·
- Agent teams · ·
- Review & diffs · ·
Provider names use the same listing as each tool page. Dotted values open their quote. A capability not shown is not yet checked; the tool may still have it.
About these tools
Paseo
Warp
At a glance
Index score out of 100
Mindshare HN mentions, 90 days
Adoption GitHub stars, not scored
Release days last 90 days
Lowest monthly plan billed monthly, lower is cheaper
Platforms listed surfaces
Votes can only raise a score: up to 20% of it reflects upvotes, graded on a curve against the most-voted tool. The square-root curve has a floor of 100 effective votes. Votes decay with a 90-day half-life. Maker self-votes do not count. Counts below 10 are hidden for display only. After activation, the score is 80% mindshare plus 20% of the greater of mindshare and the vote score. GitHub stars do not affect the Index score. Mindshare uses a log scale; votes use the square-root curve and a 100-vote floor. Ranks use unrounded scores. Mindshare and adoption bars are log-scaled; the others are linear within this comparison. How the score is built


- Free appfree
Watch IM.codes vs Paseo vs Warp on YouTube
More comparisons
Build your own



























