Remix.run Logo
▲ Degorath a day ago

Can you give an opinion on its communication style?

▲johnshahbazian a day ago | parent [-]

It's succinct and easy to understand. Some examples:

"The UI currently bypasses universal search when a ranked row is clicked, and the backend’s paginated family response can replace partial results with an error. I’m narrowing the fix to route ranked rows through the shared search and preserve the usable family when the request scope changes."

and

"Yes. JevK5 matches Qwen because Stark classifies it as the Qwen3.5 / 3.8 family.

That family metadata is included in installed-model searching at StarkApp.swift, but isn’t always visible for a single-model group. Hovering the row should reveal “Qwen3.5 / 3.8” in its details.

Its public Hugging Face metadata also declares qwen3_5_text and base_model:Qwen/Qwen3.5-4B, so a catalog match is valid too. It’s not a bug; the confusing part is that the matching metadata isn’t displayed prominently."

▲Degorath a day ago | parent [-]

Very cool, thanks for the examples!

If you had to compare it to sol or opus, is it more easy to back-and-forth with? Imo opus devolves into word salad quite easily.

▲johnshahbazian 3 hours ago | parent [-]

Its better than Opus, definitely. Sol ends up summarizing the conversation at the end fairly well - I've never felt any sort of annoyance with it. But I would say that Code 2 is maybe a bit better for communication. It gets right to the point.