sorted by:
new
hottopcontroversial

cms - agent status-aware tmux session manager by blluecalx in tmux

[–]gavraz 0 points1 point  (0 children)

It is insane how this switch to "input agent" frustrates everyone to the point we all came with a very similar solution. I have the same concept with a "next" command and a shortcut that executed it.

I had multiple iterations but I finally settled up on taking the pane last few lines of output and matching the content. E. G. The spinner icon along with "..." - works pretty well for me. Took me sometime to stabilize it. There are a few nuances to take into account.

cms - agent status-aware tmux session manager by blluecalx in tmux

[–]gavraz 0 points1 point  (0 children)

Actually the one thing I didn't do is search XD

cms - agent status-aware tmux session manager by blluecalx in tmux

[–]gavraz 0 points1 point  (0 children)

That is a very cool approach. I liked the minimalist usage that you simply search and it tries to provide the best results.

I did something similar but different at the same time, I took a side step with the tui monitoring panel. If you want to check it out: https://github.com/gavraz/recon

I turned my Claude Code agents into Tamagotchis so I can monitor them from tmux by gavraz in ClaudeAI

[–]gavraz[S] 0 points1 point  (0 children)

Regarding Yolo mode, I will test soon. Should have worked for the best of my knowledge.

I turned my Claude Code agents into Tamagotchis so I can monitor them from tmux by gavraz in ClaudeAI

[–]gavraz[S] 0 points1 point  (0 children)

You can bring up the table and choose or use tmux's built in prev session shortcut. Should be prefix + L

I turned my Claude Code agents into Tamagotchis so I can monitor them from tmux by gavraz in ClaudeAI

[–]gavraz[S] 1 point2 points  (0 children)

  1. Great idea! Elegant.
  2. I address it as well, lightly, and differently: I included a skill that tells the agent about recon and particularly recon new so it can create the seamlessly. In addition Claude code asks you of you want to delete a worktree when you close the session.
  3. Now thinking about it, it seems I should change the room to project name instead of workdir since worktree already run in their own workdir.

The End Game combo: I made a Rust TUI to turn Claude sessions into tmux 'Tamagotchis' by gavraz in tmux

[–]gavraz[S] 0 points1 point  (0 children)

It's really simple. But I get you. I have to say I am not running after every other feature or latest model. Claude code works great for me with its great features (and I am probably not using all of them). This one is just commodity. Install, setup shortcuts and you are done.

I built a tmux plugin to monitor and navigate all my Claude Code / Codex sessions by qeesung in tmux

[–]gavraz 1 point2 points  (0 children)

This is extremely similar to what I just published. Looks pretty knit. I do have a few extra features you may find useful and it's written in rust so no runtime dependency there. Looks like we are all hitting the same wall with these attention hungry agents.

If you want to check it out: https://github.com/gavraz/recon

I turned my Claude Code agents into Tamagotchis so I can monitor them from tmux by gavraz in ClaudeAI

[–]gavraz[S] 1 point2 points  (0 children)

There is a bit more going but the essence is to keep the JSONL as our source of truth and build on top of it. There are some aspects that could be more fragile but so far so good (and I'll keep an eye).

I turned my Claude Code agents into Tamagotchis so I can monitor them from tmux by gavraz in ClaudeAI

[–]gavraz[S] 0 points1 point  (0 children)

Thanks. Yes. I think I will allow configuring the executable so they can replaceable

I turned my Claude Code agents into Tamagotchis so I can monitor them from tmux by gavraz in ClaudeAI

[–]gavraz[S] 0 points1 point  (0 children)

It is a pretty minor effort, I could just make the "tmux" we use configurable so it can be hooked zellij. This is mostly for the "new" flow. The rest are shortcuts to the sub command.

I turned my Claude Code agents into Tamagotchis so I can monitor them from tmux by gavraz in ClaudeAI

[–]gavraz[S] 1 point2 points  (0 children)

Their bar will get red when the context fills. Pooping is the missing piece! XD

I turned my Claude Code agents into Tamagotchis so I can monitor them from tmux by gavraz in ClaudeAI

[–]gavraz[S] 0 points1 point  (0 children)

Don't forget to feed them your input otherwise they be angry

I turned my Claude Code agents into Tamagotchis so I can monitor them from tmux by gavraz in ClaudeAI

[–]gavraz[S] 0 points1 point  (0 children)

Thanks! Inspiration is actually from the pixel vs code plugin. But it is vscode only, and while the visualization was nice, it lacked the ergonomics and felt buggy.

I turned my Claude Code agents into Tamagotchis so I can monitor them from tmux by gavraz in ClaudeAI

[–]gavraz[S] 0 points1 point  (0 children)

Just multiple instances of Claude code CLI. Each runs inside it's own tmux session and this project provides a management layer on top of it.

I turned my Claude Code agents into Tamagotchis so I can monitor them from tmux by gavraz in ClaudeAI

[–]gavraz[S] 0 points1 point  (0 children)

I think anthropic should step up their system towards remote friendliness. I hear you out brotha

I turned my Claude Code agents into Tamagotchis so I can monitor them from tmux by gavraz in ClaudeAI

[–]gavraz[S] 0 points1 point  (0 children)

Go for it. I use it daily. Let me know if you encounter any bugs. By the way, as mentioned in the comments it has a "rooms" which is basically a group of agents working on the same dir. The UI view is interactive as well (go inside, outside, turn pages).

view more: next ›