anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 10:15:31 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Plannotator stops during execution, Exa search instability, and not auto-selected #4205

New Issue
Open
opened 2026-02-16 17:43:01 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 17:43:01 -05:00
Owner
Copy Link
Copy Source

Originally created by @ru3tyYT on GitHub (Jan 4, 2026).

Originally assigned to: @rekram1-node on GitHub.

Description

Bug Report: Plannotator stops during execution, Exa search instability, and not auto-selected

Environment

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

Plugin installs correctly and is present in:

~/.cache/opencode/node_modules/@plannotator

Expected behavior

  • Plannotator is automatically selected as the planner when installed.
  • After approving a plan, execution runs reliably to completion.
  • Search-related failures (Exa) are handled cleanly.

Actual behavior

  1. Manual Plannotator selection required

    • Even with Plannotator installed, OpenCode does not default to it.
    • I must explicitly tell OpenCode to use Plannotator, otherwise a different/default planner is used.

  2. Execution stops unpredictably

    • After approving the plan, execution starts normally.

    • When Exa search is invoked, execution may:

      • randomly stop,
      • appear to crash but then continue,
      • or enter an unstable partial state.

    • No clear fatal error is shown.

Notes

  • This is not an installation or config issue.
  • The problem appears tied to Exa search usage + planner runtime handling.
  • Failures are not surfaced or handled deterministically.

Summary

Plannotator installs and loads correctly, but:

  • is not auto-selected,
  • requires manual instruction to use,
  • and becomes unstable when Exa search runs, often stopping after plan approval.

Plugins

plannotator

OpenCode version

1.1.1

Steps to reproduce

Steps to Reproduce

  1. Install OpenCode and verify:

    opencode --version

    Output: 1.1.1

  2. Create global config:

    ~/.config/opencode/opencode.json

    {
  "plugin": ["@plannotator/opencode@latest"],
  "$schema": "https://opencode.ai/config.json"
}

  3. Clear cache:

    rm -rf ~/.cache/opencode

  4. Start OpenCode:

    opencode

  5. Trigger a planning task that uses search.

  6. Observe:

    • Plannotator is not automatically chosen.
    • Manually instruct OpenCode to use Plannotator.

  7. Approve the plan.

  8. When Exa search runs, observe that execution:

    • stops unexpectedly,
    • or crashes but continues in a partial/unstable state,
    • without a clear error.

Expected result

  • Plannotator is auto-selected.
  • Execution completes or fails cleanly with a clear error, even when Exa search is used.

Screenshot and/or share link

No response

Operating System

macOS tahoe 26.2

Terminal

normal mac terminal

Originally created by @ru3tyYT on GitHub (Jan 4, 2026). Originally assigned to: @rekram1-node on GitHub. ### Description ## Bug Report: Plannotator stops during execution, Exa search instability, and not auto-selected ### Environment * **OS:** macOS * **OpenCode:** 1.1.1 * **Plugin:** `@plannotator/opencode@latest` * **Config:** `~/.config/opencode/opencode.json` Plugin installs correctly and is present in: ``` ~/.cache/opencode/node_modules/@plannotator ``` --- ### Expected behavior * Plannotator is **automatically selected** as the planner when installed. * After approving a plan, execution runs reliably to completion. * Search-related failures (Exa) are handled cleanly. --- ### Actual behavior 1. **Manual Plannotator selection required** * Even with Plannotator installed, OpenCode does **not default to it**. * I must explicitly tell OpenCode to use **Plannotator**, otherwise a different/default planner is used. 2. **Execution stops unpredictably** * After approving the plan, execution starts normally. * When **Exa search is invoked**, execution may: * randomly stop, * appear to crash but then continue, * or enter an unstable partial state. * No clear fatal error is shown. --- ### Notes * This is **not an installation or config issue**. * The problem appears tied to **Exa search usage + planner runtime handling**. * Failures are not surfaced or handled deterministically. --- ### Summary Plannotator installs and loads correctly, but: * is **not auto-selected**, * requires **manual instruction to use**, * and becomes **unstable when Exa search runs**, often stopping after plan approval. ### Plugins plannotator ### OpenCode version 1.1.1 ### Steps to reproduce ## Steps to Reproduce 1. Install OpenCode and verify: ```bash opencode --version ``` Output: `1.1.1` 2. Create global config: ``` ~/.config/opencode/opencode.json ``` ```json { "plugin": ["@plannotator/opencode@latest"], "$schema": "https://opencode.ai/config.json" } ``` 3. Clear cache: ```bash rm -rf ~/.cache/opencode ``` 4. Start OpenCode: ```bash opencode ``` 5. Trigger a planning task that uses **search**. 6. Observe: * Plannotator is **not automatically chosen**. * Manually instruct OpenCode to use **Plannotator**. 7. Approve the plan. 8. When **Exa search runs**, observe that execution: * stops unexpectedly, * or crashes but continues in a partial/unstable state, * without a clear error. --- ### Expected result * Plannotator is auto-selected. * Execution completes or fails cleanly with a clear error, even when Exa search is used. ### Screenshot and/or share link _No response_ ### Operating System macOS tahoe 26.2 ### Terminal normal mac terminal
yindo added the bug label 2026-02-16 17:43:01 -05:00
yindo commented 2026-02-16 17:43:01 -05:00
Author
Owner
Copy Link
Copy Source

@ru3tyYT commented on GitHub (Jan 5, 2026):

also plannotator dev mentioned that opencode could fix this by enabling auto switching for the planning method. is there also a way to disable exa search as that is also breaking it.

@ru3tyYT commented on GitHub (Jan 5, 2026): also plannotator dev mentioned that opencode could fix this by enabling auto switching for the planning method. is there also a way to disable exa search as that is also breaking it.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#4205
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?