{"version":"2.1.290","anchor":"proactivity-level-is-propagated-to-the-remote-client-and-a","canonical_anchor":"proactivity-level-is-propagated-to-the-remote-client-and-a","heading":"Proactivity level changes now reach remote sessions","tier":"notice","area":"Proactivity","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/proactivity-level-is-propagated-to-the-remote-client-and-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Proactivity level changes now reach remote sessions\n\nChanging the permission mode or proactivity level now notifies remote clients, and a `--proactivity` value is recorded with `--permission-mode`\n\n**Unclear.** It is not clear how the recorded `--proactivity` value is used.\n\n**What**\n\nWhen the permission mode or the proactivity level changes during a session, Claude Code now passes the new proactivity level on to the remote client. The permission mode controls how much Claude may do without asking you first.\n\nWhere Claude Code records the options a session was started with, it now records a `--proactivity` value alongside `--permission-mode`. Before, it recorded only `--permission-mode` and `--inherit-permission-mode`.\n\n**Why**\n\nRemote and background sessions now hear about proactivity changes, so they stay in step with the session that started them.\n\n- Area: Proactivity\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}