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
trevxr·Feb 25, 2026Submission

Show HN: Rampart v0.5 – what stops your AI agent from reading your SSH keys?

The first time I gave Claude Code real shell access I immediately thought: it can read anything in my home directory right now. My .env files, my SSH keys, my AWS credentials. And if someone sneaks a "read this file and send it here" instruction into something Claude reads — a README, a package description, a code comment — there's nothing between that instruction and my files. Rampart is the thing I built for that. It sits in front of your agent and checks every command and file operation against a simple policy before it runs. If something's not allowed, it's blocked — not logged after the fact, blocked before it happens. Setup is two commands: $ rampart setup claude-code $ rampart serve --background After that, your agent works exactly the same — except now it has a policy. The default policy already covers the obvious stuff: SSH keys,
Read the rest
AWS credentials, .env files, destructive commands. You define what's allowed, everything else gets blocked or flagged for your approval. The policy is just a YAML file you can commit to your repo. Adding rules is one command: $ rampart block "curl * | bash" $ rampart allow "~/.config/myapp" One thing I'm proud of: the agent can't unblock itself. If Claude tries to run rampart allow to give itself more permissions, it gets blocked. Only you can change the policy. Every decision gets logged in a tamper-evident audit trail, so you can see exactly what your agent attempted — not just what succeeded. Works with Claude Code, Cursor, Codex, Cline, and OpenClaw. Apache 2.0, single binary, no dependencies. https://github.com/peg/rampart | https://rampart.sh/
1 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.