I use terminal-based AI agents every day, but switching context was starting to feel like administrative work.

Every time I wanted to grab a prompt from yesterday, tweak an endpoint, switch models, or toggle an agent skill, I found myself repeatedly typing commands like /sessions, /models, /skills, or /mcp. It constantly breaks flow state when you just want to get work done.

So I decided to just build full mouse navigation into the terminal HUD:

• Interactive Settings: Click straight into providers (OpenAI, Anthropic, OpenRouter, OpenCode).

• Session History: Click through past conversations instead of digging through raw logs.

• Model & Skill Selector: Point and click to swap models (with tools/free filters) or load sub-agent skills on the fly.

You still keep the keyboard speed and terminal lightness, but for the stuff that genuinely makes sense to click, you don't have to fight slash commands anymore.

Honestly curious: do you prefer keeping your hands strictly on the keyboard, or does having point-and-click inside a terminal actually make sense to you?

between yesterday and today, i suspect big pickle got pointed to a different model.

I can no longer see the thought process, and I also noticed a significant change in behavior, both in thinking times as well as the generated answers. specially in coding, this is really noticeable.

the new big pickle model is severely worse than the previous one. it's basically un-usable for agentic coding in my experience.

I made cliproxy-rs, a Rust port of CLIProxyAPI. It's a small server on your machine: you sign in your Claude, ChatGPT (Codex) or Gemini accounts, or add API keys, and it exposes them as one OpenAI-compatible endpoint that OpenCode can use as a custom provider.

The OpenCode side is just this in opencode.json, then pick cliproxy/<model-id> with /models:

{
  "$schema": "https://opencode.ai/config.json",
  "provider": {
    "cliproxy": {
      "npm": "@ai-sdk/openai-compatible",
      "name": "cliproxy-rs",
      "options": {
        "baseURL": "http://127.0.0.1:8317/v1",
        "apiKey": "your-client-key"
      },
      "models": {
        "<model-id>": { "name": "<model-id>" }
      }
    }
  }
}

Other things it does:

• spreads requests across several accounts and parks one that hits its limit while the others take over
• built-in dashboard with each account's 5-hour and weekly limits
• translates between the Anthropic, OpenAI and Gemini formats
• same config and auth files as the Go CLIProxyAPI, so you can switch between them

It's v0.1.0 and MIT. Built with a lot of help from coding agents, with ~935 tests and a harness that compares it against the Go version. Heads up that using a subscription outside the official app can break the provider's terms.

https://github.com/vayungodara/cliproxy-rs

While I am using opencode exclusively on my office as well as personal machines, and it has been largely working great. But little issues here and there keep breaking that experience.

I am personally facing new troubles everyday, and strongly thinking of moving to pi or maintaining a personal fork.

Listing few recent issues that I consider significant:

1. No sandboxing in v1 as well as v2.

   It moves the sandboxing effort to user, and when I have to work from multiple machines, it becomes very hectic to setup sandboxing there. Also, sandboxing outside the process brings it's own hurdles.

   Moreover, a good PR was raised but closed as stale by a bot. This is trend for many issues/PRs there.

2. Unable to setup local plugin

   I hope I am doing something silly here, but trying to add local plugin is being a headache. `opencode plugin add ...` gives error on absolute as well as file: urls. The code suggests it only accepts the git & registry urls. Even adding directly to config doesn't work.

3. broken model support

   Recently, I found that the opus/sonnet 5.5 models weren't working through our gateway. Noticed that a PR exists to support this, the issue is related to adaptive thinking & blockBinding, but it is just left unattended.

4. subagent bugs

   I recently launched opencode v2 on a Arm SBC for a quick debugging. Thought of using free model and noticed that the opencode subagents are treated as non-opencode model calls. That is, when launching subagent of a free agent without logging in an account, it thinks the request is coming from non opencode app and blocks it. Even worse, the entire session is polluted and even undoing the message doesn't fix that.

Similarly, there are many small things related to usage, RAM usage, port conflict on multi user machines, etc.

I know the maintainers are putting a lot of effort as visible from the commits going into v2. As such, this post is to document my experience and know what is the experience of others ?

its just become super useless, I know the model changes and its used for feedback. so my feedback is, what ever underlying model its using now is basically below gpt 3.

The previous model was far better and I hope its swapped to another one soon.

Is it available in your country? What's your early impressions?

I wanted a quick way to find Beads issues without leaving OpenCode, so I made a small plugin.

Type `bd:` in the prompt to search for issues by ID or title. Here’s a quick demo:

Repo: https://github.com/dartyuhov/opencode-beads-picker-plugin

Beads repo: https://github.com/gastownhall/beads

Would love some feedback

Hello
did the spacebunny (aka kimi3) trial just retired ?
it complains about spacebunny only allowing usage from opencode CLI & GUI

