{"version":"2.1.296","anchor":"builtintools-option-passed-through-to-the-session","canonical_anchor":"builtintools-option-passed-through-to-the-session","heading":"The builtinTools option now carries through to the session","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/builtintools-option-passed-through-to-the-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### The `builtinTools` option now carries through to the session\n\nA `builtinTools` option is now passed on to the session along with the allowed and disallowed tool lists\n\n**Unclear.** It is not clear whether `builtinTools` is an option you can set yourself, or where it is set.\n\n**What**\n\nClaude Code now passes a `builtinTools` option on to the session it starts, together with the lists of allowed and disallowed tools. Built-in tools are the actions that come with Claude Code, such as reading files or running commands.\n\n**Why**\n\nThis may be a way to choose which built-in tools a session gets.\n\n- Area: Cloud Sessions\n- Names: `builtinTools`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}