plugin json file missing

[ru3tyYT]

hey @backnotprop sorry for another issue creation, but after i cleared cache and deleted the claude version by doing
which plannotator
then getting the directory and do rm <directory>
when i try updating the plugin with the new @latest part, it seems that opencode.json is nowhere to be found, is there a command or something i can run to make one and then i can add the working plugin?
a new feature that could be cool is just maybe an installer app/script to run and it'll fully complete this for you

[ru3tyYT]

i just used mkdir command to make a plugin folder then made a opencode.json and put the plugin in there, should that work?

[backnotprop]

Hey @ru3tyYT, deleting the plannotator binary shouldn't affect your opencode.json - they're completely separate.

Where to put opencode.json:

Option 1: Project root (recommended)
Create opencode.json in the same folder where you run opencode:

{
  "plugin": ["@plannotator/opencode@latest"]
}

Option 2: Global config
Create at ~/.config/opencode/opencode.json - applies to all projects.

Quick setup:

# In your project folder:
echo '{"plugin":["@plannotator/opencode@latest"]}' > opencode.json

# Clear cache and restart:
rm -rf ~/.cache/opencode/node_modules/@plannotator

---

Troubleshooting - run these and share the output:

# 1. Check if global config exists
cat ~/.config/opencode/opencode.json

# 2. Check if project config exists (run from your project folder)
cat opencode.json

# 3. See what OpenCode is actually loading
ls -la ~/.config/opencode/
ls -la .opencode/ 2>/dev/null

# 4. Check the plugin cache
ls ~/.cache/opencode/node_modules/@plannotator 2>/dev/null && echo "Cache exists" || echo "No cache"

Your mkdir approach creating a "plugin folder" won't work - OpenCode looks for opencode.json in specific locations, not a custom folder.

If your config "keeps disappearing," that's unusual. Run the commands above and share what you see - that'll help us figure out what's happening!

I'm happy to meet with you over Google Meet or something tomorrow.

[ru3tyYT]

sorry for the late response, do you have a quick easy script/commands to easily open the json and add the plugin?

[ru3tyYT]

@backnotprop

sorry for the late response, turns out i was being stupid and was searching the opencode directory instead of the config directory, resulting in me never finding opencode.json. I located it and updated the plugin, but now when i try to do literally ANYTHING, for example, "make me an autoclicker".

I'll help you create an autoclicker for Mac. Let me first research the best approaches and understand what options are available. • Exa Code Search "macOS autoclicker Python Swift Objective-C auto click mouse automation" Code search request timed out • Exa Web Search "macOS autoclicker Python Swift Objective-C mouse automation 2025" Search request timed out lot mo ayalaya tha cuypant diractory to undorctand what dovelanmont anvironmant wo have available Let me explore the current directory to understand what development environment we have available.

i dont know if this could be a problem with just opencode or the plugin.

[backnotprop]

Seems like some issues with other plugins possibly

[ru3tyYT]

@backnotprop
i only have plannotator, do you know any troubleshooting to possibly fix this?

[ru3tyYT]

@backnotprop yes this is ai bug report to make more detailed

Bug Report: Plannotator stops during execution and is not auto-selected

Environment

• OS: macOS
• OpenCode: 1.1.1
• Plugin: @plannotator/opencode@latest
• Config: ~/.config/opencode/opencode.json

Plugin is installed and present in:

~/.cache/opencode/node_modules/@plannotator

---

Expected behavior

• When Plannotator is installed, OpenCode automatically uses it as the planner.
• After approving a plan, execution runs reliably to completion.
• Errors halt execution cleanly and are surfaced clearly.

---

Actual behavior

1. Manual planner selection required

   • Even with Plannotator installed and loaded, OpenCode does not default to it.
   • I must explicitly tell OpenCode to use Plannotator when planning
   • This feels unintended given that Plannotator is the only configured planning plugin.

2. Execution stops unpredictably

   • After approving the plan, Plannotator begins execution.
   • Execution then randomly stops without a clear error.
   • In some cases, OpenCode appears to crash but continues afterward in a partial or unstable state.

---

Notes

• Configuration and installation are confirmed correct.
• This appears to be a planner registration / runtime stability issue, not user setup.
• Failures are not handled cleanly and leave execution in an undefined state.

---

Summary

Plannotator installs and loads correctly, but:

• is not automatically selected as the planner,
• requires manual instruction to use,
• and stops randomly after approval.

This points to a planner selection and runtime robustness bug.

[backnotprop]

@ru3tyYT Manual planner selection required

Yes unfortuently this is a design thing, I think OpenCode devs would need to enable auto-switching

[ru3tyYT]

@backnotprop
so for the planning issue only thing that could fix is opencode devs enabling it?
also is there a way to disable exa search as it is breaking
lastly is there any reason/fix of why it just suddenly just stops.