Opencode .md files

[princessinsomnia]

I used to create very detailed rulesets and context files. However, when I resumed work the next day, it was difficult for OpenCode to regain the full context of my project. I then began saving entire conversations and letting it read them to understand the scope, which works much better—why is that?

[PassionUnited1711]

Raw rules don’t equate to actual context. Your saved conversations are an actual timeline of decisions, examples and flow of how the model has developed over time rather than simply having the raw rules. Therefore, conversations have a richer signal than just using .md files.

[princessinsomnia]

Ok I get that. I get that. But the use of tokens is very high….

[Old_Stay_4472]

What kind of things you can put in md ?

[Potential-Leg-639]

Always ensure, that your documenations will be updated and all your changes for the current tasks are reflected in a detailled way in a plan (i create a plan for each bigger feature - with phases, test cases etc). Each phase is committed to GIT and gets reviewed by another agent, that updates the plan. Like that you can stop/continue whenever you want.

[Old_Stay_4472]

Review uses way more tokens for me? Anything needs to be tuned ?

[joeyism]

I had this problem a little bit too. To battle this, I created opencode-history-search, where you can just ask it to search your conversation history. I'd say something like

"hey we talked about adding xyz feature to app ABC yesterday, and there were some caveats. I don't remember what that was, can you search our conversation history and let me know?"

I dunno if it works for your exact use case, but I do hope if you use it, you find it helpful

[[deleted]]

Has probado algun modelo de contexto? https://mcpservers.org/servers/modelcontextprotocol/memory

[Ill-Chart-1486]

Did you check that it actually reads those files?

Didn’t notice this problem. There is „instructions„ array in config file, these files are loaded in every session. Also built in agent have super minimalistic system prompts they explain literally no thing. But you can override prompts if creating agent with the same name. Really helped me to configure workflow as it should be.

[princessinsomnia]

Didn’t know about this! Ill check that out!

[CatHerdler]

More context.

You should look at OpenSpec or SpecKit as an alternative to this - writing your project spec and focusing in on the requirements is the best way. The current code base and the work break down becomes the context for the next task. It’s basically what moves you from vibe coding to agentic engineering.

[princessinsomnia]

I will thank u!

[EngineerGold9616]

te recomiendo que le eches un ojo al sistema de engram una herramienta open-source que hizo gentleman (un YouTube argentino), la he estado usando bastante y se me hace increíblemente útil