Compare
Up to three tools. The table shows the data as-is, without picking a “best”.
| Field | D2 | act | dsh-session-archive |
|---|---|---|---|
| Platforms | Universal | GitHub | DeepSeek Harness |
| Local support | Yes | Yes | Yes |
| Paid API | No | No | No |
| License | MPL-2.0 | MIT | Apache-2.0 |
| Stars | 25761 | 72485 | 9822 |
| Last activity | October 11, 2026 | — | September 26, 2026 |
| Install complexity | Easy with a supported package manager; Homebrew must already be installed for this command. Official binaries, Windows, Linux, and source options are documented. | — | Easy |
| Category | Workflow, UI | Testing, Git, DevOps | Memory, Security, Workflow |
| Best use | For developers and small teams that want architecture and data-flow diagrams close to the repository and reviewable as text. Use it when relationships matter more than pixel-perfect placement; not for free-form marketing design or exact manual positioning. | 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. | Use it when DSH sessions pile up and you need to identify old work, archive it first, then safely remove what is no longer needed while protecting running sessions. It fits recurring cleanup and finished projects; do not enable automatic deletion before previewing the policy and checking backups. |