From 2f182cba408350fce9e5f921e7a062370e79837b Mon Sep 17 00:00:00 2001 From: Ulises Chavarria Date: Mon, 31 Aug 2026 11:41:54 -0700 Subject: [PATCH] docs(agentic-ai): sync railguard blurb, trim fence path comment MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit CLAUDE.md's railguard banner now matches what railguard actually snapshots — file writes and approved memory deletions, not file writes alone. In railguard.yaml, the four-line history lesson on why both ~/Github and ~/github are fenced shrinks to one line stating the rule: the fence matches literally and Linux paths are case-sensitive. Co-Authored-By: Claude Opus 5 --- agentic-ai/Claude/CLAUDE.md | 2 +- agentic-ai/Claude/railguard.yaml | 5 +---- 2 files changed, 2 insertions(+), 5 deletions(-) diff --git a/agentic-ai/Claude/CLAUDE.md b/agentic-ai/Claude/CLAUDE.md index 1b70d78..edd162d 100644 --- a/agentic-ai/Claude/CLAUDE.md +++ b/agentic-ai/Claude/CLAUDE.md @@ -15,7 +15,7 @@ next to this file. # Railguard - Active Guardrails -Railguard monitors every tool call in this session: allow, ask, or block. If a command is blocked, do NOT re-issue it with cosmetic changes (new flags, encoding, wrappers) - take a genuinely different approach. On ask, wait for the human. File writes are snapshotted and can be rolled back. +Railguard monitors every tool call in this session: allow, ask, or block. If a command is blocked, do NOT re-issue it with cosmetic changes (new flags, encoding, wrappers) - take a genuinely different approach. On ask, wait for the human. File writes and approved memory deletions are snapshotted and can be rolled back. Full agent guide (rollback commands, policy customization, path-fence quirks, self-protection): run `railguard guide`. diff --git a/agentic-ai/Claude/railguard.yaml b/agentic-ai/Claude/railguard.yaml index cf30a69..1126edc 100644 --- a/agentic-ai/Claude/railguard.yaml +++ b/agentic-ai/Claude/railguard.yaml @@ -33,12 +33,9 @@ fence: allowed_paths: - "~/.claude" - "/tmp" + # Paths are case-sensitive, supporting both - "~/github" - "~/Github" - # Both cases: the fence matches literally and Linux paths are - # case-sensitive, so "~/Bitbucket" alone never matched the actual - # ~/bitbucket checkouts — which is why projects there had to enumerate - # every subpath by hand. - "~/bitbucket" - "~/Bitbucket" denied_paths: