Skip to content
maestro

Read-only mode

Read-only mode is a store access setting, not a team seat; the seats a team opens are in Roles.

Set MAESTRO_READ_ONLY=1 for a process that must fail closed on mutation:

Terminal window
MAESTRO_READ_ONLY=1 maestro status
MAESTRO_READ_ONLY=1 maestro search "<query>"

What it protects

Section titled “What it protects”

The process opens the Maestro store without persisting session, lease or liveness updates. Mutating commands refuse rather than partially writing.

Use it for diagnostics, reporting and bounded inspection where even normal session bookkeeping would be an unwanted side effect.

What it does not do

Section titled “What it does not do”
  • It does not create a monitoring role or background process.
  • It does not read raw Herdr pane transcript.
  • It does not make stale state current.
  • It does not grant access to another project store. maestro search still reads the Hub room at ~/maestro by default (pass --local to skip it); that read is itself read-only.
  • It admits term list|show and memory list|show but refuses memory render --check, which is registered as a writing command. maestro help <verb> marks the admitted verbs with a trailing *.
  • An unknown verb under MAESTRO_READ_ONLY=1 is reported as not admitted, which does not mean the verb exists.
  • It does not replace role-scoped maestro status inside an SLP team.

If a read depends on an index normally refreshed by a write-capable command, refresh that index explicitly outside read-only mode, then retry the read.