{"version":"2.1.275","anchor":"new-script-activity-indicator-in-tool-use-summaries","canonical_anchor":"new-script-activity-indicator-in-tool-use-summaries","heading":"New 'script' activity indicator in tool-use summaries","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/new-script-activity-indicator-in-tool-use-summaries","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### New 'script' activity indicator in tool-use summaries\n\nTurn summaries can now show a 'script' activity indicator alongside bash, read, and other categories\n\n**Unclear.** The finding does not say what condition triggers the 'script' indicator or what kind of activity it represents.\n\n**What**\n\nWhen Claude Code finishes a turn, it prints a short summary line of what happened (for example, how many files it read or shell commands it ran). That summary can now include a new 'script' category showing a 'working' indicator, alongside the existing bash, read, list, mcp (external tool connections), agent, and repl (interactive code execution) categories.\n\n**Why**\n\nThis gives a more complete picture of what a turn actually did, so script-related activity shows up in the summary instead of being invisible.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}