{"version":"2.1.319","anchor":"plugins-can-supply-a-subagentstatusline-command","canonical_anchor":"plugins-can-supply-a-subagentstatusline-command","heading":"Plugins can supply a subagentStatusLine command","tier":"use","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/plugins-can-supply-a-subagentstatusline-command","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Plugins can supply a subagentStatusLine command\n\nA plugin's settings can now provide a subagentStatusLine command, which gets CLAUDE_PLUGIN_ROOT and CLAUDE_PLUGIN_DATA\n\n**What**\n\n`subagentStatusLine` lets a command rewrite rows in the subagent task display. A subagent is a helper Claude starts to work on part of a task. A plugin can now provide this command:\n\n- A `subagentStatusLine.command` in a plugin's `settings.json` is registered with that plugin's data folder. If the folder cannot be created, an error is logged and the command does not run.\n\n- These commands receive `CLAUDE_PLUGIN_ROOT` and `CLAUDE_PLUGIN_DATA`, the plugin's own folder paths. A command that needs these variables but does not come from a plugin is skipped. Before, `subagentStatusLine` ran without them.\n\nThe same change adds a new prompt asking whether to download a connector's files, answered as allowed or declined.\n\n**Why**\n\nPlugins can ship subagent status line commands that rely on their own paths. A command that needs plugin variables without having them is skipped, not run.\n\n- Area: Plugins\n- Names: `subagentStatusLine`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}