Use Weavatrix Refactor only when the user explicitly requests repository source changes that benefit from a proven refactor workflow: symbol rename, coordinated rename, signature change, symbol edit, selected replacement, import cleanup, file or symbol move planning, deletion readiness, exact plan application, or…
Use Weavatrix Refactor only when the user explicitly requests repository source changes that benefit from a proven refactor workflow: symbol rename, coordinated rename, signature change, symbol edit, selected replacement, import cleanup, file or symbol move planning, deletion readiness, exact plan application, or…
Use Weavatrix Online only for configured Cloud or self-hosted endpoint status, current dependency advisory refresh, bounded installed-package malware review, owner-managed architecture contracts, or explicitly approved source-free graph synchronization. Do not use it for ordinary local code analysis or refactoring.
Use Weavatrix Online only for configured Cloud or self-hosted endpoint status, current dependency advisory refresh, bounded installed-package malware review, owner-managed architecture contracts, or explicitly approved source-free graph synchronization. Do not use it for ordinary local code analysis or refactoring.
Use the Weavatrix MCP as a reusable local repository-intelligence layer: understand unfamiliar applications with a bounded code graph, reduce repeated context, review Health, dead code, duplicates and history, trace endpoints and blast radius, enforce target architecture, and verify changes before a PR.
Apply hash-verified refactoring edit plans: a weavatrix-refactor-js plan producer computes and proves a plan against the read-only core, then applyeditplan previews it (issuing a confirm token), applies with automatic rollback, and verifiedchange proves it. The only Weavatrix component that writes code.