{"version":"2.1.248","anchor":"version-and-build-stamp-and-the-disabled-version-command","canonical_anchor":"version-and-build-stamp-and-the-disabled-version-command","heading":"Version and build stamp, and the disabled \/version command","tier":"soon","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/version-and-build-stamp-and-the-disabled-version-command","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Version and build stamp, and the disabled `\/version` command\n\nThis is build 2.1.248, and the `\/version` command exists but is hardwired off.\n\n**What**\n\nThis build reports itself as 2.1.248, built 2026-08-27T19:29:54Z, from git sha 8c9482ad0510ad5e3c88f0ebe6f035ec148f73e2. The stamp is what the binary shows about itself everywhere it names its own version. The `\/version` command that would surface it in a session is present but compiled with its enabled check hardwired to false, so it cannot be reached whatever remote config says.\n\n**Details**\n\n- The stamp appears in the user agent, update messages, LSP client info, feedback and bug-report drafts, and the pre-trust security errors for the API-key, AWS auth-refresh, AWS credential-export and GCP auth-refresh helpers.\n- `\/version`, described in the binary as showing this session's version with the note that autoupdate may have a newer one, is unavailable in this build and there is no flag or setting that turns it back on.\n\n**Evidence**\n\n`BUILD_TIME: \"2026-08-27T19:29:54Z\",`, `2026-08-27T19:29:54Z`, `x-environment-runner-version`, `Show this session's version (autoupdate may have a newer one)`\n\n- Area: Slash Commands\n- Names: `\/version`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}