What
Some 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:
- Bash, the tool that runs shell commands, is never treated as read-only
- The check of the local git repository's status reports an error straight away
- One internal
PostToolUsehook, which runs after a tool call succeeds, is not registered
The matching error says the tool is unavailable because the session runs file and shell tools only in its cloud environment.
Why
This only affects hosted or remote setups whose tools run with no local disk.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not confirmed that the git status check and the hook change depend on the diskless option.