The text content occupies like 20% of the screen, the rest is empty. Resizing the window helps.
As a result I still run sessions and processes I really don’t want to lose inside tmux, nested inside herdr. Tmux never crashes.
Everything works: you get the native view of subagents, you can upload files and images, fork threads, etc.
The massive upside is that the actual work happens on the server so you can close your laptop and it will continue plus it will not fry your thighs. The advantage over sessions (which I haven't tried but theoretically sound) is that you can configure Claude's environment on the server however you like. Give it any tools you need, ssh access to other machines, sudo, whatever.
The only downside is that every new project requires a setup step on the server (to add the systemd service) where you will develop it since Claude can only handle one server per directory. Claude will handle this step however if you give it ssh access to your server.
The machines show up nicely in Claude Desktop/Mobile/Web, and repos/projects are in a dropdown. Unless you work on very many projects at the same time, this setup is golden.
This is the only downside? You expose your servers to Claude infrastructure and their security. You inherently leave a backdoor open to your system.
I can't wrap my year around how far we backtracked on security standards, to the point people just don't even see the obvious.
For me (like for many others) tmux didn’t suit the multi agent workflow. Herdr then was too buggy in my experience.
My own tool, Jai, connects to multiple machines, handles multiple agents and enables agent to agent communication.
For those interested: https://michael.sinax.be/jai/index.html
Still though why would you release and announce this before being ready to share the sources? You're telling people to run a shell script that not only fetches and installs a random, closed-source prebuilt binary, but also runs it automatically after fetching it.
Nobody in their right mind should be running this script or recommending it to anybody.
While I agree with you on the unsafe practices, let’s say this is closed source: what is different then? People download and run closed source apps all the time.
> By hand or from source > To install by hand, download jai-x86_64-unknown-linux-musl (Linux) or jai-aarch64-apple-darwin (macOS) or jai-x86_64-pc-windows-msvc.exe (Windows), check its SHA-256 against latest.json, and put it on your PATH as jai (jai.exe on Windows). You can also build from source with cargo install --path .; those builds don't check for updates.
However I’m not able to find source code anywhere on your github.
No worries if you didn’t open source, only it seems ambiguous currently.
A nice alternative for ppl who struggle with terminal based solutions. It's a free indie product. https://shikigami.dev <--- more info there
there is an ios application in testflight and web client, nothing is on the servers, using tailscale through clients or you can use classic remote hosts.
We should compare notes!
Seems like we all get tailored suits now.
But if you have control over your setup, I would use a capable terminal and ditch in-band multiplexers that sit in the middle of the process and your terminal eating up escape sequences and native features while adding latency. Then use a separate tool for session persistence (I like zmx but there are more for this).
Firstly, I want to sandbox my agents from each other and from my hard-drive, and partition (and encrypt) secrets, so I use (and wrote) byre[0], and run a devbox with long-running agents for certain tasks. TermRover[1] is a pretty good SSH client for tmux. For a more native integration I have started using Happier[2] which provides a web front-end and iOS app for my sessions too (unified with real Claude Code, so handover is seamless), and put together a byre skill[3] to make that easy.
[0]: https://github.com/pjlsergeant/byre-happier-claude
[2]: https://happier.dev/
The tmux send-keys + terminal scrape is the LLM version of the analog hole of DRM'ed audio.