Gilbert Codex v0.8.1

Gilbert Codex v0.8.1 is the first hotfix build after the major v0.8.0 platform release. It keeps the MCP, Skills, plugin, thinking, tool, and cross-platform release foundation intact while tightening the issues found during real follow-up testing.

Release Status

• Version: 0.8.1
• Tag: v0.8.1
• Previous public release: v0.8.0
• Published release: https://github.com/UrbanWafflezz/GilbertCodex/releases/tag/v0.8.1
• Packaged targets: Windows x64, macOS Apple Silicon, macOS Intel, Linux x64
• Windows artifact family: Gilbert-Codex-0.8.1-x64-setup.exe
• macOS artifact families: Gilbert-Codex-0.8.1-macos-aarch64.dmg, Gilbert-Codex-0.8.1-macos-x64.dmg, and matching updater archives
• Linux artifact families: Gilbert-Codex-0.8.1-linux-x64.deb and Gilbert-Codex-0.8.1-linux-x64.AppImage
• Update feed asset: latest.json
• Checksum assets: .sha256 files
• Updater signature assets: .sig files

What Changed

• Kept MCP stdio subprocesses alive per configured server while the app is open, so stateful workflows such as Firebase deploy jobs can reuse the same server process and returned job IDs.
• Restarted cached MCP stdio sessions when the server config changes, the server is removed, the subprocess exits, or a broken pipe/closed stream is detected.
• Persisted Firebase project-directory context after successful MCP tool calls so later deploy/status calls can recover the correct working directory.
• Improved Firebase MCP guidance so blank deploy failures, structured project-directory errors, or missing logs fall back to terminal CLI evidence when terminal tools are available.
• Improved answer synthesis when MCP tool calls already ran, so successful MCP work is not incorrectly treated as a missing workspace edit.
• Added 9Router private-LAN URL discovery and display so other devices on the same network can use the desktop-hosted subscription router when enabled.
• Allowed 9Router local requests to private LAN addresses on the expected port while continuing to reject public hosts, HTTPS, and unexpected ports.
• Fixed Discord bridge ngrok discovery by searching the repo helper folder, PATH, and common Windows package-manager install locations.
• Updated CI and release workflow runners for steadier builds: Windows targets windows-2025-vs2026, macOS is pinned to macos-15, and Node setup uses Node 24.
• Bumped all release-facing version fields to 0.8.1.

Release Notes For Testers

• On Windows, install the NSIS setup executable and verify first launch, provider setup, chat, workspace tools, MCP stdio tools, Discord ngrok-backed bridge setup, 9Router local/LAN routing, updater check, and uninstall.
• On macOS Apple Silicon and Intel, mount the DMG, move the app into Applications, launch it, and verify Keychain-backed secrets, file picker permissions, terminal shell startup, browser preview, notifications, provider setup, MCP stdio servers, Skills, plugin imports, and update checks.
• On Linux, test both deb and AppImage artifacts on a WebKitGTK 4.1-capable desktop and verify Secret Service-backed secrets, file picker behavior, terminal shell startup, browser preview, notifications, provider setup, MCP stdio servers, Skills, plugin imports, and update checks.
• Confirm latest.json contains entries for Windows, macOS Apple Silicon, macOS Intel, Linux deb, and Linux AppImage.
• Confirm every downloadable package has a matching .sha256 file and every updater package has a matching .sig file.

Validation Commands

npm.cmd run build
npm.cmd run rust:fmt:check
npm.cmd run rust:check
npm.cmd test
cargo test --manifest-path src-tauri\Cargo.toml mcp -- --nocapture
cargo test --manifest-path src-tauri\Cargo.toml ngrok -- --nocapture
cargo test --manifest-path src-tauri\Cargo.toml nine_router -- --nocapture
git diff --check

The GitHub Release workflow performs the signed updater release build when v0.8.1 is pushed or the workflow is dispatched with this version input. Manual workflow dispatches create a draft release for review; tag pushes publish the release.

Known Limits

macOS and Linux package artifacts are built and published by GitHub-hosted native runners, but they still need real-device launch smoke tests before the project should call those platforms fully verified.

macOS artifacts are ad-hoc signed for packaging unless Apple Developer signing and notarization credentials are added to the release path. Without notarization, Gatekeeper may require extra user confirmation on first launch.

The plugin marketplace foundation is live, but deeper installation and update flows beyond the current native, MCP, and skill-import routes are still being polished.

ChatGPT GPT-5.3 Spark remains a known read-only route for workspace work. Other Codex/ChatGPT, OpenRouter, and local routes remain the recommended paths for file changes until that provider route is fixed.

Release builds require the private release overlay repository and Tauri updater signing key secrets. If those secrets are missing, the workflow should fail before shipping an incomplete desktop package.

Provider keys, OAuth secrets, GitHub tokens, Discord settings, local accounts, logs, local databases, workspace files, scan artifacts, release signing credentials, updater private keys, MCP bearer tokens, MCP stdio env values, and private overlay credentials stay out of public Git and are not bundled into installers.