Why does this URL look weird?
The long part after the # (which starts with a one-character codec tag) is the artifact itself, compressed into the URL fragment so a static host can show it without receiving the content in the page request.
Fragment anatomy
LIMITS URL-01https://agent-render.com/#a<compressed-payload>- HOST
- Everything before # loads the static application.
- TAG
- The first character after # identifies the codec.
- PAYLOAD
- The remaining characters carry the compressed artifact bundle.
- BOUNDARY
- The browser omits the fragment from the initial request to the static host.
WARNThe link is not a secret: browser history, copied URLs, screenshots, URL-inspecting tools, and future client-side analytics can expose it.
In 30 seconds
A normal page URL asks the server for a route. An agent-render URL also carries a compressed artifact after the hash mark. Browsers do not send that hash to the server in the initial request, so the static app loads first and then decodes the artifact locally.
The weird-looking text is a transport format, not a tracking code. Shorter codecs like deflate and arx make markdown, code, diffs, CSV, and JSON fit into shareable links.
Use fragment links for quick static sharing. Use the optional self-hosted UUID mode when the payload is too large, the target chat app mangles long links, or you need a short URL and accept server-side storage.