- Who it helps
- Developers supervising changes across a repository.
- Availability
- Public MIT repository by Tapas Kar, checked October 31. The README documents an npm command and local UI; installation was not tested.
What gets mapped
A JSON model assigns file paths to components and marks areas such as authentication. CI checks can detect unmapped files and stale path patterns. This checks map coverage, rather than proving that a code change is safe.
Archwhere maps agent changes to declared system components ↗
Working with agents
The interface uses GitHub issues as component threads. Replies come through an existing agent integration or webhook. The documented merge button uses the operator’s token; credentials, provider access and integration costs remain separate.
Archwhere maps agent changes to declared system components ↗
What you can do
- Read the primary evidence and its stated access limits before designing a trial. Open reference ↗
Where the evidence stops
Guessed component types and automatically adopted paths need review. No package, workflow or agent integration was executed.
Sources read. Sources checked October 31, 2026 UTC. No third-party software, model inference or complete workflow was executed.
Sources & further reading
GitHub · implementation
Archwhere maps agent changes to declared system components ↗
Primary documentation checked; no workflow executed or reported result reproduced.
Tapas Kar · page checked 2026-10-31
Coverage note: Independent attention and end-to-end execution remain unverified.
The record over time (1)
Dated source checks and published explanations. An observation date can differ from the original release date.
- · Added to Current
Archwhere puts pull requests and agent conversations on a maintained architecture map.