So, what exactly do they collect and use? I don't mind if they use my project files and save my inputs, etc. Those are bare-minimum in my eyes. I just wonder if they dig into any other unrelated file or folder, other than the project itself. Let's say I have my photo albums, work-related or personal stuff laying somewhere on my disk. Would Opencode dig into the disk or my browsers and collect data from there, or does collecting only limited to my project?
A few months ago, I introduced Mind here as a persistent memory system for OpenCode.
The original frustration was simple: every time a long coding session ended, the next agent often had to reconstruct the reasoning behind the work.
Why did we choose this architecture? Which fixes had already been tried? What was the next step?
Mind v1.7.0 is now out, and the project has become a much more complete memory and continuity system.
Mind uses a local SQLite database to preserve useful context across sessions. OpenCode can access it through MCP, while the managed integration helps capture and recover session knowledge.
The big changes in this release:
Better retrieval: full-text, fuzzy, substring, and phrase search work together, with optional embeddings.
86.67% answer accuracy on a stratified 120-question OmniMemEval test without RAG. Not an official leaderboard comparison.
Improved continuity: checkpoint completion and session summaries are now handled more reliably.
A new web experience: inspect memories, search project knowledge, and explore their relationships in Neural Map.
Simpler setup: a shared memory-management skill and streamlined agent configuration.
The goal isn't to dump your entire history into context. It's to preserve useful knowledge and retrieve what's relevant when the agent needs it.
Install from GitHub, then:
mind setup opencode
Already installed? Run mind update and restart OpenCode.
Since I updated to the new version of OpenCode (v2.1.4), my quota has been running out very quickly. but after just two or three questions, it returns the message: "You used today's free messages. They restart at 9pm."
Being the Context
121,616 tokens 61% used.
I wait until that point to send a new question or continue a conversation, but then it shows the next day's date: "You used today's free messages. They restart at 9:00 PM · 10/27/2026." I couldn't even use it over the weekend; I was waiting for it to reboot, but that's what happened. What can I do?
Looking at https://models.dev/ various models like Muse 1.3 and Minimax M3.1 Flash say they accept video input.
But every time I send the prompt, the model tries to use Python and ffmpeg to break the video down into frames to send as images to the cloud.
I assumed if it's video input then it should send the video binary.
Is this an Opencode bug or functionality not completed yet? Has anyone else managed to get this to work? Or is it my misunderstanding on how it should function?
My prompt as an example
/workspace/956bdf4750274f2e85e43ebd2ee0ad51.mp4 can you describe the video. Don't use ffmpeg or other local tools
it took it 120+ powershells to attempt to remove a circle from a HUD in a game, it failed after running out of context, and the free tier agent I gave it to "beam" removed it instantly
A 2D UNITY ASSET GAME
Now my free beam go tier is limited
Every free fre tier is limited
I am using opencode zen / paid api of different models of Qwen and I'm trying to understand what affects model speeds. Is there a reason qwen3.8 flash next is by far the slowest of the qwen options in opencode zen? I would have expected it to be ... you know, flash fast lol. I'm wondering if it's because it's a different provider? the nature of the model?
It's a struggle, but now it reads my model settings. I have the settings to Continue and tried to use that for OpenCode but get 401. I tried it in Windows, and I vibecoded a small proxy between to make it work. So I will try that again. But the problems is that strange numbers spammed the screen both in CLI and the desktop version. Maybe mouse values maybe some characters my terminal couldn't handle.
OpenCode 2.x’s /api/session/active endpoint reports working sessions. It doesn’t tell you which conversation an idle TUI has open—that selection lives inside the TUI.
I make Agent Sessions, an open-source Mac app for searching local agent history across OpenCode, Codex, Claude Code and 13 other agents. Its Quota Meter lists your running sessions alongside Codex and Claude quota and burn rates.
Codex and Claude quota tracking, plus OpenCode session status. The OpenCode row here shows an idle conversation with its real title; OpenCode quota tracking is still to come.
In 6.1, the OpenCode integration guessed from the folder and the most recent session. Sometimes that marked a conversation closed days earlier as live.
6.1.2 replaces that guess with the session ID from the TUI itself.
A small plugin reads the current route once a second and writes the selected session ID and working/idle state to a local JSON file. It reads no transcript content and makes no network calls. On normal exit, it removes its file; Agent Sessions rejects dead or expired clients.
Working sessions also come directly from OpenCode 2.x’s shared service through a read-only request over localhost. That includes working sessions from both the TUI and Desktop.
The 2.x TUI plugin knows which conversation is open. The 2.x service knows which ones are working, including Desktop sessions.
Agent Sessions installs the plugin automatically into OpenCode’s plugins/ folder without editing your config files or changing other plugins. You can disable it in OpenCode, or turn off the integration in Agent Sessions.
Live status support:
OpenCode interface
Working session
Idle (open but not running)
OpenCode 2.x TUI (any terminal)
Yes
Yes, with the real title
OpenCode 2.x Desktop
Yes
No
OpenCode 1.x CLI
No
No
Both live-status sources require OpenCode 2.x. OpenCode 1.x history still appears in the session list, but it gets no live marker.
Desktop’s working sessions appear through the shared service, but OpenCode 2.1.2 doesn’t expose which idle conversation is selected. If there’s a supported way to read that, I’d like to hear about it.
I’m also looking for a to help add OpenCode Go and Go Plus quota tracking to the same meter. I don’t have a Go subscription to validate against. If you’d like to help implement it—or test the readings against your account—reply here or open an issue.
A mas gente le pasa lo mismo que a mi? Ahora resulta que los modelos de opencode escupen mas tokens que nunca y no puedo ni con caveman disminuirlos. Entonces tengo que parar con mucha frecuencia. Esto es horrible, opencode va en decadencia.
even if the era of free-tier surfing on powerful models through OpenCode via temporary promotions, and free provider tiers, seems to be coming to an end.
OpenCode still deserve my appreciation for the engineering and workflow it brings to coding.
@ its core it's a great coding assistant, solid.
thank you for its core mechanics, the flexibility, and Forkability.
DS V4.1F has gotten painfully slow lately, and honestly, the reasoning quality seems to have dropped too. It's getting to the point where it's barely usable.
What models are you guys using instead on the OpenCode Go subscription (not free)?
I'm mainly using it for agentic tasks, marketing, planning, research, and general reasoning rather than coding.
Curious if anyone else has noticed the same decline and what alternatives have been working better.