{"version":"2.1.265","anchor":"editwritenotebookedit-style-tools-refactored-to-a-per-sess","canonical_anchor":"editwritenotebookedit-style-tools-refactored-to-a-per-sess","heading":"Edit\/Write\/NotebookEdit-style tools refactored to a per-session create() factory","tier":"internal","area":"Tooling Architecture","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/editwritenotebookedit-style-tools-refactored-to-a-per-sess","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Edit\/Write\/NotebookEdit-style tools refactored to a per-session `create()` factory\n\nEdit, Write, and Read\/PDF tools were refactored internally to build themselves from a per-session factory function\n\n**What**\n\nThe internal implementation of tools like `Edit`, `Write`, and the reader that handles files and PDFs was restructured. Previously each tool had flat methods for checking permissions, validating input, and running. Now each tool has a `create()` factory function that builds those methods bound to the specific session and context of the current invocation, giving uniform access to things like permissions, the tool list, remote-call handling, and the active model.\n\n**Why**\n\nThis is an internal code reorganization with no described effect on what these tools do from a user's perspective; it standardizes how the tools are built internally.\n\n- Area: Tooling Architecture\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}