Skip to content

feat(web-search): add Context.dev provider - #1736

Draft
mrmps wants to merge 1 commit into
AtomicBot-ai:mainfrom
mrmps:codex/context-search-provider
Draft

mrmps wants to merge 1 commit into
AtomicBot-ai:mainfrom
mrmps:codex/context-search-provider

Conversation

@mrmps

@mrmps mrmps commented Nov 19, 2026 •

Copy link
Copy Markdown

Adds Context.dev as an optional os.web.search provider, with query-relevant Highlights enabled by default. Exa remains the default, and existing fallback settings are unchanged.

Set web.search.provider to "context" and add CONTEXT_DEV_API_KEY to the existing state-directory .env. Requests use the Context account's credits. I work on Context.dev.

The comparison below shows recorded native config list --describe output, not an interactive TUI capture.

Before (Recorded provider settings help) After (Recorded provider settings help)
Before After

Context queries are limited to 500 characters. Incomplete response collections fail explicitly because the host's result format cannot represent partial status.

The own-fork Linux CI run passes on this commit. The upstream Test workflow awaits maintainer approval. The full local macOS suite finished with 24,234 passed, nine skipped and 19 failures: 17 identical cases also fail on untouched upstream; two shell-test timeouts pass on both commits in isolation. The local suite is not green.

The existing settings generator also reorders the browser isolation type union; its values and default are unchanged.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant