fengming 0.3.9 → 0.3.11

package/docs/tools/web-fetch.md

@@ -1,210 +0,0 @@
----
-summary: "web_fetch tool -- HTTP fetch with readable content extraction"
-read_when:
-  - You want to fetch a URL and extract readable content
-  - You need to configure web_fetch or its Firecrawl fallback
-  - You want to understand web_fetch limits and caching
-title: "Web fetch"
-sidebarTitle: "Web Fetch"
----
-
-The `web_fetch` tool does a plain HTTP GET and extracts readable content
-(HTML to markdown or text). It does **not** execute JavaScript.
-
-For JS-heavy sites or login-protected pages, use the
-[Web Browser](/tools/browser) instead.
-
-## Quick start
-
-`web_fetch` is **enabled by default** -- no configuration needed. The agent can
-call it immediately:
-
-```javascript
-await web_fetch({ url: "https://example.com/article" });
-```
-
-## Tool parameters
-
-<ParamField path="url" type="string" required>
-URL to fetch. `http(s)` only.
-</ParamField>
-
-<ParamField path="extractMode" type="'markdown' | 'text'" default="markdown">
-Output format after main-content extraction.
-</ParamField>
-
-<ParamField path="maxChars" type="number">
-Truncate output to this many characters.
-</ParamField>
-
-## How it works
-
-<Steps>
-  <Step title="Fetch">
-    Sends an HTTP GET with a Chrome-like User-Agent and `Accept-Language`
-    header. Blocks private/internal hostnames and re-checks redirects.
-  </Step>
-  <Step title="Extract">
-    Runs Readability (main-content extraction) on the HTML response.
-  </Step>
-  <Step title="Fallback (optional)">
-    If Readability fails and Firecrawl is configured, retries through the
-    Firecrawl API with bot-circumvention mode.
-  </Step>
-  <Step title="Cache">
-    Results are cached for 15 minutes (configurable) to reduce repeated
-    fetches of the same URL.
-  </Step>
-</Steps>
-
-## Progress updates
-
-`web_fetch` emits a public progress line only when the fetch is still pending
-after five seconds:
-
-```text
-Fetching page content...
-```
-
-Fast cache hits and quick network responses finish before the timer fires, so
-they do not show a progress line. If the call is canceled, the timer is cleared.
-When the fetch eventually completes, the agent receives the normal tool result;
-the progress line is only channel UI state and never contains fetched page
-content.
-
-## Config
-
-```json5
-{
-  tools: {
-    web: {
-      fetch: {
-        enabled: true, // default: true
-        provider: "firecrawl", // optional; omit for auto-detect
-        maxChars: 50000, // max output chars
-        maxCharsCap: 50000, // hard cap for maxChars param
-        maxResponseBytes: 2000000, // max download size before truncation
-        timeoutSeconds: 30,
-        cacheTtlMinutes: 15,
-        maxRedirects: 3,
-        useTrustedEnvProxy: false, // let a trusted HTTP(S) env proxy resolve DNS
-        readability: true, // use Readability extraction
-        userAgent: "Mozilla/5.0 ...", // override User-Agent
-        ssrfPolicy: {
-          allowRfc2544BenchmarkRange: true, // opt-in for trusted fake-IP proxies using 198.18.0.0/15
-          allowIpv6UniqueLocalRange: true, // opt-in for trusted fake-IP proxies using fc00::/7
-        },
-      },
-    },
-  },
-}
-```
-
-## Firecrawl fallback
-
-If Readability extraction fails, `web_fetch` can fall back to
-[Firecrawl](/tools/firecrawl) for bot-circumvention and better extraction:
-
-```json5
-{
-  tools: {
-    web: {
-      fetch: {
-        provider: "firecrawl", // optional; omit for auto-detect from available credentials
-      },
-    },
-  },
-  plugins: {
-    entries: {
-      firecrawl: {
-        enabled: true,
-        config: {
-          webFetch: {
-            apiKey: "fc-...", // optional if FIRECRAWL_API_KEY is set
-            baseUrl: "https://api.firecrawl.dev",
-            onlyMainContent: true,
-            maxAgeMs: 86400000, // cache duration (1 day)
-            timeoutSeconds: 60,
-          },
-        },
-      },
-    },
-  },
-}
-```
-
-`plugins.entries.firecrawl.config.webFetch.apiKey` supports SecretRef objects.
-Legacy `tools.web.fetch.firecrawl.*` config is auto-migrated by `fengming doctor --fix`.
-
-<Note>
-  If Firecrawl is enabled and its SecretRef is unresolved with no
-  `FIRECRAWL_API_KEY` env fallback, gateway startup fails fast.
-</Note>
-
-<Note>
-  Firecrawl `baseUrl` overrides are locked down: hosted traffic uses
-  `https://api.firecrawl.dev`; self-hosted overrides must target private or
-  internal endpoints, and `http://` is accepted only for those private targets.
-</Note>
-
-Current runtime behavior:
-
-- `tools.web.fetch.provider` selects the fetch fallback provider explicitly.
-- If `provider` is omitted, FengMing auto-detects the first ready web-fetch
-  provider from available credentials. Non-sandboxed `web_fetch` can use
-  installed plugins that declare `contracts.webFetchProviders` and register a
-  matching provider at runtime. Today the bundled provider is Firecrawl.
-- Sandboxed `web_fetch` calls stay limited to bundled providers.
-- If Readability is disabled, `web_fetch` skips straight to the selected
-  provider fallback. If no provider is available, it fails closed.
-
-## Trusted env proxy
-
-If your deployment requires `web_fetch` to go through a trusted outbound
-HTTP(S) proxy, set `tools.web.fetch.useTrustedEnvProxy: true`.
-
-In this mode, FengMing still applies hostname-based SSRF checks before sending
-the request, but it lets the proxy resolve DNS instead of doing local DNS
-pinning. Enable this only when the proxy is operator-controlled and enforces
-outbound policy after DNS resolution.
-
-<Note>
-  If no HTTP(S) proxy env var is configured, or the target host is excluded by
-  `NO_PROXY`, `web_fetch` falls back to the normal strict path with local DNS
-  pinning.
-</Note>
-
-## Limits and safety
-
-- `maxChars` is clamped to `tools.web.fetch.maxCharsCap`
-- Response body is capped at `maxResponseBytes` before parsing; oversized
-  responses are truncated with a warning
-- Private/internal hostnames are blocked
-- `tools.web.fetch.ssrfPolicy.allowRfc2544BenchmarkRange` and
-  `tools.web.fetch.ssrfPolicy.allowIpv6UniqueLocalRange` are narrow opt-ins
-  for trusted fake-IP proxy stacks; leave them unset unless your proxy owns
-  those synthetic ranges and enforces its own destination policy
-- Redirects are checked and limited by `maxRedirects`
-- `useTrustedEnvProxy` is an explicit opt-in and should only be enabled for
-  operator-controlled proxies that still enforce outbound policy after DNS
-  resolution
-- `web_fetch` is best-effort -- some sites need the [Web Browser](/tools/browser)
-
-## Tool profiles
-
-If you use tool profiles or allowlists, add `web_fetch` or `group:web`:
-
-```json5
-{
-  tools: {
-    allow: ["web_fetch"],
-    // or: allow: ["group:web"]  (includes web_fetch, web_search, and x_search)
-  },
-}
-```
-
-## Related
-
-- [Web Search](/tools/web) -- search the web with multiple providers
-- [Web Browser](/tools/browser) -- full browser automation for JS-heavy sites
-- [Firecrawl](/tools/firecrawl) -- Firecrawl search and scrape tools

