Skip to content
BabelBabel Docs

Permissions and approvals

Babel’s permission model is explicit rather than ambient: tools that affect your system or repository surface their activity, and mutating work happens under approval behavior you configure.

What you will see

Section titled “What you will see”
  • Tool rows in the TUI: reads, searches, edits, and commands appear as they happen.
  • Just-in-time approval: when a tool needs permission under your current approval profile, Babel asks at that moment.

Configuring approval behavior

Section titled “Configuring approval behavior”

Inside a session:

/permissions   show or set the approval profile

The current profile applies to the session; check /permissions after changing settings to confirm what is active.

Boundaries you should not assume away

Section titled “Boundaries you should not assume away”
  • Permission approval is a UX layer on top of execution isolation, not a substitute for it. The execution profile still governs how commands run (container vs host).
  • This page describes documented behavior of the product; it is not a compliance certification and does not promise that every riskful action is intercepted in every environment. Read the cited source for the current implementation.