You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know it sounds unintuitive, but I've found that if you're working in a team of people that don't use the same SDD tool as you then, you really need to store the planning artifacts outside of the code repo.
I use the basicmemory mcp, which lets me store segregate notes into projects, and projects can live anywhere on my filesystem.
I'm in the process of refining my cmds and skills there for opencode in such a way as to allow the storage backend to be pluggable via a skill.
It seems like agent-os assumes it can just write files to disk in the same repo you're working in. which is fine for solo devs, but for those that work in teams, it's a blocker
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I know it sounds unintuitive, but I've found that if you're working in a team of people that don't use the same SDD tool as you then, you really need to store the planning artifacts outside of the code repo.
I use the basicmemory mcp, which lets me store segregate notes into projects, and projects can live anywhere on my filesystem.
https://github.com/zenobi-us/dotfiles/blob/master/devtools/files/opencode/skills/projectmanagement/storage-basicmemory/SKILL.md
I'm in the process of refining my cmds and skills there for opencode in such a way as to allow the storage backend to be pluggable via a skill.
It seems like agent-os assumes it can just write files to disk in the same repo you're working in. which is fine for solo devs, but for those that work in teams, it's a blocker
Beta Was this translation helpful? Give feedback.
All reactions