[ DOCUMENTATION ]
Permissions and approvals
What Hearth may do on its own, what it must ask about, and how to change both.
ON THIS SITE
Hearth is built to ask. Reading files inside your project is always allowed. Editing files inside your project is allowed and always shown as a diff. Anything else asks first.
The three answers
When Hearth asks to run a command you can press y to allow it once, a to allow it for this project, or n to say no and tell it what to do instead.
Rules you can write down
Approvals given with a are saved in hearth.toml. Commit that file and your whole team shares the same rules. You can also list commands that are never allowed, such as anything that deletes a database.
Hearth is built to ask. Reading files inside your project is always allowed. Editing files inside your project is allowed and always shown as a diff. Anything else asks first.
The three answers
When Hearth asks to run a command you can press y to allow it once, a to allow it for this project, or n to say no and tell it what to do instead.
Rules you can write down
Approvals given with a are saved in hearth.toml. Commit that file and your whole team shares the same rules. You can also list commands that are never allowed, such as anything that deletes a database.
Was this page helpful?
Yes
Not quite
