{"version":"2.1.267","anchor":"tengu-input-prompts-effort-level-now-also-factors-in-active","canonical_anchor":"tengu-input-prompts-effort-level-now-also-factors-in-active","heading":"tengu_input_prompt's effort_level now also factors in active permission layers","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/tengu-input-prompts-effort-level-now-also-factors-in-active","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### tengu_input_prompt's effort_level now also factors in active permission layers\n\nThe effort_level recorded with tengu_input_prompt now also accounts for active permission layers\n\n**What**\n\nThe `effort_level` value logged with the `tengu_input_prompt` telemetry event is now calculated using the session's active permission layers (the rules that govern what Claude Code is allowed to do), in addition to the model and input options it already considered.\n\n**Why**\n\nThis makes the recorded effort level reflect permission context as well as model and input settings, giving a more complete picture in telemetry of how a given turn's effort was determined.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}