{"version":"2.1.323","anchor":"projects-context-handles-sessions-without-the-projects-tool","canonical_anchor":"projects-context-handles-sessions-without-the-projects-tool","heading":"Project instructions handle sessions without the Projects tool","tier":"notice","area":"Projects","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/projects-context-handles-sessions-without-the-projects-tool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Project instructions handle sessions without the Projects tool\n\nClaude is now told when it has no Projects tool, and no longer told to call project_info when a Project's docs list fails to load\n\n**What**\n\nA session can be attached to a Project, a collection of docs and files. Claude Code gives Claude instructions about it. Those instructions have changed:\n\n- No Projects tool: a new mode lists synced sources as a count per type. If no Projects tool is available, a section headed \"You have no Projects tool here\" replaces the usage instructions. Before, Claude was always told to use `project_read` and `project_write`.\n\n- Failed docs list: there was a notice for when the list of a Project's docs and files could not be loaded, telling Claude to call `project_info`. It is replaced by the short marker `marker_only_not_a_tool_call`.\n\n**Why**\n\nClaude is less likely to say it can read or edit Project docs, or to try calling `project_info`, in a session where that tool is not there.\n\n- Area: Projects\n- Names: `project_read`, `project_write`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}