Older releases wrote feedback directly to the terminal. Upgrade to the current release, restart OpenCode, and verify that only the npm installation is active.

opencode plugin opencode-plugin-loop --global --force

Current releases open results in a dedicated native dialog and send runtime diagnostics to OpenCode's structured application log.

Version 0.2.9 compiles the dialog with Solid's reactive OpenTUI transform. If Copy ID, Copy all, or Close remains visually frozen, verify the registry version, close OpenCode, refresh the plugin package cache, reinstall, and restart.

npm view opencode-plugin-loop version
rm -rf ~/.cache/opencode/packages/opencode-plugin-loop \
  ~/.cache/opencode/packages/opencode-plugin-loop@latest
opencode plugin opencode-plugin-loop --global --force

Close all OpenCode processes before removing these directories. This command removes only the cached plugin packages; it does not remove scheduled task storage.

Check the latest registry release:

npm view opencode-plugin-loop version

Check the version selected by OpenCode's cache wrapper:

node -p "require(process.env.HOME + '/.cache/opencode/packages/opencode-plugin-loop@latest/package.json').dependencies['opencode-plugin-loop']"

Check the nested installed package:

node -p "require(process.env.HOME + '/.cache/opencode/packages/opencode-plugin-loop@latest/node_modules/opencode-plugin-loop/package.json').version"

Both cache checks should match the current npm release after a forced reinstall.

Keep the unversioned package name once in each global configuration:

• ~/.config/opencode/opencode.json
• ~/.config/opencode/tui.json

Also check for a copied plugin that OpenCode may load independently:

ls ~/.config/opencode/plugins/opencode-plugin-loop

If that directory exists and the npm package is already configured, move it outside the auto-loaded plugin directory and restart OpenCode:

mv ~/.config/opencode/plugins/opencode-plugin-loop \
  ~/.config/opencode/plugins/opencode-plugin-loop.backup

Keep the backup until the npm installation has been verified.

Project task state is stored separately from the plugin package cache:

• .opencode/cache/loop/tasks.json — persisted scheduled tasks
• .opencode/cache/loop/history.log — task fire history
• OpenCode structured application logs — plugin and TUI diagnostic messages

Do not delete tasks.json unless you intentionally want to reset stored tasks. Package-cache cleanup should target only ~/.cache/opencode/packages/opencode-plugin-loop*.

This is expected. Tasks belong to the session that created them. Use --all only when cross-session access is intentional:

/loop list --all
/loop cancel <taskId> --all
/loop stop-all --all

Collect the OpenCode version, plugin version, relevant structured log entries, and exact /loop command, then open a GitHub issue.