1.9.3

Install

Drop the attached .zip at your repo root without extracting it — the agent unpacks it as the first step. Then type this shortcut phrase as a chat message to your AI agent (Claude Code, Cursor, Codex, Junie, GitHub Copilot, Windsurf, Air, or Warp):

Install Wavefoundry

That is the only operator-typed command — the agent runs the rest of the install. Prerequisites: Python 3.11+, an MCP-aware agent host. Full walkthrough and host-specific notes in the README.

Upgrade

Already running Wavefoundry? Drop the attached .zip at your repo root without extracting it and type this shortcut phrase to your agent:

Upgrade Wavefoundry

The agent unpacks the zip, advances the framework, runs any required migrations and index rebuilds, and reloads the MCP server. Review the version notes below for anything that re-indexes or changes behavior on this upgrade.

---

Changed

• MCP startup no longer starts model prewarm. The MCP handler no longer launches background embedding/reranker cache work while the host is still negotiating stdio and loading tool schemas; semantic search starts the optional prewarm after startup instead. Install guidance now reinforces the generated config contract: launch MCP with PATH python on server.py, not a hardcoded tool-venv Python path, and start a fresh host session after config/Python fixes. wf setup now smoke-tests the same python server.py --dry-run launch shape used by generated MCP configs.
• Model-fetch CA discovery honors Node's CA bundle env var. The setup/model-download trust-store fallback now recognizes NODE_EXTRA_CA_CERTS after CODEX_CA_CERTIFICATE / CLAUDE_CODE_CERT_STORE and before SSL_CERT_FILE / REQUESTS_CA_BUNDLE, so native Windows users launched from Node-based agent hosts can reuse the same corporate CA bundle the host process already trusts. Wave 1p7pk / native-Windows field follow-up.