Tirith — Terminal Security for AI Agents

Practical Notes

• README documents policy init/validate/test commands and a strictness model (paranoia 1–4).
• Install options include Homebrew, npm, Cargo, and OS packages; policy discovery looks for .tirith/policy.yaml.

Where It Fits in an Agent Workflow

If you let an agent propose commands, Tirith can sit in front of execution:

• Use policy tests during planning to catch “curl | bash” and similar source-to-sink flows early.
• Keep a small allowlist (domains you trust) and blocklist (known bad) as code in your repo.
• In CI, apply a stricter scan profile (README shows scan profiles under policy) for configs like .claude/*, mcp.json, and other agent-control files.

Practical “Do This, Not That”

• Prefer pinned installs over curl | bash whenever possible.
• If you must run a script installer, validate the URL (homograph/invisible unicode is a real class of attacks) and record the checksum or release tag you used.

FAQ

Q: Does Tirith execute commands for me? A: It can validate and policy-test commands; the goal is to surface risk before you run them.

Q: Where does the policy live? A: The README states it discovers .tirith/policy.yaml in your repo (walking up), or a user config path.

Q: Can I tune strictness? A: Yes—policy parameters include a paranoia level and action overrides for escalation.