Hacker News

I went from TUI and tested several GUIs that can also support a "TUI" view.

After testing several options at the moment I'm using Orca IDE as my daily driver - effectively as a layer on top anthropic / openai

- Supports both anthropic and openai with subscriptions and can you swithc easily between those two + other LLms

- Its a bit hidden / non intuitive to setup but it does support running everything on remove host -> I run (95%) of my jobs on remote hosts that I can both access from my laptop + their native app via a wirguard vpn

- You can switch between chatview + TUI on the same conversation - very useful if you move e.g. from desktop session to mobile view.

- For repeating LLM tasks Orca also suports a kind of scheduler - but I prefer currently to have the agent set things up via chronjobs on the remote machine (not super happy with this ...)

Key reason I dont want to go fully ChatGPT/Claude is also I dont want to build a super strong dependency on those mega players and remain the ability to switch to other interefernce providers / models.

As LLM usage is already a core workflow in our company - a sudden unavailability of one or a massive price increase - makes it absolutely necessary to build out alternatives.

We all know the downsides of SAAS Lock in too well from the 2010s. In that sense Fool me once, fool me twice..

I find TUI scales better for multiple concurrent agents across the same and different codebases, especially using tools such as herdr. I can fire off an agent, which runs sub-agents. Then check-in periodically to re-steer as needed or be interrupt driven for completions of tasks. I can't see how vscode/GUI is better for this?

I switched to the Linux desktop as soon as it was available to avoid all of the TUI rendering bugs and restore sensible copy/paste. I was using vscode's git panel to review diffs before they got committed, but had a feeling that there had to be a way to make agents pull harder so my review wasn't always the long pole in the tent.

Imagine a local GitHub PR web UI (thanks to difit), married to your agent for real time in-context discussions, and built-in skills to teach agents how to write easy to follow PR, focusing on both why's and hows.

Last night I released gavel that scratches this itch: it's open source, so fork and enjoy. https://photostructure.com/coding/gavel/

I hear people swear by https://github.com/getpaseo/paseo

Not only it's a GUI in client-server topology, it can also orchestrate the agents to work for you.

Haven't tried it yet.

I graduated from Claude Code to Herdr to now T3Code.

T3Code can do anything I might need such a tool to. It supports a bunch of different harnesses, therefore also subscriptions. It supports running agents on different servers, from the same GUI. Mobile app that works well. Orchestration that allows any agent to orchestrate others in T3Code directly.

I just ended up making my own GUI. I never really liked any of the pre-build ones. It started slow (3-4 days of work) and grew organically around my working style. I can also have my preferred UX (e.g., high information density).

Take a look at the Codex App Server or the Claude Agent SDK as a way to communicate with harnesses running headlessly and build your own UI on top. I’m sure Pi can be set up in a similar fashion.

I went the same way but found that the GUIs (Claude and Codex Desktop) are still too low-level to scale well. They are basically just tabbed chat windows. I wanted more structure and more targeted UX for managing my work. It's easy nowadays to build your own GUI, so I did.

(I found it's still quite some work to polish it so that it's actually good. Therefore, sharing it could still benefit others, so I did: obeya.si, free, open-source)

I am not a terminal head, but I find it simpler to drop into a dir and codex from there. In the GUIs, I often mistakenly end up under the wrong tab (Chat/Work/Code) and if I am in Chat, sooner or later the thing will ask me to switch to Work. On the other hand, the GUI provides the history of threads. I semi defeated this by using hooks to write questions and answers to an SQLite db.

I’m being slowly forced to use a GUI at work, and it’s fine, but I simply prefer the TUI.

I use:

claude agents

Granted, I run it as a terminal tab in my editor so that I can look at files. I prefer the TUI in a tab instead of the editor’s half-assed plugin. These days, however, I mostly look at PRs in the browser.

For my personal work I still prefer to let the agent edit the local files so I can preview the changes in my editor. I avoid PRs in my personal work.

