BashGuard
A local-first security and observability companion for Pi coding-agent sessions.
I started BashGuard because I wanted a better answer to a simple question after an agent session: what actually happened? Pi remains the place where I work with the agent. BashGuard records and presents evidence around that work so I can inspect the execution story without pretending the evidence is more complete than it is.
What works today
BashGuard is intentionally observation-first today. Its current job is to make Pi session evidence easier to inspect and reason about.
- Discover locally recorded Pi sessions
- Attach to a session and follow events live
- Inspect recorded prompts, tool calls, commands, and file activity
- Debrief session evidence alongside Git snapshots
- Surface evidence-based, non-blocking risk notices
- Call out partial, missing, truncated, or redacted evidence
What it does not do yet
These are roadmap problems, not capabilities I want the project to imply already exist.
- Approve, block, or interrupt commands
- Provide an execution sandbox
- Replay a Pi session
- Restore changes or external side effects
- Prove that a particular event caused a Git diff or remote change
Inspect the evidence, then decide what deserves policy
I'm deliberately starting with observation before enforcement. I want to understand normal execution, where the evidence is reliable, and where it is incomplete before turning observations into project policy. The direction is closer to observe → understand → recommend → review → enforce.
bashguard sessions · bashguard attach · bashguard inspect · bashguard debriefCorrelation is not causal attribution
BashGuard can place recorded prompt, tool, command, file-activity, and Git evidence beside each other. Sometimes there is direct path overlap. Sometimes the relationship is temporal. Sometimes evidence is partial or missing. I want BashGuard to make that uncertainty visible rather than claim that an event caused a Git diff or remote side effect when the evidence cannot establish it.
Follow the project as it changes
This page is the portfolio-level overview and will evolve with the project. The repository README remains the detailed source for installation, current commands, limitations, roadmap, and bug reporting.
github.com/acheltenham/BashGuard ↗