qp-exa-dynamic

LIMITATIONS

Known limitations

- **Exa's beta surface can move.** `dynamic-highlights-2026-08-28` is a research preview; a change on Exa's side means updating `DYNAMIC_BETA_VALUE`. - **Results without highlights are dropped**, matching the seam's rule. With dynamic highlights on, 8 of 8 results carried a highlight in testing, so it rarely fires. - **No `category`, domain or date filters, and no full text.** Those are Exa features this provider does not expose yet. - **One of this and the first-party Exa provider per profile.** Both register the provider id `exa` by default; running both needs a distinct `providerId` on one of them. - **`exa_search` needs an Exa key; `web_search` does not.** The tool goes straight to Exa, so with no key it fails loudly instead of falling back — that is what makes the choice real. `web_search` is unaffected either way. - **Tested against dsh `0.2.0-rc.2`**, which is what the peer ranges pin (`>=0.2.0-rc.2 <0.3.0-0`). - **Without a settings service the `/exa` writes are in-memory only.** The provider itself works either way; without a command registry there is simply no `/exa`. A settings service that refuses the write — no such entry id, no volatile field, a read-only profile — is reported as `could not save: …` rather than silently swallowed.