> now I'm using ChatGPT/Claude desktop

Same, it's lovely software for that mode of work!

I also briefly tried out other ADEs, like:

- Kepler (by the GitKraken folks) - https://www.gitkraken.com/kepler

- Paseo - https://paseo.sh/

Kepler had a really nice issue tracker integration but the UI was very vibey and not quite as to the point as I'd like (who needs graph visualization of what the agents do, just give me tools that work), and Paseo had a really nice UI that I could use to drive both Codex and Claude Code, but some OpenCode agents would sometimes hang and I didn't have tools to really do anything about it.

Maybe I should also give JetBrains Air a look again, if I ever end up subscribing to them again (I just moved to Zed for my code editing): https://www.jetbrains.com/air/

Interesting space, with so many additional tools popping up! That said, the OpenCode TUI was really pleasant too.

""GUI is less verbose with the nitty gritty hidden in expandable sections, ""

? The GUI has nothing to do with that.

If you use Chat / Work / Code <- that's the differentiation.

So 'Code' in 'Gui' is identical to Claude Code except for the visual layout.

If you use Work or Chat, which are not optimized for Coding you'll see a different experience.

If you use iTerm or Ghostty and set a key combo to switch tabs you can very easily switch between tabs and the TUI generally gives more dense information.

Usually people migrate to TUI not the other way around.

I think that there are reasons to use GUI - if there is deeper integration with Git or an issue tracker - or - in VSCode - for navigating files etc. - definitely those things are valid.

But for raw AI the getting a TUI to work the way you want it is ideal.

Herdr changed my tui game. Pi but for tmux.

I thought the TUI was the ultimate power tool and loved the original embrace from claude code. I still use TUI a lot, but have been using deepseek harness web app atop my local model and am already liking the better organization and UI of this interface. I can see my load shifting to it. But you are right, you almost always need a VS Code interface open as well.

The outputs of Opus 5.5 were so much easier to read, but I do find the the deepseek web based tool much easier to comprehend for some reason. Plus I can access it from phone (over tailscale) as well when out and about and continue sessions very easily. AND it is all open source/weights. I'm pretty thrilled, but it's been less than a week.

I also like the inner text display of the GUI more, but the window management of it terrible IMO. On my Mac I have 3 desktops open, one for "private" and two for a project each. With the Claude TUIs I just have 1-5 open terminals per desktop, each with its title neatly set automatically. With the GUI app, I can only have 1 open, not one per desktop. It seems you can open several very reduced versions of the Claudr app with a single chat but that didn't work well for me. So that's why I'm still with TUIs..

I've lost faith in the ChatGPT desktop app. It's nicer than managing a bunch of TUI sessions, but it's so prone to losing session history / context.

I switched to the GUIs half a year ago and never looked back.

From the text rendering and scrolling alone, they are much more pleasant to work with.

Conversations with activity and MR status indicators, nested sessions, images in the chat, and generally more information and functionality on the screen.

One negative is that it gives Claude, and particularly Codex, room to mess up with auto-opening artifacts.

Codex, when I was still using it, kept opening report or comparison pages in fullscreen when I did not ask for artifacts.

Claude loves to open its iOS simulator pane, but somehow never displays the one it's actually using, instead showing a simulator that is idle. It might be related to my custom tooling.

One of the very first thing you should do is stop using vscode’s terminal.

Use something like Rex, Ghostty, kitty or whatever floats your boat.

You will have a much better experience.

I use the terminal for most of my agentic workflows.

I still use vscode, but only for diffing and the proprietary devcontainer stuff.

I dislike the harness TUIs for this for the same reasons. Nothing against TUI in general, the lazy* universe for example is great.

OpenChamber (the desktop app, not the VSC extension) for OpenCode currently works best for me. Especially because of its seamless remote control via their iOS app.

> Who else is just using the GUI nowadays, or are you still on the TUI, and why, have you tried the GUI interfaces?

