Support that starts with the exact failure.

Before opening an issue

• Run Living Architecture Nodes: Scan Workspace again.
• Confirm the workspace folder you expect is the one VS Code opened.
• If a write action is unavailable, check whether the workspace is trusted.
• For stale-node results, compare the source file timestamp with its companion .node.md file.
• For exports, check the configured livingArchitectureNodes.exportPath and keep it inside the workspace.

What helps reproduce it

• Living Architecture Nodes extension version.
• VS Code version and operating system.
• The command you ran and the result you expected.
• The exact error message, if one appeared.
• A minimal reproduction that does not expose private repository content.

Public issue tracker →

Why some actions are read-only

Scanning can run in Restricted Mode. Generating .node.md drafts and writing diagnostic exports require Workspace Trust because those commands modify files.

That boundary is deliberate: opening an unfamiliar repository should not silently give the extension permission to write into it.

A draft is not verification

Generated node files are structural starting points. Review and populate them before relying on them as architecture memory. The extension does not claim that generated text is verified architecture truth.

Do not paste private material into a public issue

Do not post credentials, private repository contents, entitlement tokens, customer data, or exploitable private details in GitHub Issues. Use the private Altru.dev contact route for security-sensitive reports.

Contact Altru.dev →

Marketplace distribution

The supported public install channel is the Visual Studio Marketplace. If the extension behaves differently after an update, include both the current version and the last version that worked in your report.

Open Marketplace listing →