package/docs/tools/web.md

@@ -1,461 +0,0 @@
----
-summary: "web_search, x_search, and web_fetch -- search the web, search X posts, or fetch page content"
-title: "Web search"
-sidebarTitle: "Web Search"
-read_when:
-  - You want to enable or configure web_search
-  - You want to enable or configure x_search
-  - You need to choose a search provider
-  - You want to understand auto-detection and provider fallback
----
-
-The `web_search` tool searches the web using your configured provider and
-returns results. Results are cached by query for 15 minutes (configurable).
-
-FengMing also includes `x_search` for X (formerly Twitter) posts and
-`web_fetch` for lightweight URL fetching. In this phase, `web_fetch` stays
-local while `web_search` and `x_search` can use xAI Responses under the hood.
-
-<Info>
-  `web_search` is a lightweight HTTP tool, not browser automation. For
-  JS-heavy sites or logins, use the [Web Browser](/tools/browser). For
-  fetching a specific URL, use [Web Fetch](/tools/web-fetch).
-</Info>
-
-## Quick start
-
-<Steps>
-  <Step title="Choose a provider">
-    Pick a provider and complete any required setup. Some providers are
-    key-free, while others use API keys. See the provider pages below for
-    details.
-  </Step>
-  <Step title="Configure">
-    ```bash
-    fengming configure --section web
-    ```
-    This stores the provider and any needed credential. You can also set an env
-    var (for example `BRAVE_API_KEY`) and skip this step for API-backed
-    providers.
-  </Step>
-  <Step title="Use it">
-    The agent can now call `web_search`:
-
-    ```javascript
-    await web_search({ query: "FengMing plugin SDK" });
-    ```
-
-    For X posts, use:
-
-    ```javascript
-    await x_search({ query: "dinner recipes" });
-    ```
-
-  </Step>
-</Steps>
-
-## Choosing a provider
-
-<CardGroup cols={2}>
-  <Card title="Brave Search" icon="shield" href="/tools/brave-search">
-    Structured results with snippets. Supports `llm-context` mode, country/language filters. Free tier available.
-  </Card>
-  <Card title="DuckDuckGo" icon="bird" href="/tools/duckduckgo-search">
-    Key-free fallback. No API key needed. Unofficial HTML-based integration.
-  </Card>
-  <Card title="Exa" icon="brain" href="/tools/exa-search">
-    Neural + keyword search with content extraction (highlights, text, summaries).
-  </Card>
-  <Card title="Firecrawl" icon="flame" href="/tools/firecrawl">
-    Structured results. Best paired with `firecrawl_search` and `firecrawl_scrape` for deep extraction.
-  </Card>
-  <Card title="Gemini" icon="sparkles" href="/tools/gemini-search">
-    AI-synthesized answers with citations via Google Search grounding.
-  </Card>
-  <Card title="Grok" icon="zap" href="/tools/grok-search">
-    AI-synthesized answers with citations via xAI web grounding.
-  </Card>
-  <Card title="Kimi" icon="moon" href="/tools/kimi-search">
-    AI-synthesized answers with citations via Moonshot web search; ungrounded chat fallbacks fail explicitly.
-  </Card>
-  <Card title="MiniMax Search" icon="globe" href="/tools/minimax-search">
-    Structured results via the MiniMax Token Plan search API.
-  </Card>
-  <Card title="Ollama Web Search" icon="globe" href="/tools/ollama-search">
-    Search via a signed-in local Ollama host or the hosted Ollama API.
-  </Card>
-  <Card title="Perplexity" icon="search" href="/tools/perplexity-search">
-    Structured results with content extraction controls and domain filtering.
-  </Card>
-  <Card title="SearXNG" icon="server" href="/tools/searxng-search">
-    Self-hosted meta-search. No API key needed. Aggregates Google, Bing, DuckDuckGo, and more.
-  </Card>
-  <Card title="Tavily" icon="globe" href="/tools/tavily">
-    Structured results with search depth, topic filtering, and `tavily_extract` for URL extraction.
-  </Card>
-</CardGroup>
-
-### Provider comparison
-
-| Provider                                  | Result style                                                   | Filters                                          | API key                                                                                 |
-| ----------------------------------------- | -------------------------------------------------------------- | ------------------------------------------------ | --------------------------------------------------------------------------------------- |
-| [Brave](/tools/brave-search)              | Structured snippets                                            | Country, language, time, `llm-context` mode      | `BRAVE_API_KEY`                                                                         |
-| [DuckDuckGo](/tools/duckduckgo-search)    | Structured snippets                                            | --                                               | None (key-free)                                                                         |
-| [Exa](/tools/exa-search)                  | Structured + extracted                                         | Neural/keyword mode, date, content extraction    | `EXA_API_KEY`                                                                           |
-| [Firecrawl](/tools/firecrawl)             | Structured snippets                                            | Via `firecrawl_search` tool                      | `FIRECRAWL_API_KEY`                                                                     |
-| [Gemini](/tools/gemini-search)            | AI-synthesized + citations                                     | --                                               | `GEMINI_API_KEY`                                                                        |
-| [Grok](/tools/grok-search)                | AI-synthesized + citations                                     | --                                               | xAI OAuth, `XAI_API_KEY`, or `plugins.entries.xai.config.webSearch.apiKey`              |
-| [Kimi](/tools/kimi-search)                | AI-synthesized + citations; fails on ungrounded chat fallbacks | --                                               | `KIMI_API_KEY` / `MOONSHOT_API_KEY`                                                     |
-| [MiniMax Search](/tools/minimax-search)   | Structured snippets                                            | Region (`global` / `cn`)                         | `MINIMAX_CODE_PLAN_KEY` / `MINIMAX_CODING_API_KEY` / `MINIMAX_OAUTH_TOKEN`              |
-| [Ollama Web Search](/tools/ollama-search) | Structured snippets                                            | --                                               | None for signed-in local hosts; `OLLAMA_API_KEY` for direct `https://ollama.com` search |
-| [Perplexity](/tools/perplexity-search)    | Structured snippets                                            | Country, language, time, domains, content limits | `PERPLEXITY_API_KEY` / `OPENROUTER_API_KEY`                                             |
-| [SearXNG](/tools/searxng-search)          | Structured snippets                                            | Categories, language                             | None (self-hosted)                                                                      |
-| [Tavily](/tools/tavily)                   | Structured snippets                                            | Via `tavily_search` tool                         | `TAVILY_API_KEY`                                                                        |
-
-## Auto-detection
-
-## Native OpenAI web search
-
-Direct OpenAI Responses models use OpenAI's hosted `web_search` tool automatically when FengMing web search is enabled and no managed provider is pinned. This is provider-owned behavior in the bundled OpenAI plugin and only applies to native OpenAI API traffic, not OpenAI-compatible proxy base URLs or Azure routes. Set `tools.web.search.provider` to another provider such as `brave` to keep the managed `web_search` tool for OpenAI models, or set `tools.web.search.enabled: false` to disable both managed search and native OpenAI search.
-
-## Native Codex web search
-
-Codex-capable models can optionally use the provider-native Responses `web_search` tool instead of FengMing's managed `web_search` function.
-
-- Configure it under `tools.web.search.openaiCodex`
-- It only activates for Codex-capable OpenAI models (`openai/*` models using `api: "openai-codex-responses"`)
-- Managed `web_search` still applies to non-Codex models
-- `mode: "cached"` is the default and recommended setting
-- `tools.web.search.enabled: false` disables both managed and native search
-
-```json5
-{
-  tools: {
-    web: {
-      search: {
-        enabled: true,
-        openaiCodex: {
-          enabled: true,
-          mode: "cached",
-          allowedDomains: ["example.com"],
-          contextSize: "high",
-          userLocation: {
-            country: "US",
-            city: "New York",
-            timezone: "America/New_York",
-          },
-        },
-      },
-    },
-  },
-}
-```
-
-If native Codex search is enabled but the current model is not Codex-capable, FengMing keeps the normal managed `web_search` behavior.
-
-## Network safety
-
-Managed `web_search` provider calls use FengMing's guarded fetch path. For
-trusted provider API hosts, FengMing allows Surge, Clash, and sing-box fake-IP
-DNS answers in `198.18.0.0/15` and `fc00::/7` only for that provider hostname.
-Other private, loopback, link-local, and metadata destinations remain blocked.
-
-This automatic allowance does not apply to arbitrary `web_fetch` URLs. For
-`web_fetch`, enable `tools.web.fetch.ssrfPolicy.allowRfc2544BenchmarkRange` and
-`tools.web.fetch.ssrfPolicy.allowIpv6UniqueLocalRange` explicitly only when your
-trusted proxy owns those synthetic ranges.
-
-## Setting up web search
-
-Provider lists in docs and setup flows are alphabetical. Auto-detection keeps a
-separate precedence order.
-
-If no `provider` is set, FengMing checks providers in this order and uses the
-first one that is ready:
-
-API-backed providers first:
-
-1. **Brave** -- `BRAVE_API_KEY` or `plugins.entries.brave.config.webSearch.apiKey` (order 10)
-2. **MiniMax Search** -- `MINIMAX_CODE_PLAN_KEY` / `MINIMAX_CODING_API_KEY` / `MINIMAX_OAUTH_TOKEN` / `MINIMAX_API_KEY` or `plugins.entries.minimax.config.webSearch.apiKey` (order 15)
-3. **Gemini** -- `plugins.entries.google.config.webSearch.apiKey`, `GEMINI_API_KEY`, or `models.providers.google.apiKey` (order 20)
-4. **Grok** -- xAI OAuth, `XAI_API_KEY`, or `plugins.entries.xai.config.webSearch.apiKey` (order 30)
-5. **Kimi** -- `KIMI_API_KEY` / `MOONSHOT_API_KEY` or `plugins.entries.moonshot.config.webSearch.apiKey` (order 40)
-6. **Perplexity** -- `PERPLEXITY_API_KEY` / `OPENROUTER_API_KEY` or `plugins.entries.perplexity.config.webSearch.apiKey` (order 50)
-7. **Firecrawl** -- `FIRECRAWL_API_KEY` or `plugins.entries.firecrawl.config.webSearch.apiKey` (order 60)
-8. **Exa** -- `EXA_API_KEY` or `plugins.entries.exa.config.webSearch.apiKey`; optional `plugins.entries.exa.config.webSearch.baseUrl` overrides the Exa endpoint (order 65)
-9. **Tavily** -- `TAVILY_API_KEY` or `plugins.entries.tavily.config.webSearch.apiKey` (order 70)
-
-Key-free fallbacks after that:
-
-10. **DuckDuckGo** -- key-free HTML fallback with no account or API key (order 100)
-11. **Ollama Web Search** -- key-free fallback via your configured local Ollama host when it is reachable and signed in with `ollama signin`; can reuse Ollama provider bearer auth when the host needs it, and can call direct `https://ollama.com` search when configured with `OLLAMA_API_KEY` (order 110)
-12. **SearXNG** -- `SEARXNG_BASE_URL` or `plugins.entries.searxng.config.webSearch.baseUrl` (order 200)
-
-If no provider is detected, it falls back to Brave (you will get a missing-key
-error prompting you to configure one).
-
-<Note>
-  All provider key fields support SecretRef objects. Plugin-scoped SecretRefs
-  under `plugins.entries.<plugin>.config.webSearch.apiKey` are resolved for the
-  bundled API-backed web search providers, including Brave, Exa, Firecrawl,
-  Gemini, Grok, Kimi, MiniMax, Perplexity, and Tavily,
-  whether the provider is picked explicitly via `tools.web.search.provider` or
-  selected through auto-detect. In auto-detect mode, FengMing resolves only the
-  selected provider key -- non-selected SecretRefs stay inactive, so you can
-  keep multiple providers configured without paying resolution cost for the
-  ones you are not using.
-</Note>
-
-## Config
-
-```json5
-{
-  tools: {
-    web: {
-      search: {
-        enabled: true, // default: true
-        provider: "brave", // or omit for auto-detection
-        maxResults: 5,
-        timeoutSeconds: 30,
-        cacheTtlMinutes: 15,
-      },
-    },
-  },
-}
-```
-
-Provider-specific config (API keys, base URLs, modes) lives under
-`plugins.entries.<plugin>.config.webSearch.*`. Gemini can also reuse
-`models.providers.google.apiKey` and `models.providers.google.baseUrl` as lower-priority
-fallbacks after its dedicated web-search config and `GEMINI_API_KEY`. See the
-provider pages for examples.
-Grok can also reuse an xAI OAuth auth profile from `fengming models auth login
---provider xai --method oauth`; API-key config remains the fallback.
-
-`tools.web.search.provider` is validated against the web-search provider ids
-declared by bundled and installed plugin manifests. A typo such as `"brvae"`
-fails config validation instead of silently falling back to auto-detection. If a
-configured provider only has stale plugin evidence, such as a leftover
-`plugins.entries.<plugin>` block after uninstalling a third-party plugin,
-FengMing keeps startup resilient and reports a warning so you can reinstall the
-plugin or run `fengming doctor --fix` to clean up the stale config.
-
-`web_fetch` fallback provider selection is separate:
-
-- choose it with `tools.web.fetch.provider`
-- or omit that field and let FengMing auto-detect the first ready web-fetch
-  provider from available credentials
-- non-sandboxed `web_fetch` can use installed plugin providers that declare
-  `contracts.webFetchProviders`; sandboxed fetches stay bundled-only
-- today the bundled web-fetch provider is Firecrawl, configured under
-  `plugins.entries.firecrawl.config.webFetch.*`
-
-When you choose **Kimi** during `fengming onboard` or
-`fengming configure --section web`, FengMing can also ask for:
-
-- the Moonshot API region (`https://api.moonshot.ai/v1` or `https://api.moonshot.cn/v1`)
-- the default Kimi web-search model (defaults to `kimi-k2.6`)
-
-For `x_search`, configure `plugins.entries.xai.config.xSearch.*`. It uses the
-same xAI auth profile as chat, or the `XAI_API_KEY` / plugin web-search
-credential used by Grok web search.
-Legacy `tools.web.x_search.*` config is auto-migrated by `fengming doctor --fix`.
-When you choose Grok during `fengming onboard` or `fengming configure --section web`,
-FengMing can also offer optional `x_search` setup with the same credential.
-This is a separate follow-up step inside the Grok path, not a separate top-level
-web-search provider choice. If you pick another provider, FengMing does not
-show the `x_search` prompt.
-
-### Storing API keys
-
-<Tabs>
-  <Tab title="Config file">
-    Run `fengming configure --section web` or set the key directly:
-
-    ```json5
-    {
-      plugins: {
-        entries: {
-          brave: {
-            config: {
-              webSearch: {
-                apiKey: "YOUR_KEY", // pragma: allowlist secret
-              },
-            },
-          },
-        },
-      },
-    }
-    ```
-
-  </Tab>
-  <Tab title="Environment variable">
-    Set the provider env var in the Gateway process environment:
-
-    ```bash
-    export BRAVE_API_KEY="YOUR_KEY"
-    ```
-
-    For a gateway install, put it in `~/.fengming/.env`.
-    See [Env vars](/help/faq#env-vars-and-env-loading).
-
-  </Tab>
-</Tabs>
-
-## Tool parameters
-
-| Parameter             | Description                                           |
-| --------------------- | ----------------------------------------------------- |
-| `query`               | Search query (required)                               |
-| `count`               | Results to return (1-10, default: 5)                  |
-| `country`             | 2-letter ISO country code (e.g. "US", "DE")           |
-| `language`            | ISO 639-1 language code (e.g. "en", "de")             |
-| `search_lang`         | Search-language code (Brave only)                     |
-| `freshness`           | Time filter: `day`, `week`, `month`, or `year`        |
-| `date_after`          | Results after this date (YYYY-MM-DD)                  |
-| `date_before`         | Results before this date (YYYY-MM-DD)                 |
-| `ui_lang`             | UI language code (Brave only)                         |
-| `domain_filter`       | Domain allowlist/denylist array (Perplexity only)     |
-| `max_tokens`          | Total content budget, default 25000 (Perplexity only) |
-| `max_tokens_per_page` | Per-page token limit, default 2048 (Perplexity only)  |
-
-<Warning>
-  Not all parameters work with all providers. Brave `llm-context` mode
-  rejects `ui_lang`; `date_before` also needs `date_after` because Brave custom
-  freshness ranges require both start and end dates.
-  Gemini, Grok, and Kimi return one synthesized answer with citations. They
-  accept `count` for shared-tool compatibility, but it does not change the
-  grounded answer shape. Gemini supports `freshness`, `date_after`, and
-  `date_before` by converting them to Google Search grounding time ranges.
-  Perplexity behaves the same way when you use the Sonar/OpenRouter
-  compatibility path (`plugins.entries.perplexity.config.webSearch.baseUrl` /
-  `model` or `OPENROUTER_API_KEY`).
-  SearXNG accepts `http://` only for trusted private-network or loopback hosts;
-  public SearXNG endpoints must use `https://`.
-  Firecrawl and Tavily only support `query` and `count` through `web_search`
-  -- use their dedicated tools for advanced options.
-</Warning>
-
-## x_search
-
-`x_search` queries X (formerly Twitter) posts using xAI and returns
-AI-synthesized answers with citations. It accepts natural-language queries and
-optional structured filters. FengMing only enables the built-in xAI `x_search`
-tool on the request that serves this tool call.
-
-<Note>
-  xAI documents `x_search` as supporting keyword search, semantic search, user
-  search, and thread fetch. For per-post engagement stats such as reposts,
-  replies, bookmarks, or views, prefer a targeted lookup for the exact post URL
-  or status ID. Broad keyword searches may find the right post but return less
-  complete per-post metadata. A good pattern is: locate the post first, then
-  run a second `x_search` query focused on that exact post.
-</Note>
-
-### x_search config
-
-```json5
-{
-  plugins: {
-    entries: {
-      xai: {
-        config: {
-          xSearch: {
-            enabled: true,
-            model: "grok-4-1-fast-non-reasoning",
-            baseUrl: "https://api.x.ai/v1", // optional, overrides webSearch.baseUrl
-            inlineCitations: false,
-            maxTurns: 2,
-            timeoutSeconds: 30,
-            cacheTtlMinutes: 15,
-          },
-          webSearch: {
-            apiKey: "xai-...", // optional if an xAI auth profile or XAI_API_KEY is set
-            baseUrl: "https://api.x.ai/v1", // optional shared xAI Responses base URL
-          },
-        },
-      },
-    },
-  },
-}
-```
-
-`x_search` posts to `<baseUrl>/responses` when
-`plugins.entries.xai.config.xSearch.baseUrl` is set. If that field is omitted,
-it falls back to `plugins.entries.xai.config.webSearch.baseUrl`, then the
-legacy `tools.web.search.grok.baseUrl`, and finally the public xAI endpoint.
-
-### x_search parameters
-
-| Parameter                    | Description                                            |
-| ---------------------------- | ------------------------------------------------------ |
-| `query`                      | Search query (required)                                |
-| `allowed_x_handles`          | Restrict results to specific X handles                 |
-| `excluded_x_handles`         | Exclude specific X handles                             |
-| `from_date`                  | Only include posts on or after this date (YYYY-MM-DD)  |
-| `to_date`                    | Only include posts on or before this date (YYYY-MM-DD) |
-| `enable_image_understanding` | Let xAI inspect images attached to matching posts      |
-| `enable_video_understanding` | Let xAI inspect videos attached to matching posts      |
-
-### x_search example
-
-```javascript
-await x_search({
-  query: "dinner recipes",
-  allowed_x_handles: ["nytfood"],
-  from_date: "2026-03-01",
-});
-```
-
-```javascript
-// Per-post stats: use the exact status URL or status ID when possible
-await x_search({
-  query: "https://x.com/huntharo/status/1905678901234567890",
-});
-```
-
-## Examples
-
-```javascript
-// Basic search
-await web_search({ query: "FengMing plugin SDK" });
-
-// German-specific search
-await web_search({ query: "TV online schauen", country: "DE", language: "de" });
-
-// Recent results (past week)
-await web_search({ query: "AI developments", freshness: "week" });
-
-// Date range
-await web_search({
-  query: "climate research",
-  date_after: "2024-01-01",
-  date_before: "2024-06-30",
-});
-
-// Domain filtering (Perplexity only)
-await web_search({
-  query: "product reviews",
-  domain_filter: ["-reddit.com", "-pinterest.com"],
-});
-```
-
-## Tool profiles
-
-If you use tool profiles or allowlists, add `web_search`, `x_search`, or `group:web`:
-
-```json5
-{
-  tools: {
-    allow: ["web_search", "x_search"],
-    // or: allow: ["group:web"]  (includes web_search, x_search, and web_fetch)
-  },
-}
-```
-
-## Related
-
-- [Web Fetch](/tools/web-fetch) -- fetch a URL and extract readable content
-- [Web Browser](/tools/browser) -- full browser automation for JS-heavy sites
-- [Grok Search](/tools/grok-search) -- Grok as the `web_search` provider
-- [Ollama Web Search](/tools/ollama-search) -- key-free web search through your Ollama host

package/docs/tts.md

@@ -1,11 +0,0 @@
----
-summary: "Redirect to /tools/tts"
-title: "Text-to-speech"
-redirect: /tools/tts
----
-
-This page has moved to [Text-to-Speech](/tools/tts).
-
-## Related
-
-- [Text-to-speech](/tools/tts)