I generally prefer GUIs but I'm OK with a TUI harness. Anyway, there's a web frontend for Pi (https://github.com/agegr/pi-web) which looks very promising although it still has some rough edges. They even have an interactive demo: https://agegr.github.io/pi-web/

I'm not associated with the project.

Im also using the desktop apps (codex/claude). Using the tui doesn’t bring any advantage anymore. I can drag and drop pdfs, images, i have the browser view, can easily switch between conversations, fork them at any point.

I use whatever IDE to review the code, read tests, etc. I used to use the terminal for everything prio AI, but not anymore.

Some of it is the historical snobbery that CLI users have for GUI users. I count myself among them. Isn't it way cooler how I can fix my NIC with just three chained bash commands, while the windows users have to navigate 8 levels of dialogues?

But that mentality doesn't leave room for a lot of nuance. Even the most hard core TUI proponents and neovim gurus probably do not use Lynx as their browser (well maybe they use a vibe coded hacker news TUI client instead)

I was confused until you mentioned you were running it in VS Code. That issue goes away if you run it in a standalone terminal with tmux or tabs.

I'm still using the TUI. I've ditched my IDE and use Sublime Text with LSP for code reviews and navigation. It works great for me.

Just GUI now. I can also connect to Mac Codex from my phone and have a voice chat with it. Collects all my work in projects, can jump in and out anytime. Can start a project on the phone, move to Mac. (Almost) No sync issues, which I found the TUI/phone had.

I mostly use TUI because I have agents running on different servers over SSH.

I often need agents on one server to talk to a different agent on another server through tmux, and it's just much easier with TUI.

No idea what you're working on, but if it's anything involving sifting a lot of data, how do you know if your code actually works or does what Claude says it's doing?

I wanted to use the Claude GUI but it wants me to enable developer mode just to run it on Windows.

Would love to use a GUI, however it doesn't work properly for WSL either in 1st party or 3rd party clients like Orca, so I'm stuck with TUI

How do you handle the errors that the agents make?

How do you handle the potential errors that might be hidden in parts of the code you don’t understand anymore?

Or do you have 100% understanding of the generated code?

I'm using pi with herdr/ovis, which gets me both a GUI and a TUI. There's a Chat/Terminal switch, which is just a different view of the same pi session. It's got a decent mobile web UI, and I've been really liking it so far.

I’m using one iTerm to host the TUIs. The RAM cost is a tiny fraction of modern electron-based gui slop

Most harnesses are not designed with conversations to be append-only from the start, which causes us all endless pain when caching is concerned.

When making a harness, it is so, so easy to do the "web thing" and have your system prompt be a template where you dynamically inject variables like the current date or the contents of the current working directory, and then just re-render that template on every request. THis is a bad, doubleplusungood, terrible, awful idea, and you should never do this under any circumstances. Anthropic will soon force you not to by literally refusing conversations that "break continuity" in this way and do anything but append new user messages at the end, but other providers at least appear to work.

I've only used CC and Pi and the point of pi is to use extensions. Luckily you can write them yourself pretty easily.

I cannot get behind CC is the best harness. Once u switched to pi I knew I was never going back and occasionally I need to use CC for my subscription and find it unpleasant. CC is just this incoherent hodge podge of functionality that seems to have no vision. Subjective, of course.

I've been using claude-bridge [0] and pi-vcc [1] for compaction and it has been a complete life changer. I'm slowly phasing out my Anthropic use for Mistral but I've used it for months without issues.

[0]: https://pi.dev/packages/pi-claude-bridge?name=claude-bridge [1]: https://pi.dev/packages/@sting8k/pi-vcc?name=pi-vcc

Using the Agent SDK to connect to Anthropic is an officially supported method and does not risk a ban.

I use a cheap deepseek model for compaction on purpose since it costs a penny or two and does not use any of my Anthropic quota.

Regarding credentials, my base instructions shared across all agents and all harnesses is that all credentials are accessed through a specific powershell script and should never be shown or written to file. This seems to work with pi, opencode.

6. A\ reduce model usage for non-CC client. https://github.com/anthropics/claude-code/issues/97074

> 4. Cache related nuances (I mean, A\ regularly messes up with cache even in CC, their caching is non-trivial);

I'd be curious to know the background around this. At work, I've used @anthropic/Opus 5.5 through Portkey with Pi, and ended up with $10 within less than 10 message exchanges, on a fairly trivial topic. OTOH, when using Claude Code directly with Opus 5.5, I basically spent $30 for a good back-and-forth across a full chat, reaching the point where CC kicked off compaction.

I agree. They are probably solving problems we don’t know are problems, beyond UX (like caching). That’s one of the reasons I prefer CC over Pi. Codex is pretty nice too, with respect to UX.

You can write your own compaction function for Pi, and you can even have different, domain specific compaction logic if you want. The default one is dumb, I agree.

I tend to agree with you. I wrote 4 separate coding harnesses of my own earlier this year (in different programming languages, great learning experience), but pi running good local models like qwen 3.8 next flash, or a deepseek flash API from a vendor with decent privacy assurances is really the bedrock of my workflow. There are always exceptions: running pool harness with Laguna XS 2.1 6bit is a really nice local dev experience for code maintenance and quicker sessions. Also, I very occasionally really enjoy DeepSeek Harness with deepseek flash, CC with Opus 5.5 and agy with the latest Gemini Argon.

So there are many wonderful dev experiences, but generally relying on something relatively simple like pi makes a lot of sense, for my use cases.

Is OpenCode already passé? Especially with OpenChamber on top I don't see a reason to switch to PI.

> Pi is without contest the best harness. Because it’s yours

You can do this with any harness. I really dislike the Node.js ecosystem and avoid Pi and the like. I started with another one written in Go that has all the basics and I can extend it in minutes for anything I need while keeping track of upstream.

Exactlty. I love that it works the way I want it to work. I can install and write extensions I want.

> it’s yours, the total control is the only way to move from driving agents to orchestrating them

I wrote Juggler (https://github.com/juggler-ai/juggler) because I liked Pi's approach to everything being customisable and controllable, but I wanted a slick, navigable GUI rather than terminal hell.

...BUT: having gone to great pains to build an architecture around customisation, where every possible pluggable thing is a plugin, I'm starting to feel jaded on the whole "we need to customise it all" mentality. The models have got so good over the last year that I just don't think that tweaking the harness is something many people will need to do as things progress. The models only need a bare-bones set of tools to do everything they need, and I'm starting to think that UX and UI are the only really important things to focus on in an agent.

(Although from the perspective of coding a harness, making things plugins and having a plugin API does help to keep things clean and stops the codebase getting sloppy)

>Pi is without contest the best harness.

There is contest.

https://frontierharness.org/

With minimal work, you can get DSH web to be exposed to your internet behind Cloudflare Access (or similar) and have a harness running on your computer at home from any browser, including your phone's.

Second this, I went from Claude code fighting me all the time and being insanely opaque with its internals to Pi with detailed telemetry about what my agents are actually spending time on. My entire harness is completely custom, and works exactly the way I want it to. Absolutely love Pi

> Claude has been reading AGENTS.md files for a while now.

No it hasn’t, this is a very recent addition. Previously you had to symlink CLAUDE.md to AGENTS.md, or include a @AGENTS.md in your Claude file, but by itself it would not read it

I just have custom instructions to tell the model to edit files using its tools rather than a gigantic bash pipelines. That's 80% of it.

I just have a hook that tells agents to echo what they're trying to do. Works fine.

alternatively, you could learn to read it

> it because anthropic doesn't allow other harnesses.

You're not able to use the API credit and hook it up to another harness?

https://platform.claude.com/docs/en/about-claude/api-credits...

I use Requesty to get access to models from all providers, including Anthropic. It is pretty cheap and competitive with others for the quality. haiku 5.5 is one of the cheapest available, cheaper than Qwen while being superior in the price range (less than 10 cents per million tokens). I put 10 dollars to use on my hobby projects and I still have more than half after a couple of weeks. Using bigger models is dramatically more expensive, of course.

> because anthropic doesn't allow other harnesses

I don't think this is true. They never went through with this change. If you use the SDK it appears ToS compliant. You just can't sell it or distribute it, hence why pi doesn't support it.

> anthropic doesn't allow other harnesses

they do though?

edit: i guess the parent comment meant subscriptions specifically.

So you could make yourself much happier at work by paying the $20 yourself

You can use any harness with claude sub through llm reverse proxy

Could you share your setup? is it skill-based? I like the idea of using the model as a tutor/pair programmer so that I stay more grounded rather than delegating too much of the coding to it.

Share it please I want to see

That’s not correct. It depends how you actually connect to the Anthropic API. The Agent SDK is allowed.

https://support.claude.com/en/articles/15036540-use-the-clau...

I have not used them but supposedly you now get API credits with subscriptions now. (I don't know if it's changed but in the past when they've given API promotions it required enabling billing for API and I don't dare risk some bug on their end billing me a billion bucks)

Works on my machine (with OMP). If they ban me I’ll switch to a different provider.

Ueddit link for those who don't want be tracked by Reddit:

https://www.ueddit.com/r/DeepSeek/s/sxg7aAM6rS

X link for people who don’t use Reddit:

https://x.com/DeepSeekHarness/status/2117256196227019194

I use pi.dev since it came out and love it - and pi-claude-code is a great help since Anthropic turned of subscription access. But I also see every day how Claude Code tries to lure me back and often refers to its own skills which then don't work properly eg when spawing sub agents or asking me to run certain commands. Dark TUI Patterns.

Is that still needed now that Agent SDK usage is included in subscriptions?

https://support.claude.com/en/articles/15036540-use-the-clau...

  Update October 7, 2026: Claude Max, Ultra, and Team plans now include monthly API credits. They cover the Claude API, Claude Managed Agents, and the Claude Agent SDK and claude -p when you run them with an API key from your linked Claude Console organization. Nothing changes for your plan: when you’re signed in with your Claude plan, the Claude Agent SDK and claude -p still draw from your subscription limits.

Anthropic's subscription is the one that has historically been tough to use with other harnesses, where they have (had?) technical safeguards to ensure your subscription usage was limited to Claude Code CLI, with third party harnesses often implementing workarounds or faking it to use your Claude.ai subscription. Nowadays Jetbrains Air does officially allow using your Claude.ai subscription.

But OpenAI's subscription has seemingly always been available to use in other harnesses without trouble.

Yes, you can use your Codex subscription with Pi without any limitations. It supports Codex out of the box. You may need to install extensions for things like tracking usage and limit resets though. Pi only provides basic Codex integration.

Yes. You can and it's easy to test. I'd also encourage you to try local models with it as well.

Pi/opencode apparently make 10% already of all traffic already:

https://manifest.build/blog/chatgpt-plus-tokens-third-party-...

Yes and no. Any harness can use the subscription but must go through `claude -p` mode, which is more limited.

There is no stick unlike Anthropic (along with insisting on signing commits and "don't abuse the robot" the reason I started to use OpenAI instead of Anthropic --- not that I am under the illusion they are any less evil overall) but I think now there is starting to be a carrot towards Codex usage since there sessions are "cached forever". I assume if you use Pi you get 12 hours of cache instead.

Using your subscription in 3rd party tools is explicitly allowed for Codex, and disallowed but not really enforced for Claude. There are extensions for Pi that allow you to log in with your Claude credentials, Codex is iirc even built-in.

This, IMO, is one big selling point of Codex for me. The are much more accepting of usage outside of the Codex harness, and make it trivial to set up.

Yes, it is allowed and supported normally by pi and others.

I would not trust auto mode in the first place.

Wrap your agent of choice in e.g. docker sandbox, nono.sh, Nvidia OpenShell, microsanbox or any other sandboxing tool and run it without any checks (i.e. "yolo mode", dangerously-skip-permissions etc.)

IMHO it makes the whole category of problems around permission fatigue, trusting the harness (or plugin) authors etc go away.

Well yeah, the whole point of pi is that you build it to your workflow. If you dislike the entire point of a project, it’s not for you. I run my agents in a sandbox. When Claude or Codex then double sandbox themselves, it gets really annoying.

I use https://pi.dev/packages/pi-warden with Jev (but can use other Decisions API), it would make sense to combine with pi-permission-system to get the CC two stage "default auto" mode.

You'd have to install an extension or write a function that intercepts tool calls.

gotgenes/pi-permission-system and the ai-guard authorizer can do a lot here, it feels very similar to cc auto mode.

I built a policy authorizer on top of pi-permission-system that looks kinda like nftables that models commands/subcommands/options as read/write and enfores policies depending on if the sub agent is read only or write, which really cuts down on the stupid decisions and nicely complements AI cmd review. Pi shines for making things like that possible.

You have time to watch over your agents?

like the auto mode classifier? if it doesn't then... that's a risky tradeoff

Sounds to me like it isnt basic functionality if it all works ;)

> bear bones

*bare

> The apps I build tend to be the result of several dozen or several hundred features developed mostly serially, and I am always the bottleneck because of that whole "knowing what I want" thing.

This is probably where the disconnect is - the TUI workflow only really clicked when I started working across multiple worktrees at the same time.

It’s not all or nothing. You can still be fully in the loop, read all the code and steer each session towards the outcomes you want. You’re just doing it across multiple branches at the same time and imo it’s easier to do that through the TUI.

Agreed that it's annoying by default, but it's quite easy to disable: https://code.claude.com/docs/en/settings-reference?ref=expla...

I am using https://github.com/melihmucuk/pi-crew which I like more. It has pretty nice pre-defined agent .md files. Then there is also https://github.com/nicobailon/pi-subagents . It is probably worth trying all three and decide. But pi-crew is a winner for me personally.

Note that there is another extension called pi-crew which mentiones in Readme that it was completely vibecoded, I haven't tested that one.

I've been using pi-optchat, might want to give that a try. Manually connecting subagents to the main agent keeps them open indefinitely. https://github.com/jonaslsaa/pi-optchat

Try and get on the early access waitlist for Rex, really nice terminal + multiplexer. Ghostty replaced iterm for me and my team, then Rex which uses libghostty was a great level up further.

There are some extensions you can use to use your claude subscription on Pi, it runs Claude Code under the hood but with pi's prompts. The same is possible with Opencode

There is no 20x any longer, no?

I don’t think OP is proposing using a local model?

Why do you limit yourself to mac?

You can run larger flash models on a modern PC using strata. These models perform pretty good even on low quants.

Furthermore, next generation open weight models will swap some compute for storage, making them more accessible for masses.

I am genuinely curious to know what kind of genuine problems people are solving with opus that cant be done with sonnet or the free models. If there are problems that people are working on that only opus 5.5 can solve then were we not touching such problems last year at all (because last years best model was inferior to sonnet 5.5). And if people are solving such problems now, why cant I see any meaningful improvement in even a single software I use everyday?

Not trying to diss on anything or anybody. I want to know.

I don't get why many of the products from major providers are GUIs, don't they know how to generate a proper terminal-based tool?

Turns out, no. There's a Hemingway quote that greatly describes the current AI situation: never confuse movement for action.

Alternatively, what you’re seeing is continuous hill climbing and optimisations based on large scale experiments and simulated rollouts.

For me personally, I don’t use Claude Code because I can’t read the source.

At least with Codex, I know there’s a bunch of telemetry and all that, but I can have my agent inspect the source and have relatively greater confidence it’s not implanting spyware onto my machine, because a classifier thinks I’m working for Deepseek or something.

'Tis a joke. His landing page says he's a dev at Salesforce, so I presume not famous.

I’m definitely not famous :^) thanks for reading!

It’s not that unreasonable, or at least wasn’t a few years ago. I complained about the Chatgpt Pro $200 not allowing basically unlimited image generation (the limits were super low) a couple years ago and the next day Sam Altman tweeted asking about switching up how they handle Pro plans and putting usage into a single pool (which is what they moved to). If he didn’t read my email directly the gist at least got to him.

>> Someone at Anthropic must’ve caught wind… just a day after making my decision, they announced Claude Code would finally start supporting AGENTS.md files in an effort to get me to stay.

> Forgive me for asking if I should know, but who is the author? Is he famous?

I think that was tongue in cheek. And by that I don't mean the author's tongue was actually in his cheek.

I also think it went over your head. And by that I don't mean I think it literally went over your head.

Claude now supports AGENTS.md fully but the rest of what you said holds

An accountless provider such as PPQ.ai or NanoGPT (and these also have auto-models so that the best model can be chosen depending on how easy or hard your prompt it). If you like this idea, use this pi extension to use them: https://www.npmjs.com/package/awto-pi-lot

ChatGPT plus or pro

Something is misconfigured on your end. I have had some trouble where parameters were incorrect, but otherwise I have used several vendors (local, openrouter, ollama cloud, kimi, deep seek) and it generally works.

Most likely context length parameters aren’t set quite right for your model/provider and you genuinely run out of context during compaction

