Devotd Github
NewCoding agents

sanagnos/taskman v0.1.26 — Per-ticket agent sessions in one screen

sanagnos/taskman is a Rust tool that gathers per-ticket Claude Code or Codex sessions, issues, and pull requests into a single terminal screen.

Repositorysanagnos/taskman ↗

sanagnos/taskman is a Rust tool that gathers per-ticket Claude Code or Codex sessions, issues, and pull requests into a single terminal screen.

GitHub description: One window for all your parallel Claude work: every ticket's session, issue and PR in one place

stars
★ 4
Forks
0
Language
Rust
License
Apache-2.0
Latest release
v0.1.26
Read original source ↗View on GitHub ↗

sanagnos/taskman is a Rust repository that manages coding agent sessions for several work tickets in one terminal screen. The latest release recorded in the repository is v0.1.26. The provided information lists nothing new or changed in this version, so there is no need to separate the release itself from its changes. The README describes attaching a separate worktree to each ticket and running the Claude Code or Codex command line inside it.

A worktree is a directory that lets work on different tickets proceed side by side within the same repository. taskman shows the related issues and pull requests next to each work session, and the sidebar lets you check sessions that are waiting for a user decision or permission. The README states that a session can be resumed even after it has ended. It is therefore a tool focused on moving between the agent work of several tickets while watching status and discussion together. The license is Apache-2.0.

However, the provided information contains no changelog for v0.1.26 and no performance comparison data. The repository description and the README reveal the direction of the features, but it is not possible to judge what this release improved over the previous version. The recorded star count is 4, and the project was posted on Hacker News. With only this information it is hard to evaluate usability, stability, and adoption cases, so for now it is more reasonable to treat it as an early-stage tool to look at when asking whether it fits a working style that manages several tickets on one screen.