Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

A suite of productivity tools for Claude Code, Codex CLI and similar CLI agents. These solve pain points for me, and I build and share them in the repo[1].

I’ll highlight a couple:

- an “aichat” command group that enables continuing work from a session that is at full context usage, by creating a new session and injecting session lineage pointers so the agent/sub-agent can recover arbitrary full details from ancestor sessions. So no more compacting needed.

- aichat search command: TUI for rust/tantivy-powered full text search across Claude and Codex sessions. CLI/json mode for agents to search for past work.

- Tmux-cli tool + skill to enable CLI agents to interact with scripts (including other agents) running in other Tmux panes. Like Playwright for the terminal. Multiple CLI agents can collaborate/consult etc. Agent can run and interact with interactive CLI scripts.

[1] https://github.com/pchalasani/claude-code-tools





This is interesting. I wrote a “memory indexer” with the idea to provide a tool (cli) for my agent to “remember” past conversations we had in other session. A little bit in the spirit of your second tool I think

I’ll take a look at the others you have.


The thought behind my aichat tool was to directly leverage the session log files and avoid creating any special memory artifacts. I do create a rust/tantivy index for the fast full text search.

The aichat approach does require intentionally asking the agent to find specific earlier work: it doesn’t automatically have “awareness” of prior work. I think of this as the “unknown unknowns” problem. This is where creating explicit memory artifacts can be useful since we can pre-inject recent work-summaries into context. So I’m thinking about a lightweight hook based system to automatically create memory artifacts or work-logs of some sort.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: