Direct read-write access
Select a folder to validate and apply changes in place. Your browser will ask for permission only after you click.
Step 1
Choose your local project
Weaver indexes names and metadata first. File contents are read only when a change-set needs them.
Read-only fallback
Use this when direct folder writing is unavailable. Weaver can still simulate, preview, copy, and download results.
Browsers cannot reliably represent a completely empty folder through this fallback.
Default exclusions
Directories listed here are not indexed. A change-set targeting one will fail clearly.
Change this list before selecting a project. Re-select the folder after editing it.
Selected project
- Indexed files
- 0
- Indexed folders
- 0
- Excluded folders
- 0
- Access mode
- —
Browser compatibility and privacy details
Direct writing generally requires a Chromium-family browser, a secure context such as HTTPS or localhost, and the File System Access API. Opening Weaver as a local file may still support read-only fallback ingestion, but browsers do not allow service workers from local file URLs.
Installable offline-app support requires HTTPS or localhost. Weaver’s service worker caches only its own application files—never project files, imported JSON, previews, reports, or snapshots.
Browser filesystem operations are not genuinely atomic. Weaver performs complete preflight checks, revalidates files immediately before writing, and captures rollback data. Git or an independent backup remains the strongest protection.
Checking install and offline capabilities…
Rollback snapshots
Snapshots remain local and are not removed when you start a new task.
No snapshots are available.
Step 2
Add the JSON change-set
Paste JSON, choose a UTF-8 JSON file, or drop one below. Imported text remains editable.
Drop one JSON file here
or
Step 3
Preflight results
Every operation must pass before Weaver permits writing.
Operations
Step 4
Preview resulting files
Line numbers are for display only and are never used to apply changes.
Select a file
Step 5
Apply approved changes
Weaver will re-read every affected path before the first write.
Keep an external backup when possible.
Browser writes cannot be made as one atomic transaction. Weaver will create a rollback snapshot and attempt restoration if a write fails.
Step 6
Results
Select a file
Machine-readable result report
Copy this report back to the separate AI Builder if diagnosis is needed.