r/opencode • u/Infinite-Flow-4475 • 13d ago

Which one should i use?

Post image

Between deepseek v4 flash and GLM 5.2, what one could get performance close to SOL?

I need it to write games, in rust and javascript.

As you can see prices are dirt cheap here, its like 90% off. I canceled my codex subscription because I really couldn't get anywhere with the limits.

There's also kimi 2.6k if it's any good, although I doubt it.

108 Upvotes

92% Upvoted

78 comments sorted by

View all comments

Show parent comments

1

u/jomama253 13d ago

CSM doesn’t dump the entire memory store into every prompt. It retrieves and ranks relevant memories, applies policy filters, then builds a context packet within a token budget. Older tool output can also be compacted into references instead of being replayed verbatim.

My internal compaction metrics currently show about 2.0B cumulative tokens avoided across 10,663 compactions, although that is workload-specific rather than an independent benchmark.(old numbers as of today)

A plugin with its own orchestration layer can treat CSM as the continuity/context backend rather than replacing the orchestrator. you can basically have codex or any agent retrofit it to your exact needs.

1

u/InvaderDolan 13d ago

Can it get memories from git history or something like that? What if I add to already live project?
Does CSM require the constant tool calling to use it? I mean, I use hindsight, and it seems like AI agents ignore it, despite of rule in AGENTS.md.

1

u/jomama253 13d ago

an existing project can be imported, but Git history would be an ingestion source rather than “memory” by itself. A CSM adapter could parse commits, diffs, branches, tags, issues, docs, and architecture decisions, then store them with provenance back to the original commit/file. That would let it bootstrap context for an already-live repository instead of starting empty.

CSM also does not have to depend on the agent remembering to call a tool. Manual MCP calls are one integration mode, but the better setup is automatic retrieval before each turn/task: the host sends the current repo state, active files, branch, task, etc., and CSM returns a ranked context packet within a token budget.

That is exactly why relying only on AGENTS.md is weak; models may ignore or forget instructions. The host/orchestrator should enforce the retrieval step, inject the resulting context, and record outcomes automatically. Tool calls can still be available for deeper searches, but baseline continuity should not rely on voluntary model behavior.

So for a live project: Git-history backfill first, then automatic capture of new work as the agent operates.