HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
peg
rampart
Go2026–2026
peg / rampart

rampart

Open-source firewall for AI agents. Policy engine that audits and controls what OpenClaw, Claude Code, Cursor, Codex, and any AI tool can do on your machine.

2Distinct people
3Mentions
0Explicit recommenders
92GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Open-source firewall for AI agents. Policy engine that audits and controls what OpenClaw, Claude Code, Cursor, Codex, and any AI tool can do on your machine.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 6:28:55 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day3 dated mentions

Observed mentions: 2026-02-11 16:28:42 UTC to 2026-02-25 20:48:40 UTC.

012026-02-11 00:00:00 UTC to 2026-02-12 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 112026-02-12 00:00:00 UTC to 2026-02-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-13 00:00:00 UTC to 2026-02-14 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-02-14 00:00:00 UTC to 2026-02-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-15 00:00:00 UTC to 2026-02-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-16 00:00:00 UTC to 2026-02-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-17 00:00:00 UTC to 2026-02-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-18 00:00:00 UTC to 2026-02-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 182026-02-19 00:00:00 UTC to 2026-02-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-20 00:00:00 UTC to 2026-02-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-21 00:00:00 UTC to 2026-02-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-22 00:00:00 UTC to 2026-02-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-23 00:00:00 UTC to 2026-02-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-24 00:00:00 UTC to 2026-02-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-25 00:00:00 UTC to 2026-02-26 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 25

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 112026-02-11 00:00:00 UTC2026-02-12 00:00:00 UTC110
Feb 122026-02-12 00:00:00 UTC2026-02-13 00:00:00 UTC000
Feb 132026-02-13 00:00:00 UTC2026-02-14 00:00:00 UTC110
Feb 142026-02-14 00:00:00 UTC2026-02-15 00:00:00 UTC000
Feb 152026-02-15 00:00:00 UTC2026-02-16 00:00:00 UTC000
Feb 162026-02-16 00:00:00 UTC2026-02-17 00:00:00 UTC000
Feb 172026-02-17 00:00:00 UTC2026-02-18 00:00:00 UTC000
Feb 182026-02-18 00:00:00 UTC2026-02-19 00:00:00 UTC000
Feb 192026-02-19 00:00:00 UTC2026-02-20 00:00:00 UTC000
Feb 202026-02-20 00:00:00 UTC2026-02-21 00:00:00 UTC000
Feb 212026-02-21 00:00:00 UTC2026-02-22 00:00:00 UTC000
Feb 222026-02-22 00:00:00 UTC2026-02-23 00:00:00 UTC000
Feb 232026-02-23 00:00:00 UTC2026-02-24 00:00:00 UTC000
Feb 242026-02-24 00:00:00 UTC2026-02-25 00:00:00 UTC000
Feb 252026-02-25 00:00:00 UTC2026-02-26 00:00:00 UTC110

What Hacker News says

1 sources
cl4p·Feb 11, 2026Submission

Show HN: Rampart – Open-source security for Claude and AI agents in YOLO mode

I've been running an AI agent 24/7 on my home lab through OpenClaw — k3s cluster management, shell commands, config edits, all unsupervised. I could see what the agent was running, but had no way to stop a bad command before it executed. So I built Rampart. How it works: you write a YAML policy that says what's allowed, denied, or flagged. Rampart evaluates every tool call against that policy before it runs. Here's what a policy looks like: - rm -rf / → denied - sudo anything → logged for review - curl, wget → logged for review - git push, go build, normal dev commands → allowed - cat ~/.ssh/id_rsa → denied Everything gets written to a hash-chained audit trail. You can watch it live with "rampart watch" or generate HTML reports with "rampart report". Setup for Claude Code takes one command: "rampart setup claude-code". It insta
Read the rest
lls hooks that intercept every Bash command, file read, and file write before execution. Blocked commands never run — Claude sees an error and moves on. Setup for OpenClaw agents is also one command: "rampart setup openclaw". Works on Linux and macOS. Also works as a shell wrapper for any agent ("rampart wrap"), an MCP protocol proxy ("rampart mcp"), or an HTTP API that agent platforms can consult before executing anything ("rampart serve"). Go, ~14K lines, Apache 2.0, zero runtime deps. Policy eval takes under 20 microseconds. I'd love feedback on what policies you'd want out of the box and what integrations matter most.
2 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.