Automated Claude Project Knowledge Review
Every Monday, WebRun opens your Claude project, reads the files sitting in project knowledge, compares each against the current version of that document, lists anything that is out of date with the version that should replace it, records the review in Airtable, and updates the Notion source index while leaving every removal for you to approve.
How do I keep a Claude project's knowledge files up to date?
WebRun opens your Claude project every Monday and reviews the files sitting in project knowledge, checking each one against the current version of the same document. It logs what is current and what is stale in Airtable, updates the Notion source index, and leaves every removal for you to approve.
- Answers come from the current price list or policy, not last quarter's
- Every stale file is named with the date it went out of date
- Removals stay a human decision, so nothing disappears by surprise
Built for operations teams · knowledge managers · consultancies · support teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
claude.aiin a real browser with your saved login - no setup, no API keys. -
1
Claude - review the project knowledge
claude.ai
WebRun opens Claude to review the project knowledge. - Open the Claude project and list every file currently in project knowledge, with its name and the date it was added
- Compare each file against the current version of that document in your source index
- List any file that has moved on since it was added, naming the current version that should replace it
- Flag the superseded copy for removal but do not delete it. Deleting from project knowledge is left for a person to confirm
- Read the custom instructions and note anything that references a document no longer in the project
Done when Every file in project knowledge is marked current, superseded, or missing.
-
2
Airtable - log what is current and stale
airtable.com
WebRun opens Airtable to log what is current and stale. - Open the knowledge review base in Airtable
- Write one row per file with its name, the date added, the version found, and the verdict
- Keep the history so you can see how long a stale file was sitting in the project
- Total up how many files are current, how many were refreshed, and how many are waiting on your approval to remove
Done when This week's review is recorded file by file in Airtable.
-
3
Notion - update the source index
notion.so
WebRun opens Notion to update the source index. - Update the Notion source index with the current version and owner of each document
- List the superseded files awaiting your approval to remove, with a link to each
- Note any conversation topic where the project answered from a document that has since changed
Done when The Notion index shows the true current state of the project knowledge.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it delete files from my project?
No. WebRun lists what is stale and names the version that should replace it, but adding or removing files in project knowledge is left for you to do. Both are irreversible, so a person always makes that call.
How does it know a file is out of date?
It compares each file in project knowledge against the current version in the source index you point it at, using the version and the last modified date rather than reading the file and guessing.
Does it change my custom instructions?
No. It reads them and reports any instruction that points at a document no longer in the project, but the wording of your instructions is only ever edited by you.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.