Bitter Frontier What coding agents just made possible, where the bottleneck moved, and what deserves attention.

Evidence record / grok-build

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-09-21-grok-build-public-changelog-is-a-curated-lagging-subset-the-in-tree-notes-are-the-fuller-record

Public changelog is a curated, lagging subset; the in-tree notes are the fuller record. The contract names x.ai/build/changelog as the dated operator channel. In this window it trailed builds by at least 9 days and dropped a permission-default line.

Channel: docs-only. Half: defect. Date: window.

Operator consequence: Read crates/codegen/xai-grok-shell/changelogs/<version>.md at a pinned sync for what a version changed, not the web page. For 1.0.9 specifically, the default mode flip to auto and back happened inside one release; if you installed 1.0.9, check that new sessions start in ask. 1.0.11 made the default mode configurable (“Default permission mode for new interactive sessions is now configurable”).

Receipt

Finding metadata

Confidence
high

Run: 2026-09-21-weekly-digest-2026-08-20_2026-09-21-frontier-v0

Finding ID: 2026-09-21-grok-build-public-changelog-is-a-curated-lagging-subset-the-in-tree-notes-are-the-fuller-record

Profile citations

Source links

Primary links, including exact changelog lines when available.

  1. Grok Build
    official docs2026-09-21-grok-build-public-changelog-is-a-curated-lagging-subset-the-in-tree-notes-are-the-fuller-recordweb.archive.org/web/20260906084923/https://x.ai/build/changelogtagged commit file2026-09-21-grok-build-public-changelog-is-a-curated-lagging-subset-the-in-tree-notes-are-the-fuller-recordxai-org/grok-build / crates/codegen/xai-grok-shell/changelogs/1.0.9.md

Versioned source: run artifact