Skip to content

v0.4.1 — provider detection fix

Latest

Choose a tag to compare

@andregoncalves andregoncalves released this 09 Sep 21:21

Fixed

  • Provider detection in the browser half. The chip read the active session's provider through a
    connection.api.sessions.models(...) call that does not exist in DSH (ctx.connection is a
    ConnectionHandle with rpc, not a session API), so the lookup always threw and the chip silently
    fell back to the DeepSeek balance in every session — including OpenRouter, Moonshot, Zhipu, and
    MiniMax sessions. It now reads ctx.modelDirectories.directoryFor(sessionId).store (the shared
    state the composer's model seat writes) and keeps the model-directory subscription that re-polls
    on a model switch.
  • scripts/verify-client.mjs now drives the real refresh path and asserts the resolved kind for
    each provider route, the OpenRouter regression included.

Full Changelog: v0.4.0...v0.4.1