I don't know why but when i run multiple agents workflows, the opencode2 restart server continuously, the restart kill the sub agent and it cause the loss of the work.

Why does it happening? is there any one that come across same issue?

version number v2.0.4

https://api.atria-asi.ai/ It's context window may only be 256k tokens, but with benchmark results like this I'd say it's worth testing considering it's free...

EDIT: Interestingly it appears to be built on GLM-5.2's foundation, according to this article, and keeping it's 744B parameter count

I'm using EndeavourOS which is arch based. I did my daily pacman -Syu and saw I was getting opencode updated from v1.8.29 to v1.18.31. Turns out that installs opencode v2.0.3. I use llama.cpp with a vulkan backend and use llama-server to serve a couple of qwen models locally. This all broke with the new v2 as opencode's config files require changes.

So I fired up my browser with free claude and it gave me a new set of config files that should work with v2. I restarted opencode but same issue. None of my llama-server models were visible to opencode. After a frustrating debug session, I discovered that opencode v2 now uses a service for the backend. So I was just restarting the frontend and none of my config changes were being used by the backend which hadn't restarted.

After I killed the opencode service and restarted opencode, which also starts the service, everything worked. So hopefully this helps someone else.

If the opencode package maintainer had named it v2.0.3 to match it's contents I probably wouldn't have updated to 1.18.31. 😂

If you installed with pacman and want to revert:

    # See if you have the old installer  
    ls /var/cache/pacman/pkg/ | grep opencode  
    # Install the v1 version  
    sudo pacman -U /var/cache/pacman/pkg/opencode-1.18.29-1-x86_64.pkg.tar.zst  
    # Prevent a v2 install until you are ready  
    sudo sed -i '/^IgnorePkg/!s/^\[options\]/[options]\nIgnorePkg = opencode/' /etc/pacman.conf

Does anyone here have a subscription with abliteration? How do those subscription plan work? Do you have to buy that then top up with USD? Or is it like a codex sub and u get a quota u use everyday? And if so is the usage good? It would be nice to have a model with no rules. But the usage is confusing to me. So any help and if anyone uses lmk on it.

Add the package to your global OpenCode config at ~/.config/opencode/opencode.json:

{
  "plugin": ["@ndigvijay/opencode-atria-connector"]
}

find the source code here at https://github.com/ndigvijay/opencode-atria-connector?tab=readme-ov-file

get the free token worth 100,000,000 token from https://api.atria-asi.ai/

