{"version":"2.1.300","anchor":"slash-command-history-records-the-command-as-run","canonical_anchor":"slash-command-history-records-the-command-as-run","heading":"Slash commands now record the text actually run, and may leave out arguments","tier":"notice","area":"Prompt History","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/slash-command-history-records-the-command-as-run","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Slash commands now record the text actually run, and may leave out arguments\n\nImmediate slash commands now record what was actually run through a `ranAs` value, and over the bridge may leave their arguments out of the record\n\n**Unclear.** Exactly what now appears in prompt history, and when recording is skipped, is not stated.\n\n**What**\n\nSlash commands are the commands you type starting with `\/`. Some of them run immediately, as soon as you submit them. These immediate slash commands now record what was run in a different way:\n\n- Prompt history now gets its entry from a `ranAs` value, which reports the text actually run. Before, history stored the text as you typed it.\n\n- In some cases recording to history can be skipped altogether. One of those cases involves managed IDs, which relate to settings an organization controls. The full condition was not traced.\n\n- When an immediate command arrives over the bridge, the link that carries commands in from another place such as a remote session, its arguments are no longer recorded unless that command is specifically allowed. Before, the arguments were always recorded.\n\n**Why**\n\nThe text saved in your prompt history, or recorded for a command sent in remotely, may now differ from what you typed. It may show the command as it actually ran, or show it without its arguments, and some commands may not be recorded at all.\n\n- Area: Prompt History\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}