tail
A Claude Code settings key, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.
The sort command's output-file flags are no longer treated as write targets for permissions.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.233.
In the changelogs
14Releases whose published page names tail.
-
v2.1.319
Saving long command output checks for more problems before pointing to the file
When Claude Code saves long shell output piped into
tail, it now checks the save folder and free file slots, and cleans up if saving failsfound in this entry's text
-
v2.1.319
Saving output piped into tail is stricter and safer
Claude Code's saving of output piped into
tailnow checks commands more carefully, skips risky shell forms and checks free disk entriesfound in this entry's text
-
v2.1.318
Saving output piped into
tailnow stops when disk space runs lowThe file that keeps what was piped into
tailnow checks free disk space and gives up when space is lowfound in this entry's text
-
v2.1.317
The full-output hint for failed Bash commands now follows a different remote switch
The hint pointing to a failed command's saved full output now depends on a newly named remote switch that falls back to off
found in this entry's text
-
v2.1.317
Full output of a command piped into tail can be saved so Claude reads it instead of rerunning
Behind a server switch, Claude Code can save the full input of a shell command piped into tail and tell Claude where to read it
found in this entry's text
-
v2.1.317
Commands that pipe into tail now keep a copy of the full output
When a shell command pipes its output into tail, Claude Code now saves the full output so it can be read later
found in this entry's text
-
v2.1.309
Claude is told the name of an attached machine and how to check background commands
Instructions about an attached machine now name it, and tell Claude to read a background command's output there because it never reports finishing
found in this entry's text
-
v2.1.281
Agent output_file omitted in diskless launches
Background agents started where there is no disk no longer point to an output file that cannot exist
found in this entry's text
-
v2.1.281
wc path extraction now uses the generic handler
wcnow uses the same file-path handling astail,sortanduniqfound in this entry's text
-
v2.1.280
Clearer message for unreadable large saved-output files on a remote host
Clearer explanation given to Claude when a large tool output is saved to a file it can't read on a remote host
found in this entry's text
-
v2.1.280
Multi-machine tool-output truncation notice
Claude now gets told when a teammate's tool output was truncated and the full output only exists on their machine
found in this entry's text
-
v2.1.268
Hook-injected transcript entries can now be placed at head or tail, not just prepended
Hooks can now insert transcript entries at the tail as well as the head
named in this entry
-
v2.1.233
sort output-file targets are no longer extracted as paths
The
sortcommand's output-file flags are no longer treated as write targets for permissions.found in this entry's text
-
v1.0.89
Expanded Bash Command Permission Tracking
found in this entry's text
First cited
0No release's published evidence quotes this name. The ledger indexes the Evidence lines of every changelog on this site, so this says nobody here has ever quoted it; it says nothing about how old the name is.
Presence across releases
0The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.