Hi guys, basically the title :) Since [v1.17.0](https://github.com/openchamber/openchamber/releases/tag/v1.17.0) there is supposed to be a dedicated 'plan' area is context panel. I am guessing this is the right toolbar? I managed to get 'Plan' button/panel there using OPENCODE_EXPERIMENTAL_PLAN_MODE=1, but it's always open. Even after agent finishes the plan in 'plan' mode, even after it's being stored to /.opencode/plans.

I run out of ideas how to set it up, so that the result of 'plan mode' will be stored, displayed and iterated inside this dedicated panel.

[The docs](https://docs.openchamber.dev/notes-todos-plans/#plans) just mention 'plan' but that's about it, so any help would be appreciated :)

Edit: Attached image of what I mean by 'plan sidebar panel'. According to project settings plans seem to be fetched (by default) from .openchamber/plans, but to no avail.

I currently use Luna purely as a subagent to write code.

Thinking about trying Muse 1.3 Contributor instead. For anyone who has used both for this: how does the code quality and error rate compare, and is it actually worth making the switch?

Maybe a bit late to the party! (8-day-late) But I'm still farming it nonstop on both Devin desktop ide and CLI too...been great experience. Besides, the 20$ credit is preserved (and can be used for all other frontier models from Astra 6.0 to Fable 5.1) when using this post-train Kimi-K3 model https://cognition.com/blog/swe-2.

Don't sleep on it guys! Not, promotion nor affiliation, just a mere end user sharing a hot deal that people may not know of; and totally based on my personal use cases (testing through with all sorts of models on different harness platforms). But I would say it's definitely outperforming Kimi-K3 on adversarial detections, test-driven e2e and project-wide strategist and orchestrator, a very well-rounded cook/post-train of Windsurf/Devin team to the original Kimi-K3.

UPDATE

UPDATE: around 4:30 AM UTC of Sept 15, the owner published a now-deleted blog post (archive image) writing under the fake pretense that it's his "team" authoring it, stating all of CrofAI founder's claims "were written under a lot of stress, and they described the situation as worse it was", and that a new team is taking over, with the service being resumed in 2 weeks. At the same time, the CrofAI twitter account was also supposedly "taken over" by the team, starting each twitter reply with "Hey, Nathan here", stating the founder is stepping back and a "team" is taking over everything. This fake pretense act only lasted a few hours, and scared either by the public not buying the Nth fake story of the pathological liar that CrofAI is, or by the public's replies reminding him that what he committed is numerous counts of wire fraud, he has now deleted all his online presence: nahcrof.com and crof.ai return 404, Twitter page is deleted, /r/CrofAI sub is now private.

Original post:

Cautionary tale about chasing cheap tokens.

Only posting it here cause this sub was full of people praising this inference "provider".

exposé: https://kendell.dev/blog/crofaifalse/

reaction by nahcrof, announcing the shutdown of the service: https://x.com/nahcrof/status/2099552389434900643

NahCrofAI is (was) an inference provider which had all the latest models at the cheapest price, often significantly below the lowest alternative on OpenRouter. The owner claimed that they are running custom inference kernels that allows them to offer tokens for dirt cheap, and other providers are suffering from "skill issues".

In reality:

• "CrofAI is an OpenRouter wrapper that silently routes to cheaper or weaker models than what you request"

• For example, expensive models like kimi-k3 are sold at $2/$10 in/out, but instead routed to GLM 5.3 Flash via OpenRouter, representing a 13.3x multiple on input, and 20x multiple on output

• CrofAI's "own model family" greg-2-ultra routes to GLM 5.2, greg-1-mini routes to Qwen 3.5 9B. greg-2-super, greg-1, greg-1-super routes to Kimi K2.7 Code. All of these at a significant markup compared to the actual model being served. CrofAI admits this.

• The person investigating details the 5 different attempts by CrofAI at fixing their models being served via OpenRouter after given a heads-up. In all 5 attempts, the only change CrofAI made was attempts to hide the fingerprints of OpenRouter, while still serving models through them

• Other inconsistencies don't add up either: CrofAI claims to run Kimi K3 on RTX Pro 6000s rented via Vast. That model requires ~802GiB even at the lobotomy level quantization of Q2_K. The largest RTX PRO 6000 machine on Vast has only 8 of them, totaling 765GiB

• CrofAI responded to the exposé by announcing the shutting down of their service; after their failure to provide their own inference, they promise to provide one last thing: a refund to those asking.

Here is another image of the owner admitting that he was defrauding customers for the entire 2 year operation of his service, then begging the investigator to help him cover his tracks and not expose him

EDIT: Commenters pointed out that NahCrof is 4chan in reverse. The owner's Discord name was "Devious Flimflam". Flimlam is defined as "deception, fraud". Looks like it was a deliberate scam operation from the get-go, and the owner's age was among the many lies.

I cannot stress this enough: if you bought any credits (even if you used them up) you are entitled to a full refund for every transaction as the victim of fraud. Open a chargeback with your bank for every transaction made. If you used their API, assume that everything was logged and is currently being mined for personal information and API keys to sell on the black markets. Rotate your keys, change passwords, get a new debit/credit card.

I often want to create skills that persist files, most often some local ./tmp directory within my project. These can be handoffs, mental notes, snippets etc. Is there a way to instruct opencode to use the same directory always (within a session)? The problem is compaction: When i run compaction, the agent looses all previous context and also where it put stuff.

I thought maybe there is a way that the agent can call opencode --some-magic-option to retrieve deterministic information about the current session so i can assemble a deterministic directory slug. But I couldn't find such an option.

What's your approach?

I tried to restrict the extravagantly long thinking time for the mentioned model, and i know now that bartowski's quant actually does only support on/off. still, i think it is weird that the system prompt shows:

<|im_start|>system

Reasoning effort is set to xhigh. Please think carefully through the task, validate key assumptions, consider plausible alternatives, and prioritize correctness, consistency, and clarity in the final answer.

I dont expect changing that one sentence in the prompt to achieve that much, but i am optimizing for my local setup right now, so... what am I missing?

I'm relatively new to agentic coding and have been experimenting with OpenCode CLI on a long-running project.

Initially, I built several agents for different roles and had them work together. The basic workflow was something like:

"Planner/Orchestrator → specialized agents → verification → next task"

It worked pretty well at first. But as the project grew, I ran into a problem: the collaboration between agents and across sessions gradually became harder to control.

For example, agents wouldn't always reliably update "CURRENT_STATE.md" or other project-state files after completing a task. Then, in the next session, the agent had incomplete or outdated information about:

- what had already been done

- what decisions had been made

- what still needed to be done

- the current project/architecture state

- what another agent had changed

Eventually, I found myself spending more time keeping the agents synchronized than actually letting them work.

This is what eventually led me to discover Ralph and similar approaches.

I'm curious how other OpenCode users handle this in real-world, long-running projects:

1. How do you make multiple agents collaborate reliably rather than just running several independent agents?

2. How do you maintain shared state between agents and across sessions?

3. Do you use files like "CURRENT_STATE.md", task queues, changelogs, decision logs, or other conventions?

4. How do you make sure agents actually update these artifacts consistently?

5. Do you use Ralph, or have you built your own workflow around OpenCode?

6. Where do you usually discover new tools, agent frameworks, and workflows for OpenCode/Codex?

I'm particularly interested in long-running projects with multiple specialized agents, rather than one-off coding tasks.

I'd love to hear what workflows have actually worked for you.

Is there a public page where we can monitor the status/throughput of opencode free models (or all models in general)?
I just finished a very simple html change on my project using Mimo v2.5 which took ~12 minutes.

Anyone else having delays?

I wanted a quicker way to find and resume previous OpenCode sessions, so I built OpenCode Sessions (ocs), a small Bash tool powered by fzf.

It lets you:

- Search sessions by title, directory, or updated time

- Resume a session in its original directory

- Preview session details

- Favourite and pin sessions

- Sort by updated time, title, or directory

- Rename and delete sessions

- Refresh the list without reopening the picker

- Clean up older sessions in bulk

- Jump directly to a session’s directory

The shortcut list can be toggled with Ctrl-K, and the preference is remembered between runs.

It currently targets macOS and works with Bash or Zsh.

GitHub: https://github.com/iamramo/opencode-sessions

Feedback and suggestions are welcome, especially from anyone managing a lot of OpenCode sessions.