Alternatives
Products that do what td – a CLI to manage tasks, sessions, and worktrees for agentic coding does
Hi everyone! I built this because I wanted a little bit more organization around my Claude sessions, worktrees and plans while staying in the terminal and not relying on another SaaS tool. Since it's a command line tool, the added bonus is that Claude can use `td` directly. The td calendar was just a fun add-on but the Claude session stats have been pretty interesting! Let me know what you think!
- 1
- 2
- 3
- 4
- 5
- 6
- 7TC
2018 · github.com
- 8WC
A friend and I built this as a side project to help us collaborate on files with our agents. Claude / Codex kept outputting .md and .html files which are great until we needed to share them, so we built this small website to help with that. Agent can either use an HTTP + Skill or an MCP which also uses MCP Apps to add widgets to Claude Desktop / Mobile chat. Would love any feedback and hopefully this helps someone else as it did us!
Jun 2026 · workplane.co
- 9CC
I built Claude‑CMD, an open-source command-line interface for working with Claude Code commands, configurations, and AI-driven workflows. It’s designed to help developers and PMs streamline how they interact with Claude Code in coding tasks, automation, and prompt management. Website: claudecmd.com Happy to answer questions or hear suggestions. You can also contribute your own commands to help improve the project. Contributions welcome!
2025 · github.com
- 10TC
Agents can run non-interactive commands, but they often fail once a workflow needs a real terminal (SSH sessions, installers, debuggers, REPLs, TUIs). I built term-cli so an agent can drive an interactive terminal session (keystrokes in, output out, wait for prompts). And it comes with agent skill for easy integration. It supports in-band file transfer: the agent can move files through the terminal stream itself (same channel as the interactive session), which is useful when the agent doesn’t have scp/sftp, shared volumes, or direct filesystem access across boundaries. Recent example:…
Mar 2026 · github.com
- 11IB
The main goal of this was to be able to not just run multiple Claude Code sessions at once, but actually manage them and keep track of what I was doing. Sometimes this is multiple attempts on the same task, sometimes I work several tasks at once. Really I was just sick of twiddling my thumbs waiting for the coding agent to finish, and I wanted it to be easy to work on/review/test another change while I waited.
2025 · github.com
- 12TA
Hey HN, I think session transcripts written by coding agents like Claude Code and Codex are very interesting because they offer a detailed window into how work gets shipped. You can see the sequence of decisions that resulted in the final PR, what the agent got wrong, tools used etc. So I built a cli that analyzes these sessions and provides a local dashboard that shows what each session shipped (PRs, features), how much each PR cost, and recommendations for more effective usage. Concretely, it enriches each session with: - Outcome links: merged PRs, features shipped, files changed -…
Jul 2026 · github.com
- 13MA
This weekend I built a multi-agent coding system which, quite unexpectedly, beat Claude Code on Stanford's Terminal Bench! The architecture is straightforward, consisting of an orchestrator agent that deploys explorer & coder subagents to complete complex terminal based tasks, utilising an intelligent context sharing mechanism along the way which makes it all work. The repo has a lot of technical details, and all the code and prompts for you to play around with if you'd like! I had a lot of fun making this, I hope you have fun reading the README, using it yourself, or even extending it! As…
2025 · github.com
- 14PT
I vibe-coded a terminal tool called Pluqqy (I had a dormant domain on hand) to help me keep LLM context organized while coding with AI. It’s my first time writing Go and my first terminal app, built almost entirely with Claude Code. • What it does: Pluqqy lets you manage prompts, rules, and context as small building blocks, then stitch them together into a single file (like AGENT.md or CLAUDE.md) that your coding agent can consume. It’s meant to reduce context drift and make iteration easier. • Why I built it: I was losing track of my agent context between sessions and wanted something…
Oct 2025 · github.com
- 15AS
Hi, this is my first npm package that is getting a couple of hundreds downloads. It's a super simple CLI time tracker, mostly suitable for 9 to 5 jobs I hope you check it out and tell me what you think. Demo and etc. https://github.com/omidfi/moro
2017
- 16
- 17DC
After a year of producing all my code through Claude Code, I was growing frustrated with losing Terminal tabs and not noticing when sessions are ready to continue. I looked around at all the terminal managers people have been building for this type of workflow and couldn't find anything that worked for me. Cmux came close but was too buggy in the area I cared the most about: knowing when my sessions are ready for input. I also felt like the sidebar was too cluttered and hard to parse visually. So, I made my own Claude-first terminal manager and optimized it for the habits I've developed over…
Apr 2026 · github.com
- 18SR
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 19NT
I built a CLI tool that turns codebases and PRs into diagrams so you can quickly understand how things fit together. Originally made it because I couldn't follow my own AI-generated repos. Just shipped a big update: - Switched from D2 to Mermaid for rendering - Tree-sitter AST parsing + agentic flow instead of raw LLM calls. ~50x faster. - Works on any GitHub repo or PR, not just local - Dropped the web frontend, it's just a CLI now - Published as a pip package Still a ton to improve and I'm building fast. Feedback, issues, PRs all welcome.
Feb 2026 · github.com
- 20CC
Uses agent and Git Hooks to automatically create Git Notes on commit, containing the agent conversation that led to that commit. Works if either you or the agent commit. It's basically the same thing as entire.io just announced that they got $60m investment for. Except I got Claude Code to write it last week, in my spare time, without really paying attention. I certainly didn't read or write any of the code, except for one rubbish joke in the README. I've got a Claude Code instance working on Gemini CLI support and OpenCode support currently.
Feb 2026 · github.com
- 21CR
Hey HN, Over the past 10 months I've been using Claude Code heavily, and one limitation kept coming up: you can really only run one coding agent at a time. While one agent is refactoring something, the rest of the repo is basically blocked unless you start manually juggling branches and working directories. The core issue is that AI coding agents operate directly in your filesystem. If two agents run in the same working directory they quickly start stepping on each other’s changes. Git worktrees turned out to be a surprisingly good primitive for solving this. So I built ChatML, a Desktop app…
Mar 2026 · github.com
- 22AW
AdaL is the world’s first local coding agent with web UI. Claude Code has proven that coding agents work best when they are local, bringing developers back to the terminal. Terminal UIs are fast and great with shortcuts, shell mode, and developer-friendly workflows. But they are limited in history and image display, and the experience varies by terminal and OS. Many of them flicker (buuuut not AdaL CLI ). Most importantly, they can be quite intimidating for non-technical users. This led us to explore new possibilities for a coding agent interface. What if you could get the best of both…
Jan 2026 · youtube.com
- 23UA
I've been using LLMs for long discovery and research chats (papers, repos, best practices), then distilling that into phased markdown (build plan + tests), then handing those phases to Codex/Claude to implement and test phase by phase. The annoying part was always the distillation and keeping docs and architecture current, so I built Unpack: a lightweight GitHub template plus docs structure and a few commands that turns conversations into phases/specs and keeps project docs up to date as the agent builds. It can also generate Mintlify-friendly end-user docs. There are other…
Feb 2026 · github.com
- 24KY
Hey HN! I wanted to practice "vibe coding" and see how far and fast I can go by only prompting, without actual coding. I decided to make a simple CLI app that scrapes web docs into a single md file (I was annoyed that LLM keeps writing Tailwind 3 code for a Tailwind 4 project). In just a couple of hours, the CLI app was ready! Then iterated on arguments for another couple of hours. Result: https://github.com/vladstudio/web2llm Then I decided to go further and "productize" the CLI by making a web app for it. Another half-day, and the web app is ready!…
2025 · web2llm.dev
Ranked by how close each launch is in meaning, then by votes. Refine with a description →