Synced from monorepo
Synced from monorepo Changes: - Refresh tool search when the managed MCP catalog is re-fetched - Prevent duplicate leader process spawn and startup hang from stale leaders - Document marketplaces, plugins, and organization controls - Stamp session ID on image generation direct-to-API requests - Fix auto mode blocked documentation - Auto mode considers recent user intent - Expose deploy archive, taken-down, limit, and in-progress reasons on the chat API - Fail-closed auth refresh contract for shell clients - Emit a chat-supplied per-session turn index in turn hooks - Show bash mode chrome in minimal mode - Add metrics for true-noop and stationarity stops - Include voice interim text on prompt submit - Silently end turn on true-noop thrash - Quiet copy toast when clipboard delivery is confirmed - Fix session fork truncating at the wrong prompt in rewound sessions - Make the idle "still running" watcher cue clickable to open the tasks pane - Default web search model to grok-4.5 - Let plugin subagents inherit parent MCP servers - Gate no-op end-turn reminder on system reminders - Add gateway bridge lifecycle telemetry - Allow editing finalized text while voice is open - Relocate token carrier to turn-commit events and plumb per-turn origin context - Raise workflow scratch quotas and make failed runs resumable - Workflows overlay: auto-progress phases, live agent status, and drop budget meter Source-Revision: 9b8d35b46d959c042ea9aa31cbbebbd1f0c5c527
This commit is contained in:
parent
69f0ba880a
commit
6e38642082
103 changed files with 4964 additions and 1261 deletions
|
|
@ -6,7 +6,7 @@ Grok connects to custom model endpoints for alternative providers, self-hosted m
|
|||
|
||||
## Default Models
|
||||
|
||||
By default, Grok uses models hosted by SpaceXAI, and new sessions start with `grok-build`. Default models require no configuration. Authenticate with `grok login` or an API key, then start a session.
|
||||
By default, Grok uses models hosted by SpaceXAI, and new sessions start with `grok-4.5`. Default models require no configuration. Authenticate with `grok login` or an API key, then start a session.
|
||||
|
||||
List all available models:
|
||||
|
||||
|
|
@ -48,7 +48,7 @@ Set a persistent default in `~/.grok/config.toml`:
|
|||
|
||||
```toml
|
||||
[models]
|
||||
default = "grok-build"
|
||||
default = "grok-4.5"
|
||||
```
|
||||
|
||||
---
|
||||
|
|
@ -315,13 +315,13 @@ The `web_search` tool uses a separate model. Configure it with:
|
|||
|
||||
```toml
|
||||
[models]
|
||||
web_search = "grok-4.20-multi-agent"
|
||||
web_search = "grok-4.5"
|
||||
```
|
||||
|
||||
Or via environment variable:
|
||||
|
||||
```bash
|
||||
export GROK_WEB_SEARCH_MODEL="grok-4.20-multi-agent"
|
||||
export GROK_WEB_SEARCH_MODEL="grok-4.5"
|
||||
```
|
||||
|
||||
If you point web search at a custom model, you also need a `[model.*]` entry so Grok can reach it. Server-side ("backend") web search runs only when the model sets `supports_backend_search = true` (and the build enables backend search); it does not depend on `api_backend`:
|
||||
|
|
|
|||
Loading…
Reference in a new issue