Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | act | Superpowers | dsh-chrome |
|---|---|---|---|
| Platforms | GitHub | Claude Code, Codex, Cursor, OpenCode | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MIT | MIT | MIT |
| Stars | 72437 | 304147 | 9 |
| Last activity | — | — | — |
| Install complexity | — | — | متوسط / Moderate |
| Category | Testing, Git, DevOps | Code Review, Multi-Agent, Testing, Workflow | Browser Automation, Security |
| Best use | Best for a developer or small team that repeatedly edits GitHub Actions workflows and wants to test a job before pushing. It provides a local run log, while a final GitHub check remains necessary. It is not suitable when exact hosted-runner parity is required. | Best for a developer or project owner working on a substantial feature or a difficult bug. It helps clarify requirements, approve a plan, and inspect tests and file changes. Its value is a visible path from decision to verification. A small text edit may not need the full workflow. | Best for a developer debugging a local or test web UI who wants a DSH agent to see the page and network evidence in the same session. It reduces manual copying and supports interactive inspection after an explicit request. Avoid it for sensitive production accounts or if broad browser permissions are unacceptable. |