Review documentation changes with the evidence beside you.

Use the web workspace

1. Name the watch and enter an official documentation or changelog URL. Its private Space is created automatically; an unrelated Space with the same name stays separate.
2. Optionally choose a connected coding project, select repositories, and confirm each source branch and PR target. Change those branches in Coding before saving if needed.
3. Choose Notify only for change emails without code execution, or Auto-fix + draft PR to assess selected repositories, repair affected code in E2B, run tests, and request reviewer approval before opening draft PRs. Auto-fix requires configured repository tests and draft PRs after checks enabled.
4. New web watches offer daily checks by default; choose manual checks if preferred. Your policy is saved once for future changes. The saved watch shows the next check, linked repositories, blocked repairs, run results, and draft PR links. Nothing merges automatically.
5. Choose Check now when you want to compare a later reading. Open the old and new text, source URLs, reading times, warnings and content hashes.
6. For a pending change, use Find affected code to copy a CLI command for your local repository. Review potential usages alongside the saved page change.
7. If the change is the one you reviewed, select the review checkbox and accept it. Only that exact pending reading becomes the new baseline.

A failed or blocked reading keeps both your baseline and any pending change. Refresh saved state after a conflicting or uncertain request. Refreshing reads the saved result; it does not run another crawl.

What daily checks do

The first check is due 24 hours after enabling Daily. Checks run roughly once a day, with possible maintenance queue delays; the next check time is a due time, not a guaranteed start time. A manual check resets the next daily check to 24 hours later. A scheduled attempt advances the next daily check even if the source fails or the process is interrupted.

Existing manual watches stay manual until their owners enable Daily. Return to API change watches in your workspace to review results, last failed attempts, and retained pending evidence. Enable the optional email-alert checkbox and save to receive change alerts. Alerts obey account email preferences and quiet hours, and repeated readings of the same change deduplicate. Daily checks keep your accepted baseline.

If an older API response omits the schedule, the web page shows it as unknown and disables schedule controls. Refresh saved state to verify it. A missing field does not establish whether daily checks are enabled or disabled.

Continue from your assistant or chat

Connect an MCP client such as Claude, Codex or Cursor, or link Telegram or WhatsApp, to the same account. The hosted watch tools read and change the same saved watches as this workspace. Ask your assistant to list your watches, inspect a pending change, or check the latest documentation.

api_watch_list and api_watch_get read saved state. Creating, checking, scheduling, accepting or removing a watch requires write access and the surface’s action approval flow. Checking always validates the source now using our crawler. Accepting requires the exact pending hash and watch version you reviewed.

Connect repositories and choose their branches in Coding projects, then configure their test commands. You can request a separate bounded coding run or save an Auto-fix watch policy. A branch change requires confirming that policy again. A documentation change alone does not establish that your code needs repair. See sandboxed coding and the MCP tool reference.

Use local baselines in the CLI

The CLI uses the same comparison rules, with snapshots stored on your computer. Local CLI watches and web watches have separate storage; they do not synchronize. Use pm watch remote list and pm watch remote get with a saved watch ID to work with the hosted watches instead. Hosted mutations require the exact observed --version; acceptance also requires the reviewed --hash. See the CLI reference for create, check, schedule, accept and remove.

pm auth login
pm watch add postgres https://www.postgresql.org/docs/release/
pm watch check postgres --output json
# Review the change, then copy its afterHash:
pm watch accept postgres --hash <afterHash>

For CI, pm watch check postgres --fail-on-change --output json exits 3 when changed and 0 when unchanged. Keep the watch directory between CI runs. Other failures use other nonzero statuses. Install the CLI.

Connect through the API

These routes use the base https://api.persistmemory.com/api/v1 and your account’s Bearer credential. Keep credentials on your server. Reads require read scope; mutations require write scope. A watch belongs to its account and an owned Space.

The schedule is manual or daily. Daily watches always include a nonempty ISO nextCheckAt; manual watches omit it. Enabling Daily requires an active Space you own. Pausing with Manual is allowed in an archived Space you own. Schedule changes conflict while a check holds a live lease.

Use the exact version and pending hash from the displayed result. Schedule saves increment the version, so an older review can become stale. On conflict or a lost or unreadable response, refresh and review the saved result before another mutation. Do not blindly repeat the request or substitute a newer version or hash automatically.

Coverage, cost and limits

• Checks run manually or daily after you enable the schedule. Review results in the workspace and optionally scan a local repository with the CLI. Email alerts are optional. Baseline acceptance, applying patches and publishing PRs remain explicit decisions.
• Each account can save ten web watches. Only the baseline and latest pending reading are retained. Deleting a watch frees capacity; archiving its Space does not.
• Documentation pages retain at most 12,000 extracted characters; OpenAPI specifications retain up to 512,000 UTF-8 bytes; SDK feeds retain ten releases with up to 600 note characters each. Coverage limits remain visible. Navigation and formatting changes can appear in page comparisons.
• Every new watch check validates the website now, including conditional requests when the site supports them. Saved web watch checks are at least 60 seconds apart. The review shows when the content was fetched and checked; older saved readings may still be marked cached.
• These comparisons use the existing public reader, no paid crawler and no AI model. JavaScript pages use our configured isolated browser. Pages requiring sign-in or CAPTCHA completion may remain unavailable.
• You can read, pause existing daily checks, or delete watches in an archived Space when no check is in progress. Unarchive the Space before enabling Daily, checking now, or accepting changes. Shared Spaces are not supported for watches.