tip: click a tool card to expand and see its parameters. Use the toggles on the Tool State tab to enable/disable specific tools and actions.

two gates: approving installs a tool — registered, visible, and switched off. You enable it separately on the Tool State tab. Read the runs line, not the description: that's what actually executes. Rejecting requires a critique, and the proposer reads it and can revise.

override layer: tools ship with Nano-floor defaults at the call site; this shows only the operator overrides on top. Secrets are masked.

enable/disable: toggle tools and their sub-actions on or off. A disabled tool is refused at call time — the LLM gets a clear "disabled by the operator" error immediately. (Toggles here are in-memory and reset on restart; to persist a disable, add the tool to dashboard.tools_disabled in seren-workbench.yaml.)

content-blind: entries capture metadata only — tool name, duration, success/failure. Argument values and result text are intentionally not stored.