The primary benefit I've gotten over just a straight tmux session is that there is a collapsable left "tab" bar that shows you your different workspaces, which you can relabel, and below that is a list of the agents you are running (claude code, codex, etc) along with their status (idle, blocked, working).
So I will start a workspace for each different thing I'm working on, label it "Studio Shed Packet", "Teapot game", "Mux experiment". Then in each one I run a Claude Code. Then I can see the status of my Claude Codes just by glancing at the sidebar, rather than having to switch between screens to see what is waiting next.
You can rename the tabs in tmux but not sure if there's a way to do dynamic status (I suspect there is but it's probably non trivial to get it to play nice with the harness)
You can do this. In my current tmux session I have four windows each with a status indicator that shows up when that window is running a claude code session. It is a blue animated braille spinner when it is working, a red dot when it needs attention and a green tick when it is finished with its work.
Claude code exposes a bunch of hooks you can use to have tmux commands execute. This is invaluable if you are multi-tasking and need to see at a glance what needs attention.
Was just about to say this. And the application can also try to rename the terminal window title with the OSC 2 escape sequence. Don't think you need more than that. The bell was the general "Something needs your attention" since forever.
Yes but someone else has put in the effort so I don't have to. I could go to the supermarket and buy a bunch of groceries and make food, or I could buy food from a restaurant.
A bit naive, but I'd guess that privacy supporting projects might tend to attract people on the political extreme so you see people are more passionate about this?
The average person who wants (or sells) a car probably doesn't have many strong feels on politics. The average person who goes out of their way to be to buy a specific privacy focused VPN is probably a bit more in tune politically and likely to have stronger feelings.
@geotp Ignore a lot of the mean comments, this is an excellent project and something that I've being meaning to hack together for myself. Having web access to remotely debug I2C/UART is a literal godsend. I cannot wait to just drop in an ESP32 instead of having to connect a rats nest of wires.
That ruthless review prompt seems interesting, would you be willing to share it? I've been trying to have Claude act as a reviewer for me and it feels like it never will disagree.
It's very hard to untangle it from the rest of its context (the prompt is built dynamically, from a lot of parts, some project-specific, some specific to my preferences, some built from interaction history), so I can't really share it. In any case, I don't think it's some specific prompt engineering sorcery I'm doing, it's not like I've spent any real time refining it or experimenting with various magical incantations. It's probably just some model features making it more amenable to the kind of instructions that are relevant in these cases (directness, questioning trade-offs, thoroughness etc.). My chatbot swears equally graphical in review prompts and news summarizing prompts so I'm pretty sure I'm not tickling the machine just right :)
Can you share more information about the undercutting? I've heard of places like Elecrow trying to incentivize people to sell via their platform/OEM service but it sounds like you've had people asking you to license your designs?
I never followed up, but I didn't read it as some serious IP licensing thing. It sounded like they've come to the conclusion that they're making the stuff that's sold on Tindie anyway, so might as well set up a website and ship directly to your customers.
About Sunday/Monday last week right before it went down I noticed the site was supper buggy and failing to add things to cart, I emailed support and got a "we are checking the issue". Since it went down all I've heard from support is "Please be patient. Tindie will be back up soon as we are currently performing maintenance. At this time, we do not have an estimated timeframe to provide."
The fact that it wasn't communicated at all prior and not having a timeframe makes me thing this was probably an ops screw up.
I see this a lot with small independent sites with big userbases. Instead of being honest, they hide mistakes behind maintenance or blame it on hackers.
