realvco Docs

ROOT Access Control

Each AI agent settings sub-tab has a “ROOT Access Control” toggle. Lets you time-bound grant this agent host root access. System auto-revokes when expired.

Defaults: OC-1 enabled 72 hours by default; OC-2 / HM-3 disabled.

Where to find

OC-1 (or OC-2, HM-3) tab → Settings sub-tab → ROOT Access Control section

OC-1 Settings sub-tab ROOT Access Control section OC-1 Settings sub-tab ROOT Access Control section
Middle of Settings sub-tab: red dot status + 5 duration buttons

You’ll see:

ElementMeaning
Red dot + Disabled / EnabledCurrent state indicator
5 buttons: Off / 6hr / 24hr / 72hr / 30dClick any → that duration takes effect
Description textExplains post-enable safety behavior

What each option means

ButtonMeaningBest for
OffOff, back to container isolation defaultDon’t need host access
6hrEnabled 6 hours, auto-revoked on expiry”Need to fix a bug tonight, must be done by morning”
24hrEnabled 24 hours”Running data analysis or long task, may need overnight”
72hrEnabled 72 hours (3 days)“Weekend wants to install new MCP server, want it cleaned up by Monday”
30dEnabled 30 days”Doing a project this month, need this agent for host operations all month”

How to do it

Step 1: click your desired duration

E.g. want 6 hours → click 6hr.

Click is immediate (no confirmation dialog — it’s time-bounded and reversible, will auto-revoke).

Step 2: confirm state change

After clicking:

  • Red dot’s Disabled changes to Enabled (X hours X min remaining)
  • Countdown starts

Step 3: don’t have to manually disable

System auto-revokes on expiry, you don’t have to remember. Want to revoke early → click Off.

What happens when enabled

The instant you click a duration:

  1. The AI agent’s container immediately gets host read/write access
  2. Countdown starts (system checks every minute)
  3. When countdown hits zero → auto-revoke, back to container isolation

While enabled, this agent can:

  • Read/write any host file
  • Install/remove software
  • Run system administration commands

⚠️ But disaster-level commands are still blocked:

  • Delete system files
  • Reboot host
  • Modify SSH config

These are built-in, non-toggleable safety nets.

How to confirm ROOT is enabled

You’ll see 3 visual cues:

  1. AI agent tab title shows red [ROOT] badge
  2. Home sub-tab main view shows red text “Host Root access granted”
  3. Countdown timer displays remaining time

If you see ROOT badge but don’t remember enabling it, check audit log for history.

Common scenarios

You want to…Click
Let HM-3 run a one-time system maintenance script6hr
Let OC-2 cross-container debug for a day24hr
Weekend project needs OC-1 for host files72hr
Month-long project / long-term maintenance role30d
Done with task, want to revoke nowOff (don’t wait for expiry)

Safety reminder

Granting ROOT means this AI container can touch anything on the host (except built-in disaster protection):

  • Mistakes the AI makes while executing your commands have larger consequences
  • If this container is compromised, the attacker also gets host access
  • Understand this risk before granting; don’t keep it on long-term “for convenience”

Strongly recommend: before granting ROOT, create a host restore point. One-click rollback in case of issues.