{"version":"2.1.265","anchor":"shelltoolcommand-bash-executions-now-default-to-inserting","canonical_anchor":"shelltoolcommand-bash-executions-now-default-to-inserting","heading":"shellToolCommand : bash executions now default to inserting a 'cc-shell' background-task join marker","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/shelltoolcommand-bash-executions-now-default-to-inserting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### `shellToolCommand`: bash executions now default to inserting a 'cc-shell' background-task join marker\n\nBash commands now default to a 'shell' execution class that inserts a background-task join marker\n\n**Unclear.** What the cc-shell join marker is used for downstream, and whether it's visible to users, isn't shown by the finding.\n\n**What**\n\nBash command execution now defaults its internal cgroup class (a grouping used to manage resource limits) to `\"shell\"`. Whenever that class is `\"shell\"`, a new `shellToolCommand` setting kicks in and causes the command builder to prepend a small marker command, referred to as a `cc-shell` join marker, before running the actual command.\n\n**Why**\n\nThis appears to be internal plumbing for tracking or synchronizing background shell tasks; the finding doesn't specify what user-visible behavior depends on this marker.\n\n- Area: Elsewhere\n- Names: `cc-shell`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}