Good questions! All of that is handled inside of the coding agent (Claude Code / OpenCode). `aoe` is responsible for managing the agent sessions: It does keep those sessions persistent in tmux even if you close `aoe`, but if you restart your system, resuming a sessions would rely upon opencode/claude code storing the conversation history for each session, which I believe they do but would need to be manually restored for each agent.

THIS!!! I'm right there with you. Imo, using aoe (or whatever tool you can find for session management) is the key unlock to help give us all the patience to try out the ollama/lmstudio/mlx providers to see how they really perform. We're lacking information about what work is really being done with local coding models, at least somewhat because imo most github open source repos don't ask you to share what LLM you used to help you, and they should.

We need to start sharing our specific success and failure stories from using local llms for coding

I haven't. Looks cool though!

Thank you for the feedback! My general feeling is that people are not doing sandboxing. Those that are, generally use devcontainers or some docker based solution

Once you are attached to an agent session, correct it's just tmux! aoe does: - gives you one screen that shows you all of your agents and shows you which one s are waiting for you to attach to them and give them a new task or answer a question

- Easy git worktree integration to help you manage branches when running multiple agents in parallel on the same repo.

I also plan on adding a lightweight docker sandbox integration to help give you the option to sandbox a session when you run it (but that part isn't ready yet)

Personally I'm actually feeling like the CLI agent is a great experience once you get used to it, and managing them in aoe honestly does sort of feel like my worker management strategy when I was trying to maximize my productivity in age of empires 2

Conductor build looked cool. For me, I wanted something a little lighter weight that stays in the terminal. When I looked at conductor it seemed like it was a standalone app

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.

I'm also seriously considering the ability to produce aoeii sound effects like "nuh nuh nuh"

1

it must be done

It has been scheduled https://github.com/njbrake/agent-of-empires/issues/23

Haha I'm all about the KISS principle. I also set up a snapshot testing framework so that people can submit screenshots of any messed up status reports and I can easily add them to the test suite to make sure we fix any issues that someone sees.

I'd love a cli subcommands that would just give me status, btw. Very neat to have.

I need to add some better docs but the CLI of aoe supports it already!