readonly-mode

You can enable read-only mode by running the enable-readonly-mode.sh script, which creates a persistent marker file to block write operations. This marker enforces a safe no-write state across tools and sessions to prevent unintended changes.

A marker file, specifically named .gemini_readonly, is a persistent file created to enforce read-only mode across tools and sessions. It acts as a signal to block write-capable tools from modifying the live project during critical tasks.

You should lock a project into a read-only state when you need to prevent accidental edits during critical tasks like auditing, code review, or safe collaboration. It creates a persistent marker to ensure no unintended modifications occur.

Yes, read-only mode persists across sessions and tools by creating a persistent marker file. This ensures that write-capable tools are continuously blocked from making accidental modifications in the live project environment.

Yes, you can run the enable-readonly-mode.sh shell script to quickly activate read-only mode. This creates a marker file that blocks write operations, protecting your project from unintended changes during reviews or audits.

The best way to enforce a no-write state is to create a persistent marker file that blocks write-capable tools. This approach prevents accidental modifications across sessions, ensuring safe collaboration and auditing.