If you’re happy with OpenCode as the harness, OpenChamber is great. But if you prefer using different harnesses under the hood, Paseo is a better fit.
I installed it on my homelab and can access the same sessions from my MacBook or iPhone at any time. Been really nice to use so far.
are people using these things but isolating agents to some sort of containerization individually or do you have like one big dev env ? probably time i get around to sorting a better dev container strategy just to isolate agents here but trying to think of the best way to set this up locally.
This actual functionality should be more explicitly stated, and should be described much sooner IMO.
What do you when done with a work tree? Just delete? I wish there was a middle ground of hiding it from the main panel, but keeping it for a week or so just in case I need to refer to something in the transcript...
They fumbled the initial rollout with the way they gate-kept the agents behind their own subscription. I used Claude through its API pricing for a while, and the UI experience with the sidebar chat was so much better than the Claude CLI.
I could see the thought stream, click on artifacts, view diffs, etc. But it burned through tokens way too quickly, so I downgraded to the CLI agent.
At least I can use IDEA's inspections through the MCP server. It enables the agent to use the IDEA's index for navigation (finding usages, locating symbols, etc.)
As a simpler desktop-only multi-platform option, I can highly recommend Termic (https://github.com/simion/termic). It just runs existing TUI coding agents (so Codex, Claude Code, OpenCode, etc) and manages them in sandboxed git worktrees. You get a real PTY to manage agent in, lets you see when one is working or has paused, plus a terminal, "changed git files", even in-line-code comments you can feed back to the agent. It's a good design, works well, the main dev is working very quickly on improvements, and they're responsive to issues and PRs.
Features we are proud of are one click onboarding of new VPSs into the agent fleet. Agent orchestration across different machines and harnesses. As an example, a Codex coordinator on one machine can run a Grok implementer subagent on another machine and they can talk to each other.
It's not really ready for public consumption yet, but it's been our exclusive daily driver for the past month. We'd be happy for people to test drive it and provide feeback regardless: https://github.com/madeinorbit/podium
Any suggestions for terminal UI versions of something like this?
I have a number of these pieces in a binary I drop first thing on every agent computer: https://github.com/housecat-inc/scratch
Chat to code with an inspector to point at specific DOM sections, review diffs on the box, hand off to mobile, etc.
Makes me wonder where all this will end up. Or DIY win with hyper-personalized tools? Will one vendor become the center of gravity similar to VSCode in previous generation? Will there be a cottage industry of more opinionated tools?
[1] https://air.dev/
Honestly right now I do a lot of development from my phone - I don't have the time to pull out my laptop very much. Right now I use hermes agent and just chat with it on Slack. But sometimes I wish I had easier access to more advanced features, and Slack isn't the best UI for this stuff. So I want to use something like this but am having analysis paralysis.
First screenshot is of a phone.
Yeah I’m never installing a coding agent on my phone.
Makes it feel like actual effort went into this. :)
I've said it before and I'll keep on saying it: the churn in new dev interfaces it's super exciting. Can't wait to see what next week brings.
OpenChamber, OpenAI, Open WebUI, OpenDoor, Open weights, OpenTable, OpenClaw, Open This, Open That. We're increasingly diluting the meaning of the term, and "open source" more broadly, that we're at the point of OpenFatigue being a real concern here.