Leaderboard / #5 of 13 / Installed or launched
Paseo
Phone-first users who want a daemon on their machine.
Weighted feature assessment74.5range 57.0 to 92.0doc coverage 65% / Launchedmeasured: Launch probe
Scores by category
Rubric breakdown
- AAgent breadthweight 154
- BIsolation and parallelismweight 15n/r
- CReview, merge and PR flowweight 15n/r
- DRemote, cloud and mobile reachweight 105
- EOpenness and licenseweight 105
- FMaturity and momentumweight 154
- GLinux setup friction (measured)weight 104
- HPricing and BYO modelweight 55
- IDocs and transparencyweight 5n/r
Verdict
Strengths and weaknesses
Strengths
- Pair a device, import sessions you started in a terminal, schedules
- Apache-2.0, light-ish at 852 MB
Weaknesses
- Isolation and review model not verified
Evidence
What we saw and where it came from
- Hands-on (this box)
- Launched on Linux (4.7 s, 852 MB); no account wall.
- Launch probe
- First window 4.65 s, process-tree RSS 852 MB on Xvfb.
- Known issues
- 1.4k open issues+PRs.
- Notes
- Schedules feature visible in UI.

Sources
Feature facts
From docs, repos and our probes
- Platforms
- macOS, Windows, Linux (AppImage/deb/rpm/tar), mobile + web (README)
- Supported agents
- Claude Code, Codex, Copilot, OpenCode, Pi, Antigravity, Muse Code
- Parallelism
- Workspaces per project (details not verified)
- Isolation
- unknown
- Review, merge, PR
- unknown
- Remote, cloud, mobile
- Daemon + 'Pair device' to phone; import sessions started in a terminal
- MCP
- unknown
- Cost visibility
- unknown
- Model choice
- Via providers
- Setup
- Install app; add project; setup providers
"unknown" means we found no source and did not guess.