[FEATURE]: custom config path to also support agent definition (via markdown) #3432
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
I would like to use a different path for all of my opencode's configuration.
Currently, I am seeting OPENCODE_CONFIG as an env variable as suggested in the docs, and it works well.
However, OPENCODE_CONFIG should point to the json file rather than my custom folder, which made me suspect it won't pick up any agents defined in my {OPENCODE_CONFIG}/agent/*.md dir.
Sadly I checked this out and I am right.
Feature ask is to allow agents be defined in markdown in a custom directory path.
I believe a clean way to handle it is to have OPENCODE_CONFIG to point to an entire opencode config directory, which can include any existing or future configuration, agent file being among this.
My current workaround is to use the json to define agents.
Thanks for making such an awesome tool!