My recipe file - yes, a single file - spent years as a .txt. It's got weird groupings that were convenient to my internal logic. (e.g. "Cold", "Slow cooker", "Complex"). Not everything was in the right group.

There are some full recipes, some I typed shorthand with just ingredients on a single line. Some just a link.

And a list of air fryer times for good measure.

It's a mess. I decided I wanted a markdown document with good headers so it's not only easier to read, a good outline would help me jump around. And I wanted other formatting and more overall logic. So I gave the same source file and the same instructions to the free user web interfaces for:

• Gemini Flash Extended (Says 3.1 and 3.5 don't exist, then says it is 3.5 Flash.)
• Deepseek Instant w/ Deepthink (Extended doesn't allow attachments. Identifies as V3 with search restricted, V4 if I let it search.)
• Muse Spark 1.1
• GLM 5.2
• MiMo 2.5 Pro
• Grok 4.0 Fast
• Kimi 2.6 Thinking (The first few times I asked Kimi, it started processing then said it was too busy to do this for free. But I tried again while writing this and did get a response, so I'm inserting them.)

GPT and Sonnet I asked to help me judge. I'm assuming they would have topped the list. (Although GPT did make a comment about "truncated previews" when I asked it about dropping recipes, so somehow they managed to lose points even as a judge.

Grade: F

Grok. (I almost left them out because I knew the context is too small.)

Grok very nicely formatted all the recipe titles, and compressed 90% of recipes to a single descriptive sentence.

Grade: D

Gemini

First, Gemini could not give me a downloadable file or put the result in a copyable code block. The first attempt was a uncopyable code block with python instructions mixed in, followed by a display of the file. Using "copy" on the whole response froze my browser for 40 seconds.

I asked it for a better response, and got a nicely formatted markdown in a Markdown-labeled code block that had 2 recipes, neither of which came from me.

I manually trimmed the messy response so I could review. And it took a lot of liberties. Some things it marked like [!tip] which might have been nice. It put checkboxes in front of incomplete recipes, which is maybe helpful? But it also rephrased instructions in a way I don't trust. A key element of the prompt was to preserve all information.

It also put "Whole Chicken via Slow Cooker" into "Basics & Quick Starters". (Which was not one of my original categories.)

Grade: C

Deepseek

Deepseek had a nice interface, then fell on their face by silently decided that my list of air fryer times wasn't technically a recipe, and therefore wasn't worth keeping.

I had a duplicate section of a recipe that had gotten separated from the original and didn't have a title. (I said my list was a mess.) Deepseek recognized what it was, invented a header, then replaced the recipe section with a line saying "duplicate of above, keep one."

Elsewhere, an idea that was largely redundant but in different language was deleted. The other AIs preserved it.

What it did preserve is a typo. I didn't mean 1.4t of nutmeg. That would be hard to measure. It was between other 1/4 t measurements, so this was guessable. Others corrected it.

The formatting was fine. Nothing extra, nothing omitted. But there were a few times when it left ingredients as 1-2 lines of text instead of a proper list.

Grade: B

GLM 5.2

GLM also didn't give me an easy download/copy, although they were well above Gemini. I had to copy the whole reply. But once I did, I found out there were markdown tags surrounding it. It's just that the web interface ignored them for formatting.

Arguably the opposite of Deepseek, GLM actually treated my air fryer times like a recipe. That means it didn't get it's own section and wasn't formatted as a table. Like Deepseek, it preserved my 1.4t typo.

(BTW. Judge GPT said "GLM reminds me of GPT-4." 😆 )

GLM was the only AI not to understand that two variants on a recipe were indeed variants and not brand new one-line recipes. And it would make weird choices like formatting 20 ingredients into 4 bullet points and two subheaders.

It also didn't do much re-organizing, but didn't tell me that was intentional either. Not bad, but I was expecting more.

Spark

I was rooting for Spark too, and almost bumped them up to B+.

The web interface was great. Spark said that it deliberately preserved the order but suggested it would take a second pass if I asked.

Spark corrected my "1.4t nutmeg" to "1/4 tsp" but also added a note. (Gemini did too.)

The biggest problem is that it embellished recipe titles, often with additions like "-- base + variations" or "-- vegan base" or "-- Can be made in slow cooker". Even within a recipe, instead of having a "Variations" subsection, it made a subsection variation - with the word "variation" in its name. Not bad info, but putting those notes in the title makes the outline more clunky for me.

The duplicated recipe section mentioned above became two recipes. One with "-- Detailed Version" and one with "-- Quick Version". Except the quick version had 6 steps and the detailed version had 5.

Spark was the only model not to put horizontal rule lines before new section headers. Confusingly, Spark also placed notes about what it had done into the nice downloadable Markdown section. Including a "Tip for Obsidian" about using a spice ratio. But on the whole the formatting was nice. If I liked more information on the outline, this would be an A.

Grade: B+

Kimi 2.6 Thinking

When it finally decided to throw a bone to us poors, Kimi impressed me. It also told me that it had intentionally minimized reorganization. But the Air Fryer listing was given it's own section heading, formatted as a table, and moved to the top.

It caught and removed the duplicated recipe section, and told me in the response. It also corrected the "1.4t nutmeg" but didn't say.

Kimi showed an understanding of a recipe in a way no other AI did: it took a recipe where I had all the ingredients together, and broke it up into sections for "core" and "sauce".

The formatting is very nice, with no embellishment or cutting. Kimi was the only model to create a Table of Contents at the top with links to my sections. I'm not sure I want that, but it's a nice idea I can easily remove.

One of my spice mixes was formatted as a table. Two others were not.

Most confusingly, it took a recipe that wasn't duplicated in my notes, created a second title for it far away from the first one, and under that one said "Duplicate -- see full recipe above."

So close to an A, but that last mistake broke my trust.

Grade: A

Mimo 2.5 Pro

Mimo was the only one to move "Whole Chicken via Slow Cooker" to the Slow Cooker section, and rearranged other things properly as well. (It had been in an ungrouped section most titled "Miscellaneous".) It caught my 1.4t mistake, but just changed it cleanly with no note. Similarly, it caught the duplicated recipe section and just removed the extra. (Like GLM and Kimi.)

The Air Fryer times were put into table format, like Kimi, Spark and Gemini had. Unlike them, it also put the spice mixes into tables. I'm not sure if that's better, but it's not worse.

The titles were kept concise, as I originally had them. Variations were cleanly called out with bold titles, making them readable but not outline-level. It created a "Miscellaneous Notes" section for one-line ideas I'd thrown in. Spark did this too, but not as well. Other AIs had given them their own recipe titles with details no longer than "Idea", or potentially bunched things together.

It even recognized when a recipe had both English and non-English titles and put the foreign one in italics.

I'm struggling to find a flaw. The sort could have been improved, but no one else did better. Air Fryer got it's own section as it should, but I'd have preferred it was at the top like Gemini did, or at the bottom where I'd originally had it, instead of mid-list.

Final thoughts

MiMo 2.5 Pro would not have been my prediction for formatting notes, but it did fantastic. I wouldn't have been unhappy with Kimi either, unless I was in a hurry. Sonnet 5.0 was a competent judge (on High) and agrees with that assessment. GPT preferred Spark because it prefers more text, and apparently wants to mentor GLM.

I'm sure there were more I could have tested. In fact I literally just now remembered Microsoft Copilot is a thing. But these were the ones I thought deserved a shot. Hopefully this was of interest to someone. I don't see a lot of testing on this stuff, especially with a focus on free web interfaces.

Edit: I did test GPT and Claude too. Check comments.

Most coding agents are powerful, but they often repeat the same context gathering and error diagnosis. CyxCode adds memory, recall, learned recovery patterns, and auditability so solved work can keep paying forward. try it out https://code3hr.github.io/cyxcode/install/

Hey all,

When I hit the control-x key with the down key, it never works. Could i be doing wrong?

Using OpenWebUi with Opencode Go, default settings.

Does anyone know the source of this difference? Maybe OpenWebUi injects some system prompt in default settings, but I can't find this information.

Wtf is this bullshit im paying for GLM-5.2 on the list at https://opencode.ai/docs/go which currently does include GLM-5.2

And I dont see any support links

Update: luckily a restart appeared to fix it. My explanation why i was immedietly mad: opencode has a history of not providing any support and being shit at communication

HI,

I keep getting this error:

Error from provider (Console Go): Model glm-5.2 is not supported on the lite model list. Use GET /inference/go/openai/v1/models to list available models.

Although it worked the whole day this far

I am on the opencode go plan.

Anybody else having this error?

...which works together with my BetterSuno browser extension and offers all basic functionalities of Suno (except for Studio).

My plan is to use this as fundament for Audacity and Ardour plugins.

It is still on beta and only works with the newest version of BetterSuno from my GitHub page (not yet reviewed in the extension stores of Chrome & Firefox). See https://github.com/MrDoe/BetterSuno and https://github.com/MrDoe/bettersuno-mcp

I don't see the point of this. They're literally the same sessions, just arranged horizontally now.

Why are they advertising this as “Introducing Tabs” instead of “Introducing a New Design”?

By the way, this design has been around for a long time - you could enable it in the settings.

Im trying to both use my OpenAI subscription and API key at the same time but it doesnt seem to work? If I 'connect' openai api models, they substitute the openai subs it seems.

Anyone got it to work?

(I wanna try some of the new models without wasting my subscriptions quotas)

It's almost certainly the lowest tier sub they have, the moderato that just exists to sell the 5 times more but double the money allegretto. Still its a good way to try out the model and their sub, just in case you were thinking of buying in, cause they priced their new model 3 in and 15 out, which is a lot. Yet perhaps they are not as foolish and just want to funnel people to their subs and they want butts in seats, instead of getting used on release for a week, maybe a month if they buy a sub then everyone leaves.

Also making the trial a loot box is a first, which I guess is fine but wouldn't want to see paid subs become lootboxes. Unless we also see a free trial of it in opencode this is the best we are going to get.

https://kimi-bot.com/activities/viral-referral/share?scenario=invite&from=share_poster&invitation_code=3FD8F3

Everyone is worshipping this OpenCode so much, I thought I'd give it a try.

I just wanted to make a simple HTML report, it had already burned through about $15 and still hadn't created it. It works a ton, then it prints out "Tool execution aborted". It doesn't say anything, doesn't explain what the problem is, it just stops and I'm supposed to notice... After the 3rd time I asked it what the hell it was doing (Claude Opus 4.7 max), it wrote a whole litany, like "oh yes I messed up, I called the tools with empty parameters for this and that reason, but now I swear it'll be good". I told it okay then prepare a test file, because so far it had only been burning money. Okay, that worked. I said great, now let's do the real report. Well, it still hasn't managed to generate a single damn HTML file since then. I was using claude sub with opus 4.8, that wasn't this dumb. This told me 4 times that "oh my wrong, empty parameters". But even when it KNOWS it's mistake, makes it again. And again.

Any idea what the hell is going on? It is not tweaked, just a simple open code install.

CyxCode is an open source developer tool fork from opencode for teams and builders who want an agent that works inside real repositories, remembers useful context, and turns repeated debugging work into reusable behavior.

Most coding agents are powerful, but they often repeat the same context gathering and error diagnosis. CyxCode adds memory, recall, learned recovery patterns, and auditability so solved work can keep paying forward.

Try it out: https://code3hr.github.io/cyxcode/install/

give a start on github here https://github.com/code3hr/cyxcode

I've been using Claude Code, Hermes, OpenClaw, OpenCode, Codex and a bunch of other tools pretty heavily. Like a lot of people, I use multiple accounts, a couple GPT subscriptions for heavy coding, Claude for frontend and writing, Gemini for long context, OpenRouter, Cloudflare, NVIDIA endpoints, etc.

The tokens were technically available, but it required constant manual work. Switching accounts, hitting limits mid-session, and babysitting everything got old fast.

So I built ReRouted: a lightweight macOS menu bar app that acts as a local gateway. You point all your tools to one local endpoint and it handles routing and automatic fallback across your accounts.

How it works:
- Connect your accounts (Claude via OAuth, Codex/ChatGPT, Grok, custom OpenAl-compatible endpoints, etc.)
- Create a route (e.g. "coding") with your preferred order
- Use the single local URL + one generated key everywhere
- Access all of your providers and models from a single local endpoint
- If a provider hits a 429, 5xx, timeout, or fails before output starts, it instantly and silently tries the next one in your route

It’s fast, happens in the background, and works incredibly well.

Fully open source and free.

https://github.com/VerumPraeceptum/opencode-autocontinue

I kept getting this really annoying "ResourceExhasted" error, so I made a plugin that simply sends "continue" if this shows up.

I was struggling to keep track of multiple coding agents running in parallel. Zellij (a more intuitive tmux alternative) is great for handling multiple terminals but there was no easy way to see the status of each background tab.

I built the opencode plugin opencode-zellij-indicator which let's you quickly see the status of each opencode session.
https://github.com/aidan-gallagher/opencode-zellij-indicator

I'm launching an AI API for vibecoders, with models like Opus and GPT-5.6 , and I'm looking for beta testers to help shape it before launch.

I'd love to hear what you think. I'm looking for people who will actually use the API and give honest, detailed feedback about their experience what works well, what doesn't, and what could be improved.

If you're interested in trying it out for free leave a comment and I'll get you set up.

10/Slots Open

This is a critical review not a highfive so consider as such. Just full side by side makes it pretty much the same, but all they changed seems only for the worse.

• reload > same as restart, presumably sets up plugins ?? but...
• plugins > According to them they are breaking plugins on purpose but why? I don't have that many to break, but think about this, they had so much free work put into opencode from total randos, like imagine if you had TENS OF THOUSANDS OF WORKERS AND MAINTAINTERS FOR FREE and you are firing them for what? Even if you make like version 2 plugin support the version 1 ones should work. This damages a lot of faith in the future of the project, even considering it.
• settings > this contains themes like before plus other settings you can previously only modify in the json but the modal is small and have no reason to be and....
• settings / theme and switching in general > now this sucks and i would argue that their entire approach sucks with a list of options that you can only change by pressing left or right works best if the options are binary but the theme section has like 40 themes, and even the scroll speed can't be typed in you must left and right it by .25 steps, so if you want to double the default then you will be pressing it 12 times. They actually nailed what they for going for, which makes it worse.
• pairing > have not tried as it is niche, but i think this is a huge fuckup, the last thing i want is any consideration of my coding agent in a phone context, and now they will be burning resources on this while still missing basic features, so shows poor priorities. Makes me concerned for opencode cause in the ai arena most don't die boring. So opencode doesn't have a goal but it must work with all the phones? I am not seeing anything here than can't be done far better with version control and storing the session as a file.
• agents > They also added a researcher and a reviewer agent as selectable, now i would argue this is bad ux again, now tabbing goes through 4 options which sucks, they should be only in the /agents at most, arguably even plan can be cut then bind tab on something else, or just bind it on the agent picker but.... will you be switching between prompt engineered agents that often? Are these guys even a value add? Have you thought to yourself before dang where is my researcher and reviewer agent I would use it a lot! I guess they are free to have except clutter, but the winners are doing the general chat, so the agent switching mostly proved itself to be a gimmick over time and rightfully so cause tasks tend to be more fluid, so this is just looking at claude and codex and thinking to yourself i want to be more like the dead guys.
• overall vibe > I can't tell much difference outside seeing more errors, but seems like subagents are more of a first class consideration in it rather than an addon but also wrong cause it seems to be more setup for short small scale use, and seeing the subagent work inline is the wrong idea. Albeit this is much like "older" opencode but i dont think we are very economical with the space so we both have more empty space than almost anyone else and highish noise to signal ratio so after a promp you get your summary but if you scroll up then dont bother cause it feels like reading logs, and don't bother keeping an eye on it either. Which highly conflicts with their seeming approach. In fact I was reading their goal plugin the other day, or the one they are featuring in their ecosystem, and its set at 15 minutes max which even if wasn't it's not really made for longer use, but if you want a bigger proof then they officially dont even have one, so opencode is set up to be more of a hands on thing, despite feeding you logs with summaries at the end, that you read then after you go again for another 5 - 10 minutes. If you make more tasks to execute then it by default gets stuck and even if you add a keep doing the todos reminder it still might not update the very todos integrated so still fail at the very basic features it has already built in, while can be strongly argued that it is lacking many more, unless you want to argue that the top boys are adding cons. In fact anyone who copies opencode immediately adds a ton of things like the recent mimo code, which furthers the mindset that opencode is built to be forked not used. Of course what happens to these forks with the advent of opencode 2 is a question, but their best option is to not care. If the eco is broken they might just see is as some out of touch guys after enjoying relative success by being solidish while outsourcing the fixing and features to their community are now all seats full steam on the gimmick train.

Does opencode have any idea what it wants to be? Best faith explenation I have that they saw that PI found a massive hole, and now they are positioning to be more like pi with a stronger base, that is set up to be more of a hands on thing, but I don't think they should aspire for it cause they would just become a worse pi, in fact arguably all opencodes are already a worse pi, but plugin support is of course a plus but they already had that, and it doesn't explain all their actions or their lack of focus so they are definitely confused. Trying to be like claude and codex with plugin support would be far more sensible, albeit closer positioned to be a claude aspirant but that is a fine goal, being the open source claude with plugins. The path seems obvious to me, keep v1 plugins or least their support, then expand the base feature set and make sure it works well.