[Bug]: OmO does not auto update as it should, I updated manually with npx install and it still throws errors using GPT-5.4 with Sisyphus

[jeremyakers]

Prerequisites

• I will write this issue in English (see our Language Policy)
• I have searched existing issues to avoid duplicates
• I am using the latest version of oh-my-opencode
• 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

First: OmO will not auto-update on it's own. It throws this error when I start OpenCode:

INFO  ... service=plugin path=oh-my-opencode loading plugin
WARN  ... service=bun pkg=oh-my-opencode cachedVersion=3.8.4 Failed to resolve latest version, using cached

After updating to 3.11 manully using npx install: I switched Sisyphus to GPT5.4 as documented in the release notes and new docs.

However: I am still seeing this error message to NEVER use GPT with Sisyphus:

I also noticed the latest version is actually 3.11.1, but npm will not update to it:

$ npm view oh-my-opencode@latest

oh-my-opencode@3.11.1 | SUL-1.0 | deps: 16 | versions: 177
The Best AI Agent Harness - Batteries-Included OpenCode Plugin with Multi-Model Orchestration, Parallel Background Agents, and Crafted LSP/AST Tools
https://github.com/code-yeongyu/oh-my-openagent#readme

keywords: opencode, plugin, oracle, librarian, agents, ai, llm

bin: oh-my-opencode

dist
.tarball: https://registry.npmjs.org/oh-my-opencode/-/oh-my-opencode-3.11.1.tgz
.shasum: f55fe94ab1e749322f7963fc8dc0f1d7666f33b0
.integrity: sha512-cASqc0FzBIc2kMsimGff5WR0CQCAj+02L5ZgK+6CV/Uono73V2soFr3lV9kJsp/iqvQ1qfhchIDQamdgbCzhNQ==
.unpackedSize: 5.7 MB

dependencies:
@ast-grep/cli: ^0.40.0                @modelcontextprotocol/sdk: ^1.25.2    detect-libc: ^2.0.0                   picocolors: ^1.1.1                    
@ast-grep/napi: ^0.40.0               @opencode-ai/plugin: ^1.2.16          diff: ^8.0.3                          picomatch: ^4.0.2                     
@clack/prompts: ^0.11.0               @opencode-ai/sdk: ^1.2.17             js-yaml: ^4.1.1                       vscode-jsonrpc: ^8.2.0                
@code-yeongyu/comment-checker: ^0.7.0 commander: ^14.0.2                    jsonc-parser: ^3.3.1                  zod: ^4.1.8                           

maintainers:
- code-yeongyu <code.yeon.gyu@gmail.com>

dist-tags:
beta: 3.0.0-beta.16  latest: 3.11.1       

published 2 hours ago by code-yeongyu <code.yeon.gyu@gmail.com>
$ npx oh-my-opencode -v
3.11.0
$ oh-my-opencode -v
3.11.0
$ npm install -g oh-my-opencode@latest

changed 114 packages in 32s

30 packages are looking for funding
  run `npm fund` for details
$ npx oh-my-opencode -v
3.11.0

Steps to Reproduce

1. Configure Sisyphus to use GPT-5.4 which is supposed to now be supported.
2. See error saying to NEVER use that model with Sisyphus

Expected Behavior

If GPT-5.4 is really supposed, it should not error.

Actual Behavior

Didn't I cover this above?

seeing this error message to NEVER use GPT with Sisyphus:

Doctor Output

$ npx oh-my-opencode doctor

 oMoMoMoMo Doctor 

 ⚠ 3 issues found:

1. Loaded plugin is outdated
   Loaded 3.8.4, latest 3.11.1.
   Fix: Update: cd "/home/jeremy/.cache/opencode" && bun add oh-my-opencode@latest
   Affects: plugin features

2. Comment checker unavailable
   Comment checker binary is not installed.
   Fix: Install @code-yeongyu/comment-checker
   Affects: comment-checker hook

3. No LSP servers detected
   LSP-dependent tools will be limited until at least one server is installed.
   Affects: lsp diagnostics, rename, references

Regarding this doctor output, I tried the "fix" it suggested, the command falsely claims permission denied when the file is clearly writable:

jeremy@pop-os-thelio:~/.cache/opencode$ bun add oh-my-opencode@latest
EACCES: Permission denied while opening "/home/jeremy/.cache/opencode/package.json"
note: package.json must be writable to add packages
jeremy@pop-os-thelio:~/.cache/opencode$ ls -lha /home/jeremy/.cache/opencode/package.json
-rw-rw-r-- 1 jeremy jeremy 194 Feb 23 20:09 /home/jeremy/.cache/opencode/package.json
jeremy@pop-os-thelio:~/.cache/opencode$ touch /home/jeremy/.cache/opencode/package.json
jeremy@pop-os-thelio:~/.cache/opencode$ cat /home/jeremy/.cache/opencode/package.json
{
  "dependencies": {
    "opencode-anthropic-auth": "0.0.13",
    "@gitlab/opencode-gitlab-auth": "1.3.2",
    "opencode-archive-before-compaction": "0.1.0",
    "oh-my-opencode": "3.8.4"
  }
}
jeremy@pop-os-thelio:~/.cache/opencode$ bun add oh-my-opencode@latest
EACCES: Permission denied while opening "/home/jeremy/.cache/opencode/package.json"
note: package.json must be writable to add packages

Error Logs

Configuration

Additional Context

