{"version":"2.1.284","anchor":"diskless-cloud-sessions-bash-never-read-only-some-hooks-an","canonical_anchor":"diskless-cloud-sessions-bash-never-read-only-some-hooks-an","heading":"Bash is never treated as read-only in cloud-only sessions","tier":"notice","area":"Diskless Mode","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/diskless-cloud-sessions-bash-never-read-only-some-hooks-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Bash is never treated as read-only in cloud-only sessions\n\nIn sessions that run file and shell tools only in the cloud, Bash is never counted as read-only, and a local git check is skipped\n\n**Unclear.** It is not confirmed that the git status check and the hook change depend on the diskless option.\n\n**What**\n\nSome sessions are launched with a diskless option, which means file and shell tools run only in a cloud environment and never on the local machine. In these sessions:\n\n- Bash, the tool that runs shell commands, is never treated as read-only\n\n- The check of the local git repository's status reports an error straight away\n\n- One internal `PostToolUse` hook, which runs after a tool call succeeds, is not registered\n\nThe matching error says the tool is unavailable because the session runs file and shell tools only in its cloud environment.\n\n**Why**\n\nThis only affects hosted or remote setups whose tools run with no local disk.\n\n- Area: Diskless Mode\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}