This is build 2.1.248, and the /version command exists but is hardwired off.
A /version slash command is compiled in with its enabled check fixed to false, so remote config cannot turn it on.
What's wrong with this entry?
This 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.
- 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.
/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.
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)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
A crashing slash command now tells you it crashed
Both mention slash command
-
v2.1.234
A command can decide from its arguments whether it counts as sensitive
Both mention slash command
-
v2.1.234
A slash-command grouping for a command that does not exist
Both mention slash command