Repository navigation
1.299.0
1.299.0 — OpenCode at the front door
A new desktop setup now starts with OpenCode. The same connection screen used
before an AI import has the install button inline, tests the install, and only
then enables Continue. Direct API remains the phone path and a one-click
fallback.
What changed
- OpenCode is the desktop default. A brand-new desktop install starts on
the OpenCode backend. Phones still use Direct API, because OpenCode runs on
the computer. - The install button is in the setup path. The shared wizard used by
Practice and the import helper opens on OpenCode instead of hiding it under
an advanced disclosure. Install OpenCode downloads the supported build,
shows progress, and can retry a failed start without leaving the screen. - Test, then Continue. Installing no longer silently marks AI as ready.
The screen saves an optional provider key, Test OpenCode starts the
agent and checks its health and provider list, and Continue to import
unlocks only after that test succeeds. - Readiness tells the truth. Practice, the empty screen and the import
helper now require an actual OpenCode install, or a server the user
configured, before showing AI as ready. A missing install points back to the
install button instead of failing later in an import. - Direct API and offline remain reachable. The same screen offers a
Direct API key path for phones, existing keys or a fallback, and Paste
questions instead (works offline) stays visible on both paths. - Existing Direct API setups keep working. An install that already has AI
enabled or saved Direct API credentials, but no saved backend, is migrated
to Direct API. It is not moved to OpenCode by the new default.
The welcome guide's one-click installer still enables AI on a successful
install. The shared wizard passes { enable: false } so it can test the
connection before turning AI on.
Verification
node --test passes 2,563 tests. npm run check is clean across
352 source files; main.js is current at 7,065,144 bytes from
355 modules. git diff --check is clean. The release asset is rebuilt from
this commit, so the build-verification check can reproduce it byte for byte.
The installer and test flow are covered by the wizard tests with a mocked
desktop manager. A live Obsidian window and a real OpenCode installation are
not available in this workspace, so the final in-app install click-through
remains an owner check.