Skip to content

feat(cli): support Grok Build custom host configuration - #10830

Merged
diegosouzapw merged 2 commits into
diegosouzapw:release/v3.8.50from
tuandinh0801:feat/grok-build-cli-support
Aug 21, 2026
Merged

diegosouzapw merged 2 commits into
diegosouzapw:release/v3.8.50from
tuandinh0801:feat/grok-build-cli-support

Conversation

@tuandinh0801

Copy link
Copy Markdown
Contributor

Summary

  • Add a Grok Build card to the CLI Code dashboard.
  • Configure the main model and Grok Build subagent model overrides.
  • Preserve unrelated TOML data and restore prior mappings on reset.
  • Resolve config.toml through GROK_HOME or the CLI config home.
  • Integrate status detection, endpoint display, backups, and restore.
  • Omit API keys from settings responses.

Closes #10829

@diegosouzapw
diegosouzapw merged commit 6fd4040 into diegosouzapw:release/v3.8.50 Aug 21, 2026
4 of 7 checks passed
xiaoyaner0201 added a commit to xiaoyaner0201/OmniRoute that referenced this pull request Aug 21, 2026
…fd4040)

Additive two-parent merge onto the current live head, which advanced again during
O5/R6 from b87056a to 6fd4040 (five commits: diegosouzapw#10830 Grok Build custom host,
diegosouzapw#10854 skills marketplace API-key installs, diegosouzapw#10804 Cursor account Agent endpoint,
diegosouzapw#10531 freebuff translate-path golden regen, diegosouzapw#10805 SSE silent-close truncation).

Zero file overlap with this PR's 34-file diff; the merge is conflict-free and
introduces no adaptation of either side. No force, rebase, amend, or squash.
muhamadgalihsaputra pushed a commit to niyatna/NiyatnaRoute that referenced this pull request Sep 27, 2026
…#10830)

Adds a Grok Build card to the CLI Code dashboard: configures the main model and per-subagent model overrides, surgically upserts only the [model.omniroute] section of config.toml (preserving unrelated user sections), resolves config.toml via GROK_HOME or the CLI config home, and omits API keys from settings responses. Closes diegosouzapw#10829.

Validated in an isolated worktree boarded onto origin/release/v3.8.50 (0 conflicts, 14 files):
- 6/48 focused node:test cases in tests/integration/cli-settings-grok-build.test.ts initially failed with 422 instead of 200/409 — traced to this route being the first CLI-tool settings route to actually pass a targetPath into the shared guardCliConfigWrite/ensureCliConfigWriteAllowed container-ephemeral-write guard (every other cli-tools/*-settings route calls it with no path, which always no-ops). This devbox genuinely runs inside Docker with no bind mount for the test's tmpdir fixtures, so the guard correctly refused — a real environment-dependent gap in the PR's own test setup (missing OMNIROUTE_ALLOW_CONTAINER_CONFIG_WRITE=1, the pattern already used by tests/unit/cli-tools-apply-container-422.test.ts for this exact guard). Fixed by setting that flag in the test file's setup, pushed fix-in-place.
- 61/61 tests pass after the fix (grok-build-config, check-tool-config-status, all-statuses-route, cli-settings-grok-build, plus 13/13 UI tests via vitest for GrokBuildToolCard/ToolDetailClient).
- Verified the "omit API keys from settings responses" claim: GET applies omitApiKeys() to both config/settings before responding.
- check-file-size, check-changelog-integrity: OK.
- typecheck:core: clean.
- check-complexity / check-cognitive-complexity: OK, both under baseline.

Co-authored-by: tuandinh0801 <tuandinh0801@users.noreply.github.com>
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.

feat(providers): Support Grok Build custom host configuration

3 participants