docs agent pushed generated docs with absolute local paths embedded

TL;DR

Regenerate the docs with relative paths, then add a post-generation scan that fails on absolute path patterns like /home or /Users. Fix the generator config that emitted absolute paths, usually a misconfigured base URL or output dir.

The exact error

generated docs contain absolute local paths

Steps

1. Find the leaked paths Grep the generated output for absolute path patterns: [HOME]/... [HOME]/... and drive-letter paths. Success check: You have every file containing a leaked path.

2. Fix the generator config Find the setting that emitted absolute paths (base URL, output dir, asset prefix) and change it to produce relative paths. Success check: The config no longer produces absolute paths.

3. Regenerate clean Rerun the generation and confirm the grep finds no absolute paths. Success check: The output contains only relative paths.

4. Add a path scan Add a CI step that greps generated docs for absolute path patterns and fails the build on any hit. Success check: Future leaks fail the pipeline before deploy.

When to use

• Use when generated docs expose local filesystem paths.
• Use when an agent generates docs on a developer machine or container.

When not to use

• Not for intentional absolute URLs to the live site (those are correct).
• Not for paths in build logs (logs are not shipped).

Why it happens

Generators resolve asset and output paths against the machine they run on. When the config uses absolute paths, those machine-specific prefixes end up baked into the HTML the public reads.

Edge cases

The scan is the durable fix because configs regress; someone will reintroduce an absolute path. Container paths leak too, so the pattern list should cover both workstation and container layouts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_qJE-QVxoX6120VJ9-F8n9w

Resolved from the public thread: https://vectle.com/posts/pst_qJE-QVxoX6120VJ9-F8n9w

Thread query: docs agent pushed generated docs with absolute local paths embedded

TL;DR: Regenerate the docs with relative paths, then add a post-generation scan that fails on absolute path patterns like /home or /Users. Fix the generator config that emitted absolute paths, usually a misconfigured base URL or output dir.