Show HN: Tmux-IDE, OSS agent-first terminal IDE (tmux.thijsverreck.com)
Small OSS project that i created for myself and want to share with the community. It's a declarative, scriptable, terminal-based IDE focussed on agentic engineering.
That's a lot of jargon, but essentially its a multi-agent IDE that you start in your terminal.
Why is that relevant? Thanks to tmux and SSH, it means that you have a really simple and efficient way to create your own always-on coding setup.
Boot into your IDE through ssh, give a prompt to claude and close off your machine. In tmux-ide claude will keep working.
The tool is intentionally really lightweight, because I think the power should come from the harnesses that you are working with.
I'm hoping to share this with the community and get feedback and suggestions to shape this project! I think that "remote work" is directionally correct, because we can now have extremely long-running coding tasks. But I also think we should be able to control and orchstrate that experience according to what we need.
The project is 100% open-source, and i hope to shape it together with others who like to work in this way too!
Github: https://github.com/wavyrai/tmux-ide Docs: https://tmux.thijsverreck.com/docs
31 comments
[ 3.1 ms ] story [ 53.3 ms ] threadI am burning a lot of tokens every day at work and on personal projects. It's helpful. I generally work in tmux with github copilot in one pane, and a few other terminal panes showing tests and current diff.
I find it really important to avoid the temptation to multi-task by running multiple agents. For quite varied tasks, productivity gains from multi-tasking have proven to be illusory. Why would it be different with writing software?
https://en.wikipedia.org/wiki/Human_multitasking
It supports tmux, but you can use it without via embedded terminal. It also has native integration with a few select terminals that expose the right kind of APIs.
Installs as single binary (written in Go) with no external dependencies.
tmux is powerful, but not exactly approachable, and "multi-agent orchestration" on top of it feels like something that could get hard to reason about quickly. Curious how you think about UX here.
From my perspective, this is cool, but since tmux is kind of permanent, you open your layout, set 1,2,3 screens for agents, you might add gemini and opencode. then open vite for server and one for shell for example. Then you can just close it and reopen whenever you want to work on it.
And that is it. If I am missing something, processes taking memory or such, I have a machine with memory (I know, flexing how expensive things are), please explain.