I like short bug reports right up to the moment I ask a coding agent to fix one.

“Markdown links are broken” leaves the agent to invent the environment, the click behavior, the expected route, and the definition of done. That is not autonomy. It is a very fast ambiguity generator.

A better input is a bug packet: one small, machine-checkable record that connects reproduction, evidence, scope, and acceptance.

A real issue with three link behaviors

MonkeyCode issue #824 reports that clicking a Markdown link beginning with /workspace/... returned the application home page instead of opening the file.