I never really rely on compaction. Instead, I instruct the coding agents to maintain a handoff markdown document across sessions. Ymmv.

Try pi-vcc or pi-blackhole

Alas Opencode's source is hideous to read.

When you say "kinda dumb" it's worth noting that the smaller coding models tend not to actually need system prompts to be helpful coding assistants, etc. Qwen maybe more than Muse Glimmer? I've not tested Qwen 3.8 27B enough yet. Even Gemma 4 didn't seem to need much.

Muse Glimmer is so absolutely tuned for one particular pattern (turn-by-turn agentic coding and assistance) that it will do it more or less without a prompt at all (except to set the reasoning level maybe). Beyond the tools announcement, it feels to me like it almost only needs a prompt to do plan mode stuff. If LM Studio (in either of its forms) or Unsloth Desktop had proper support for running inside a linux container rather than just a filesystem sandbox, you'd barely need a dedicated coding agent at all. Osaurus gets even closer.

I wanted to like Opencode but I can't, really. I am enjoying Pi slightly more because it's just way less convoluted and obscure.

FWIW I use Paseo for the GUI, which to some extent eliminates that aspect of decision fatigue; if you like Paseo's UI well enough, you can have it with almost any harness. And since it can connect to its daemon via ssh you can still have the desktop GUI with a container. (Not clear to me if Opencode v2 Desktop makes remote connections to the daemon or just wraps the web interface like v1 did)

Opencode's system prompt is much smaller than omp. Smaller models may not work well just because of this. Also omp is not pi.

ohmypi is not pi, it's based on pi, but it's not pi.

Damn I built almost the exact same thing lol, down the supervisor for each project and web kanban board thing. I use fly.io sprites for the compute which has been cool to experiment with.

WRT security, I recommend you skynot to use Pi (it's in the sweet-spot IMO): https://www.npmjs.com/package/skynot

I wrote it, in case you have any questions AMA.

> At this point, you probably don't need either.

There's only so much stuff I have the patience to tell it in a session before I write it down somewhere.

It's common to disclose that it's your own project when linking it. Don't mean to be rude or anything.

Man, my M1 Pro unfortunately only has 16GB of RAM; it has been such a limiter to using local models. I'll give kapitsa a try, I see I should be able to squeeze some smaller models on

Made me click, but I have no idea what this is supposed to be.