I really enjoy the sidebar style for organising work, I’m not sure why the OpenCode desktop app moved to browser-like tabs (horizontal ones, though tbh my browsers now have vertical ones ehh).
I prefer Paseo https://github.com/getpaseo/paseo, mainly because I have specific preferences for different harness + model combinations. For example, I like using ChatGPT models via pi, and GLM via Claude Code.
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.
this looks prettttttty slick i might dive in later.
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.
I have a VM in which I run my general compute. In that VM I use incus linux container and run these tools as unauthorized user of the container. That should be reasonable security while having nice control for resources.
It’s just a personal preference, to be honest, so I wouldn’t overengineer it yet. In my case, I run it in a VM behind Tailscale. The main reason is that I want it to be able to install or use whatever tools it needs without contaminating my main machine. It can expose anything I need over Tailscale. So for me, it’s basically just a cheap, throwaway machine.
Orca is my main ADE too, but I haven't found any other users!
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...
Even though all these "ADE"s are mostly the exact same (Superset, T3, Conductor, Paseo,random Reddit-dude,etc.). I'm liking Orca largely because of the built in browser with ability to select an object(s), write a comment and send it back to the agent. I had built my own solution, but Orca makes it even easier and convenient.
Over 50 npm dependencies (dev and non-dev). Is this really how things are developed in 2026? After all what's happening (cyber security), is any developer out there running this kind of software just like that in their main machines without any concerns?
This looks pretty awesome, like almost exactly what I've been hoping for. Is it possible to run the sessions on a remote server to keep tasks running? I mostly work from my laptop and it's nice to fire off tasks to a remote server (mostly been Cursor Cloud Agents lately) and close my laptop, maybe check in from the app later.
I've been paying JetBrains in a personal capacity for about 15 years. Almost from the first year of my professional career. I didn't renew this year. I feel so sad and disheartened that a company that produced such brilliant tools have completely lost the plot on AI. They had started work on Fleet, a lightweight VSCode like IDE, before LLMs became big, but abandoned the effort without seeing it through. It could've been a great agentic IDE (all I want is whole file+project view for every conversation, instead of just diff so I can have a better perspective of the codebase). Instead they built multiple confusing tools (might be internal org structure and competition leaking out), and took far too long to adopt SOTA CLI coding agents, and kept charging for it as a separate subscription. I wish they do a whole company rethink on agentic development, but it is going to be tough because the existing enterprise licenses will continue to be the main revenue driver for a few more years, until it all dries up all at once.
I use IntelliJ at my current gig—and the CoPilot plugin for AI, because it’s what I have access to—and it has become ClaudeCode-esque of late: sub-agents, skills, tool-calling, hooks…and continues to improve. It’s unfortunate how the AI-in-a-sidebar UI kind of hides how sophisticated it has grown, but it’s a glass of ice water in hell in an environment where you can’t easily procure what you want.
Same thing. I've been using JetBrains IDEs for 25 years, and by now the keyboard shortcuts are hardwired into my fingers.
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.)
Tiny screen that can barely show any information and the awkward miniature keyboard that's slow to use and gives no feedback, it's a pretty awful way to do anything.
lately, i like to try to spend the morning talking through and framing up a few very detailed initiatives for parallel efforts that each spawn and orchestrate their own tasks, then feed them to /goals and go for a nice walk in the park, get some groceries, check in on the orchestrators and spawned tasks along the way, steer them from the phone.
so far it's been working pretty well for me in most cases, but not always. having a few parallel efforts in motion means that even if one goes off the rails, i can pause it and still make progress on the others, then fix it up when i get home.
You can also use it as a plain old chat client. I prefer it over OpenWebui because I can actually carry over my OpenCode configuration, which has specialized subagent definitions (for example, the "research" agent fires off a bunch of "web search" agents that use a cheap model to fetch and summarize, and the more capable "research" agent pulls it all together, decides if more search effort is necessary, etc.). So I can VPN into my home network and boom, self-hosted chat interface that's more capable than what you can (easily) do in OpenWebui.
Oh, I love the idea of a changes walkthrough. Maybe I'm old fashioned but I still look through all the code and prose that gets committed. In Orca, it took me about half an hour to even find the diff view (hidden behind a panel, activated on the top right)
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.
Seems like another clone of Conductor, though this one has a serious amount of feature creep (supporting so many platforms will add a ton of extra complexity), and on OpenCode SDK only.
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.
This looks very nice and well done. Good job! Okay, I'm going to have a tongue-in-cheek rant now.
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.
This actual functionality should be more explicitly stated, and should be described much sooner IMO.
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.
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.)
First screenshot is of a phone.
Yeah I’m never installing a coding agent on my phone.
Both codex and Claude have remote from phone. I’m personally using cli + terminal from phone.
I’m sure I’m not the only one.
It’s not great but it’s better than anything else I’ve tried.
so far it's been working pretty well for me in most cases, but not always. having a few parallel efforts in motion means that even if one goes off the rails, i can pause it and still make progress on the others, then fix it up when i get home.
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.
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.
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.
OpenConcern.
But at least it's better than Concern.net or iConcern, or even eConcern.
Let's not forget Digital Concern, ConcernCloud. And my least favourite, Concern On BlockChain.
MIT license.