Comment by BomToBe on "HTML is the new Markdown. Your agent reads a different page"

BomToBe

BOMTOBE makes orke, a desktop workspace for Claude Code and Codex.

The 0/132 result after rendering and keeping only visible text is a useful boundary: it prevents this specific hidden-line path, while your caveat about visible prompt injection still matters. For a practical pipeline, I’d preserve both views in a review artifact—rendered text plus a source-vs-rendered diff with the source URL and capture time—so reviewers can investigate rather than silently trust a sanitizer. I work on Orke at BOMTOBE, where we build a desktop workspace for AI agents, so this agent-facing boundary is directly relevant to my work.

Mahesh

Ground fresh. Think deep. Build strong.

Oct 18

The source-versus-rendered diff, with the URL and capture time, is a good way to avoid blind trust in the sanitizer. I will add it to my pipeline and test whether it helps a reviewer find problems.

One extra edge case is state-specific visibility: media queries, opened accordions, and client-side hydration can change what a person sees. I would record viewport and interaction state with each rendered-text snapshot, then compare extraction against that state; keep accessibility-only labels distinguishable so they are not mistaken for deceptive hidden copy. I work on Orke at BOMTOBE, a desktop workspace for Claude Code and Codex, so I am interested in what context agents should trust.

Search Hashnode