No response

Operating System

Linux

OpenCode Version

1.2.21

[acamq]

The ability for sisyphus to use gpt-5.4 is in v3.11.1. You need to get your oh-my-opencode updated. cd "/home/[username]/.cache/opencode" && bun add oh-my-opencode@latest worked for me without write issues.

[jeremyakers]

I'm starting to suspect this is a snap confinement issue. On Ubuntu (and most modern distros now) "bun" is installed by default as a snap package, and snap packages cannot access hidden folders in a users home directory. So ".cache" is not writable by bun by default on those distros.

[acamq]

Try making sure your opencode.json has oh-my-opencode@latest

[jeremyakers]

I removed bun from snap, and installed it instead from npm (Which means it's installed only for my user, no longer available at system level, which is kind of annoying).

But I still see this error in the logs:

WARN ... service=bun pkg=oh-my-opencode cachedVersion=^3.11.1 Failed to resolve latest version, using cached

So it updated to 3.11.1, but it will continue to fail to auto-update due to this failure to resolve latest version.

[acamq]

Thanks for the detailed report. I've investigated and found there are actually two separate issues here:

Issue 1: Directory Mismatch (oh-my-opencode bug)

There's a bug in oh-my-opencode where the auto-update checker reads/writes to the wrong directory:

Component	Current (Wrong)	Should Be
Version check	~/.config/opencode/node_modules/...	~/.cache/opencode/node_modules/...
bun install cwd	~/.config/opencode/	~/.cache/opencode/

OpenCode loads plugins from ~/.cache/opencode/ (see src/bun/index.ts), but oh-my-opencode's auto-updater is looking at ~/.config/opencode/. This is why the manual cd ~/.cache/opencode && bun add oh-my-opencode@latest worked — it updated the correct location.

This will be fixed in the next release.

Issue 2: "Failed to resolve latest version" (environment-specific)

This warning comes from OpenCode itself, not oh-my-opencode:

WARN ... service=bun pkg=oh-my-opencode cachedVersion=^3.11.1 Failed to resolve latest version, using cached

OpenCode runs bun info oh-my-opencode version to check for updates. If this fails, it assumes the cached version is fine and doesn't update. The fact that npm view works but bun info doesn't suggests a bun-specific issue, possibly:

1. Residual snap-related config/cache
2. Bun's package cache corruption
3. .npmrc or registry config that bun handles differently

To debug, please run:

cd ~/.cache/opencode
bun info oh-my-opencode version

If that returns nothing or errors:

# Clear bun's cache
bun pm cache rm

# Try again
bun info oh-my-opencode version

Also, can you share your bun version and any .npmrc config?

bun --version
cat ~/.npmrc 2>/dev/null || echo "no user .npmrc"
cat ~/.cache/opencode/.npmrc 2>/dev/null || echo "no cache .npmrc"

Immediate Workaround

To ensure auto-updates work going forward, verify your ~/.cache/opencode/package.json has the correct entry:

cd ~/.cache/opencode
cat package.json

You want "oh-my-opencode": "3.11.1" (exact version) or "oh-my-opencode": "latest", not a range like "^3.11.1". If it has a caret:

# Fix pinned version with caret
jq '.dependencies."oh-my-opencode" = "latest"' package.json > tmp.json && mv tmp.json package.json
bun install

[jeremyakers]

It did have the carot, so I switched it to "latest":

jeremy@pop-os-thelio:~/.cache/opencode$ bun info oh-my-opencode version
3.11.1
jeremy@pop-os-thelio:~/.cache/opencode$ bun --version
cat ~/.npmrc 2>/dev/null || echo "no user .npmrc"
cat ~/.cache/opencode/.npmrc 2>/dev/null || echo "no cache .npmrc"
1.3.10
prefix=~/.npm-global
no cache .npmrc
jeremy@pop-os-thelio:~/.cache/opencode$ cat package.json
{
  "dependencies": {
    "@gitlab/opencode-gitlab-auth": "1.3.2",
    "oh-my-opencode": "^3.11.1",
    "opencode-anthropic-auth": "0.0.13",
    "opencode-archive-before-compaction": "0.1.0"
  }
}
jeremy@pop-os-thelio:~/.cache/opencode$ vi package.json
jeremy@pop-os-thelio:~/.cache/opencode$ cat package.json 
{
  "dependencies": {
    "@gitlab/opencode-gitlab-auth": "1.3.2",
    "oh-my-opencode": "latest",
    "opencode-anthropic-auth": "0.0.13",
    "opencode-archive-before-compaction": "0.1.0"
  }
}

However it still throws this error at startup:

WARN ... service=bun pkg=oh-my-opencode cachedVersion=latest Failed to resolve latest version, using cached

[acamq]

Did you do the other debugging steps? If nothing works, try deleting opencode's cache and reinstalling

[popododo0720]

This issue is addressed by #2402.

The root cause is that bun install -g oh-my-opencode (or npm install -g) only updates the global npm package, but opencode loads the plugin from its own separate cache at ~/.cache/opencode/node_modules/ with its own bun.lock. The cached version stays stale regardless of global installs.

The PR adds cache invalidation to the postinstall.mjs script, so that after a global install, the stale cached module and lockfiles are automatically removed. On next opencode launch, the plugin is re-resolved to the latest version.

[acamq]

I believe #2380 will fix the auto-updater, so once you get the version with that fix, auto-updates should work fine.