Visitar URL original
[Bug]: oh-my-openagent fails to load on opencode v1.14.32 (works on v1.14.30) · Issue #3758 · code-yeongyu/oh-my-openagent · GitHub
Skip to content

[Bug]: oh-my-openagent fails to load on opencode v1.14.32 (works on v1.14.30) #3758

Closed

Description

@9teeedev

Prerequisites

  • I have searched existing issues to avoid duplicates
  • I am using the latest version of oh-my-openagent
  • I have read the documentation or asked an AI coding agent with this project's GitHub URL loaded and couldn't find the answer

Bug Description

oh-my-openagent fails to work with opencode version 1.14.32. After upgrading opencode to 1.14.32, the plugin does not function correctly. Downgrading opencode to 1.14.30 resolves the issue — the plugin loads and works as expected.

This suggests a regression or breaking change introduced between opencode 1.14.30 and 1.14.32 that affects oh-my-openagent's plugin initialization or compatibility.

Steps to Reproduce

  1. Install opencode 1.14.32
  2. Install oh-my-openagent (latest version)
  3. Run bunx oh-my-opencode doctor — observe the plugin failing to load or function
  4. Downgrade opencode to 1.14.30
  5. Run bunx oh-my-opencode doctor again — plugin works normally

Isolation matrix:

Works:  opencode 1.14.30 + oh-my-openagent latest
Breaks: opencode 1.14.32 + oh-my-openagent latest

Expected Behavior

oh-my-openagent should be compatible with opencode 1.14.32, or at minimum the breaking change should be documented with a migration path.

Actual Behavior

On opencode 1.14.32, oh-my-openagent fails to load or function. No specific error message is displayed beyond the plugin not activating. Switching back to opencode 1.14.30 immediately restores full functionality.

Workaround

Downgrade opencode to 1.14.30:

# Install opencode 1.14.30 (example — adjust for your package manager)
npm install -g opencode@1.14.30

Operating System

macOS (Darwin 25.4.0)

OpenCode Version

1.14.32 (broken), 1.14.30 (works)

Additional Context

It is unclear whether this is an opencode-side breaking change or an oh-my-openagent compatibility issue. If maintainers can identify what changed between opencode 1.14.30 → 1.14.32 (plugin API, config format, initialization hooks), that would help narrow the root cause.

Activity

  1. Ethan0x0000 commented on May 2, 2026

    @Ethan0x0000

    +1

  2. darianstlex commented on May 2, 2026

    @darianstlex

    +1

  3. Dommage commented on May 2, 2026

    @Dommage

    +1

  4. HyeokjaeLee commented on May 2, 2026

    @HyeokjaeLee

    It seems this will be handled in the PR at anomalyco/opencode#25440.

  5. lazydog28 commented on May 2, 2026

    @lazydog28

    The @opencode-ai/plugin's Hooks interface is identical between v1.14.31 and v1.14.32 — the config hook signature has always been (input: Config) => Promise, receiving a Config object and relying on in-place mutation. This interface never provided an agent registration API.
    oh-my-openagent works around this by mutating config.agent inside the config hook — this is fundamentally a workaround, not a supported pattern.

    opencode core's initialization order is:

    1. Load opencode.json (config file) → parse config object
    2. Read agent definitions from config → register into core agent registry ← agents are "locked in"
    3. Load external plugins
    4. Call each plugin's config hook → oh-my-openagent tries to mutate config.agent

    Step 4's mutation only changes the raw config JS object, but Step 2 has already parsed agents into opencode core's independent data structure. The mutation has zero effect on the core agent registry.

    opencode core completed agent initialization before the plugin had a chance to register them.

  6. xianyuntang commented on May 2, 2026

    @xianyuntang

    +1

  7. shf-275599 commented on May 2, 2026

    @shf-275599

    +1

  8. diarworld commented on May 2, 2026

    @diarworld

    +1

  9. pibrei commented on May 2, 2026

    @pibrei

    +1

  10. Overdue-Lin commented on May 2, 2026

    @Overdue-Lin

    +1

  11. TheAsda commented on May 2, 2026

    @TheAsda

    +1

  12. noffolo commented on May 2, 2026

    @noffolo

    +1

  13. lninghaha commented on May 2, 2026

    @lninghaha

    +1

  14. fangzx2001 commented on May 2, 2026

    @fangzx2001

    +1

  15. Gioxaa commented on May 2, 2026

    @Gioxaa

    +1

  16. expiren commented on May 2, 2026

    @expiren

    +1

  17. the-kro commented on May 2, 2026

    @the-kro

    Is there a temporary fix we can make ourselves without having to revert to older version of opencode?

  18. PVLPM commented on May 2, 2026

    @PVLPM

    +1

  19. PVLPM commented on May 2, 2026

    @PVLPM

    Fixed in OpenCode v1.14.33

  20. libz1 commented on May 7, 2026

    @libz1

    +1

  21. libz1 commented on May 7, 2026

    @libz1

    +1

  22. acamq commented on May 7, 2026

    @acamq
    Contributor

    @libz1 please try opencode v1.14.33 or higher

  23. PVLPM commented on May 7, 2026

    @PVLPM

    @acamq Hi, just tried with new 1.14.41 on Electron build (no choice for Tauri) - still I get a lot of session error notifications while starting the OC and no OmO Agents once again... I revert back to 1.14.33 Tauri build...

  24. acamq commented on May 7, 2026

    @acamq
    Contributor

    @PVLPM please open a new issue with more details

  25. Dats4794 commented on May 18, 2026

    @Dats4794

    Still bugging, opencode cli is not usable by now.

  26. Alcatraz-Zhang commented on Jun 8, 2026

    @Alcatraz-Zhang

    Triggered this bug with opencode 1.16.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions