Robotgo vs screenpipe
Side-by-side comparison of two AI agent tools
Short answer
- screenpipe is growing faster: +130 GitHub stars in the last 30 days vs +70 for Robotgo.
- Pick Robotgo for: robotGo, Go Native cross-platform RPA, GUI automation, Auto test and Computer use @vcaesar. Pick screenpipe for: yC (S26) | Open Computer History | Record your screen continuously locally and provide context to your agents.
From GitHub data refreshed daily.
R
Robotgoopen-source
RobotGo, Go Native cross-platform RPA, GUI automation, Auto test and Computer use @vcaesar
s
screenpipeopen-source
YC (S26) | Open Computer History | Record your screen continuously locally and provide context to your agents (Claude, Codex, Openclaw, Hermes, Runner...)
Metrics
| Robotgo | screenpipe | |
|---|---|---|
| Stars | 10.9k | 21.8k |
| Star velocity /mo | 70 | 130 |
| Commits (90d) | 13 | 2.8k |
| Releases (6m) | 5 | 10 |
| Downloads (30d, npm + PyPI) | — | 30.8K |
| Overall score | 0.5102655682083486 | 0.7762751608008367 |
FAQ
- Which is more popular, Robotgo or screenpipe?
- screenpipe has more GitHub stars (21,796 vs 10,860).
- Which is more actively developed, Robotgo or screenpipe?
- screenpipe had more commits in the last 90 days (2,810 vs 13).
- Should I use Robotgo or screenpipe?
- Compare their capabilities, limitations and "best for" notes above. Both are open source, so trying each on a small task is the fastest way to decide.