Weave fails to load and register agents on Opencode v1.3.13

[rothnic]

I discovered this after tracing down a separate issue with v1.3.13 in terms of kimi for coding kimi k2.5 failed tool calls. None of the custom commands or agents are really loaded, though they show up for the ones in my weave config file that have some customizations (model, prompt append, skills).

The thing I initially noticed was the Loom agent didn't show Loom (Main Orchestrator) when selecting it for a new session, just Loom, and noticed /start-work wasn't there anymore.

---

Edit:

Just noticing that I was getting a separate Loom agent due to setting the model, prompt append, and skills for Loom in the config file. So, it seems to not be overriding the actual Loom agent.

[pgermishuys]

Thanks for reporting this. Not really sure what's going on as this was first reported in the opencode desktop client. I tend to hold off on updating opencode as there appears to be breaking changes quite often with new releases.

Digging into this now.

[rothnic]

I'm also dealing with some odd Kimi for coding API provider issues that are confusing things though I still have been having intermittent issues where the weave plugin doesn't appear to initialize correctly. As of the last 12h or so I've seen this less as I've updated again to the latest opencode version.

[pgermishuys]

Would you mind sharing your weave-opencode.jsonc config, anonymizing any sensitive information? Apologies for the delay in getting back to you on this.

[rothnic]

Sure, and absolutely no problem. I just wanted to share it in case someone else experienced the issue. Overall, I'm chasing some issues with the kimi model and while I can't find anything about my setup that would be causing issues, i'm going to probably just have to start clean and bring pieces back in. The only plugins I have is cc-safety-net and weave, then a number of skills.

I just started using weave and had an agent read through my skills to generate this initial config, so some of it might not be super well thought out, but should give you an idea. It worked without issue for some time, but yeah it has been going in and out of weave initializing correctly. Almost feels like a timing or race condition type issue, which could be influence by my particular opencode config and/or state data, etc. My opencode db, for example, has grown quite large and probably need to do something with that.

https://gist.github.com/rothnic/f2d88e9463fd58f0afd16b9426751d39

[rothnic]

Let me do some more testing to isolate things further so i don't send you down a chase. I'll try to create a clean config and add things in until i can figure out what is going on.

[pgermishuys]

Would you mind downloading weave 0.7.5 and running /weave-health and telling me what you see?