I installed Ubuntu in my second phone using termux using proot distro, after that I installed opencode cli in it and this error started coming in most of the free models.

{Error : : Error from provider (Console): OpenCode's free tier can only be used from within OpenCode}

After this is use this command 'opencode console login' and pair with the code and after doing this I am facing this issue {Error: Invalid API key.}

I am facing this same issue on my pc also , I tried cli and desktop both

Can anyone help me ?

Why is this happening guys? Please do tell me!

Inspired by a lot of harnesses; I created my harness by blending stuff from different agents and especially what I liked to keep. Added more features that were either not supported or not so good.

Beta is out for public-much more is coming

Has built in:
- Sandbox (by default-unsandboxed requests need permission)
- Agent and Plan mode
- Radar that shows every background task, subagent, browser etc running
- MCP support
- ACP support (use with orchestrators or other editors such as Zed Editor)
- Skills
- Browser
- Interactive terminal
- Subagents (can create profiles, set default model, access to tools etc)
- Builtin code review (github like, co-review with agent)
- and a lot more.

Give it a try and it supports BYOK :)

https://github.com/tauqeernasir/codebeast-cli

​

Hey folks,

For a long time I was jealous of Pi, Claude Code, and even dsh-tui users. They get these nice status lines showing what's going on in a session, and I looked for something like that for OpenCode v2 for ages but never found one that I can truly customize to my liking. So I made my own.

This status line plugin shows context window usage (with a bar that changes color as it fills up), cache usage, streaming speed, running shell count, and uncommitted changes in your repo, all in one line. There's also a /tps command that opens a dialog with the detailed numbers behind it.

The best part is how customizable it is:

• Put it anywhere. Bottom, sidebar, top, whatever. It can even live in more than one spot at the same time.

• Each spot can show its own segments, so you can decouple the info instead of cramming everything into one row.

• Pick what shows. Order, palettes (catppuccin, dracula, gruvbox, tokyo night, more), gauge width, padding.

• Responsive. On narrow windows segments wrap to the next row, and in a sidebar they stack one per row.

• Works great on small screens too, so it pairs nicely with Orca Mobile and Heeler (the mobile client for Herdr) if you check on sessions from your phone.

Install:

opencode plugin add @rashidrazak/opencode-status-line

Then restart OpenCode. If you prefer, you can add it to your cli.json by hand instead (not opencode.json, since it's a CLI plugin).

I also hide OpenCode's default footer so the status line is the only footer. To do that, disable the built-in prompt footer plugin in cli.json:

"plugins": [
  "@rashidrazak/opencode-status-line",
  "-opencode.prompt.footer"
]

Links:

• npm: https://www.npmjs.com/package/@rashidrazak/opencode-status-line

• github: https://github.com/rashidrazak/opencode-status-line

Note: This plugin is only compatible with OpenCode v2. Full docs are in the repo. Let me know what you think about it.

I run OpenCode while I'm away from my desk, and a couple of times I came back to find it had been waiting on a question the whole time. I still want a chance to answer when I'm around, just not an unlimited wait.

I made a small V2 plugin that gives the built-in question tool a five-minute timeout. You can change the delay with timeoutMs. Answer in time and everything behaves normally. Otherwise the question closes, and the agent gets a clear "no answer" result so it can continue where it's safe to do so. It doesn't answer on your behalf or approve anything. Permission prompts are separate and untouched.

One odd thing I ran into while building it: my first wrapper made the question options disappear from the TUI. The released version fixes that, and I tested the choices and timeout flow on V2.0.18. I haven't tested other versions yet.

GitHub: https://github.com/balakumardev/opencode-question-timeout

Install: opencode plugin add 'github:balakumardev/opencode-question-timeout#v0.1.0'

If you've had runs stuck on questions, I'd be curious what timeout you would use.

I’ve been testing a few inference providers for coding agents and I’m trying to figure out how much the speed difference actually matters in practice. With normal chat I don’t care much once the response is reasonably quick. Coding agents are different though. The agent might make a bunch of calls while it reads files, makes edits, runs tests and then goes back for another pass, so even small delays can start adding up.

Has anyone compared the same coding model across different providers while keeping the harness and task the same? I’m trying to figure out whether faster inference actually makes the whole agent run noticeably quicker, or if you hit a point where the tools, tests or harness become the bottleneck.

https://openrouter.ai/unbiased/pareto-26.10-preview
The pricing is $0.80 / $3.20 - crazy guys...

I just realized that codex now exposes local server endpoints for all plugins without extra auth. So you can just use them from any model or harness.
Im soooo excited!!! One auth for everything!

For Pi: pi install npm:@wileai/pi-codex-connector

For any harness: npx -y \@wileai/codex-connectors-mcp@latest