forked from Selig/openclaw-skill
Selig
4c966a3ad2
6 custom skills (assign-task, dispatch-webhook, daily-briefing, task-capture, qmd-brain, tts-voice) with technical documentation. Compatible with Claude Code, OpenClaw, Codex CLI, and OpenCode.
29 lines
1.2 KiB
Markdown
29 lines
1.2 KiB
Markdown
# Elevated Mode Documentation
|
|
|
|
## Overview
|
|
|
|
The Elevated Mode feature (`/elevated` or `/elev` directives) controls execution behavior for sandboxed agents. `/elevated on` runs on the gateway host while maintaining exec approvals, whereas `/elevated full` does the same but auto-approves executions.
|
|
|
|
## Key Functionality
|
|
|
|
**Core behaviors:**
|
|
- `on`/`ask`: Gateway host execution with approval checks intact
|
|
- `full`: Gateway host execution with automatic approval bypass
|
|
- `off`: Disables elevated mode
|
|
- These directives only affect sandboxed agents; unsandboxed agents already execute on the host
|
|
|
|
**Important limitation:** Only changes behavior when the agent is sandboxed; otherwise exec already runs on the host.
|
|
|
|
## Access Control
|
|
|
|
Elevated mode availability is determined by multiple gates:
|
|
- Global feature flag: `tools.elevated.enabled`
|
|
- Per-provider allowlists under `tools.elevated.allowFrom`
|
|
- Per-agent restrictions through `agents.list[].tools.elevated`
|
|
|
|
Discord has a fallback: if no Discord allowlist is specified, the DM allowlist applies automatically.
|
|
|
|
## Usage Methods
|
|
|
|
Users can set elevated mode by sending directive-only messages, check current status with `/elevated:`, or apply directives inline within messages for single-use application.
|