v1.8.1

Fixed

• Vault mode no longer reads local accounts at startup. While OpenCode is connected to the Claustrum vault, only vault accounts are used, but the plugin still opened and parsed the local account files when OpenCode started, including the token file. It now reads only its settings from openai-auth.json while connected, and loads local accounts the first time they're used after you disconnect, with no restart needed.

  • OpenCode 2: a damaged local token file stopped the plugin from starting, even in vault mode. It no longer does.
  • OpenCode 1: a damaged local token file made the plugin forget your saved settings in vault mode, killswitch floors included. They're kept now.

• The vault menu no longer reads "0 accounts" before the vault has answered. Right after OpenCode or Pi starts, or after the vault daemon restarts, /openai could show "Connected · 0 accounts" with advice to grant access, when the vault simply hadn't answered yet. It now says "Connected · waiting for the vault's first answer", with no account actions until the vault answers. A vault that answers with no accounts still shows the existing message and its fix. The sidebar makes the same distinction.

Changed

• Tested on OpenCode 2.2.0. The real OpenCode 2 tests now run on 2.2.0. The plugin moves to OpenTUI 0.7.0, the version OpenCode 2.2.0 uses; the compiled sidebar is unchanged.
• Dependencies: the bundled ai SDK moves to 7.0.155, and Pi support is tested on Pi 1.4.0.