snare 1.8.0 — a block explains what it caught

When snare blocks something, it now tells you exactly what it caught, and gives it to you in a form you can copy.

What snare caught, up front

A block now opens with each file and line snare suspects, why, and the text that matched. The whole message is also saved to ~/.snare/logs/last-block.txt. Print it again any time:

snare gate report

Paste it into your own agent, an issue or a chat to work out what it is. An agent's transcript scrolls away; the report stays.

Read it yourself before you allow it

A block can be a false alarm: a minified file, an unusual config. If you think it is one, the message now says what to do first:

1. Open every flagged file and read it in full, not just the flagged line.
2. Check who added it and when: git log -p -- <file>.
3. Only then, in your own terminal, run the snare gate allow … command the block prints.

An agent can help you understand the code. But an agent reading a poisoned repository can be talked into calling it safe, so the decision has to rest on what you read.

Not sure, or it looks real? snare respond takes charge of the clean-up.

For coding agents

The instructions snare agents install writes now tell agents to show you the whole block message, not a summary. Run snare agents install again to refresh them.

Update

snare update && snare selftest

132 self-test checks pass.