31–40 of 45 posts
Thank you for sharing this. Regarding feedback on whether sandboxing would be useful, yes, please! Including something like Docker sandboxes would make isolating the agent env’s much less of a hassle. As an aside, I’m curious how others are handling this now… Mostly just creating dedicated user accounts?
This looks cool, I’ll definitely try it out. The best (for me) of these that I’ve tried so far is conductor.build They have a different UI orientation, and it’s more locked into Claude code, but it might be good inspiration for your future plans. They get the git worktree setup and teardown and managing dev servers part of it right IMO.
Have you tried Coder (coder.com)?
Hmm, this looks interesting. I've wanted to try something like this with an API provider that's free. I wonder how difficult to setup and how good OpenCode can be if used together with Ollama/llama.cpp and/or DeepSeek-Coder or Quen?
We need to start sharing our specific success and failure stories from using local llms for coding
How do you handle session persistence across reboots / restarts for self-hosted models? Does ollama support persistence out of the box? I tried using codex-oss which does support persistence but codex injects 6K of system setup context which I thought was too much for self hosted models.
I'm setting up a small orchestration around zellij (I have almost no experience with tmux, so I went with the "modern" alternative), upterm and qrencode that allows me to 1) generate a claude code instance in a persistent session 2) make it controllable remotely via upterm 3) scan a qr code to copy the upterm server's ssh url on my phone so that I can paste it in termux. I wonder if it would be more ergonomic to conn…
Tbh that's exactly what I'm using aoe for: termius on my phone ssh into my Mac mini and then use aoe to check in on each agent session. Just make sure you check out the readme if you do this because at least for termius there's a quirk to make tmux and TUI happy. The recommended approach is to run aoe itself inside a tmux session which then will spawn additional tmux sessions as needed.
Earlier quoted context omitted.
Tbh that's exactly what I'm using aoe for: termius on my phone ssh into my Mac mini and then use aoe to check in on each agent session. Just make sure you check out the readme if you do this because at least for termius there's a quirk to make tmux and TUI happy. The recommended approach is to run aoe itself inside a tmux session which then will spawn additional tmux sessions as needed.
After your comment I tried to do something with my phone but tmux + claude code is definitely not great on mobile though the main view of aoe works decently.
Steps to reproduce the bug that broke my tmux:
1. `aoe add .`
2. `aoe`
3. Attach to the session that was added
4. Close that pane with ` x` then `y`
5. Tmux closes down
6. Attempt to reattach to any session within tmux: `open terminal failed: not a terminal`
7. `tmux kill-server` is the only viable option, losing all my sessions
Does it have a . Hotkey for automatically switching to the next idle worker, like the namesake did?
I'm always curious how folks do status detection. Here you use tmux capture-pane and detect off that! Whew! Simple & direct! I've been really enjoying how OpenCode is so extensible, how you can make great plugins that can for example read the session.idle event & then go do whatever they want. That does require dropping in some config asking for the plugin, which takes some effort & requires a restart (but your sessi…
https://code.claude.com/docs/en/hooks-guide#hook-events-over...
It must be newer because Opus never seems to know about it, and the claude-code-guide tool that fires occasionally misses it