Security

Security

You approve sensitive actions. Reading the project proceeds.

Tetrarch asks before it does something sensitive. Leave those checks on.

Your files

Reading and searching the project proceed. Edits to project files show up for you to review. Changes to configuration, and anything that could expose a secret, still ask. Keep env files and keys out of the chat. Commit with git so you can undo.

Other tools

A tool you connect needs your approval, and so does each call, unless you have allowed that tool. Terminal commands ask by default. Run modes are how you loosen that for commands you trust.

The network

Actions that send data off the machine ask first. The agent does not get a free hand to move your code elsewhere.

Folders you have not trusted

In a folder you have not trusted, Tetrarch will not put the repo into the prompt or stage writes. Trust the folder when you know the code.

If something is wrong

Contact Tetrarch support. Include what you saw and the steps to reproduce it.