PCS 0.9.121

PCS 0.9.121

PCS 0.9.121 fixes a problem where a temporary provider timeout could leave automatic memory processing paused for the rest of a conversation. PCS now retries eligible temporary failures automatically, so recovering from a brief outage no longer depends on restarting the conversation or pressing Process recent conversation.

• Automatic recovery during a conversation. Timeouts, connection failures and selected temporary server errors now trigger a cooldown. Successive waits are 30 seconds, 1 minute, 2 minutes and then 5 minutes. Retries follow the existing processing schedule and Local quiet-time rules, so an attempt may happen later than the cooldown alone suggests. Each provider attempt may incur charges.

• Fresh checks before retrying. Each attempt reads the current eligible sources and checks the current saving and sharing permissions. Stop, Lock and cancellation retain their protections. Authentication and quota problems still require attention. Explicit Remember requests and corrections are not automatically replayed, and PCS does not repeat a save whose outcome is uncertain.

• Recovery for later memory-search indexing. A temporary failure while creating search embeddings no longer disables indexing for every later memory batch. Older memories missing those search vectors still use the existing Rebuild memory search action; their saved memory content is not regenerated to repair the index.

• More accurate provider handling and saving status. Related provider adapters now distinguish temporary network failures from malformed requests and other errors that should not be retried. Saving & memory health explains when processing is waiting to retry and distinguishes saved original conversation records from completed memories. Updated button references use Process recent conversation. Diagnostics no longer present an unchecked source count as zero pending work.

Upgrading

This release adds no vault-format change or new minimum-reader requirement. Existing feature-specific requirements still apply.

1. Save edits and let work you want to keep finish, then choose Quit PCS and wait for shutdown. Close any other PCS instance using the same data folder.
2. Copy the entire stopped data folder to a separate backup location, keeping the original. If you use a custom data directory, copy that directory.
3. Extract the complete Windows package into a fresh folder and keep it closed. Place a copy of your data folder beside the new Start PCS.exe, without merging it with an existing data folder.
4. Launch PCS, choose Unlock existing with your existing vault passphrase, and check your saved records. Follow the included Backup & restore guidance for Materials.

Keep the previous installation and backup while checking the updated copy. A full data-folder copy can include unencrypted original Materials files, so protect the backup accordingly.

Validation

The final package passed 15,071 Python tests and 3,338 JavaScript tests, with eight documented platform- or permission-dependent Python skips. Fresh offline installation, application lint checks, two native Windows launch/unlock/Lock/Quit cycles, and independent archive and delivered-file verification also passed.

These checks used fictional data and simulated providers. They do not establish live-provider recovery, personal-vault migration, device behavior or long-session reliability.

Release files

• PCS-0.9.121-Windows-x64.zip — complete Windows application.
• PCS-0.9.121-Source.zip — matching source, tests and build support.
• PCS-0.9.121-SHA256SUMS.txt — archive checksums.

Support PCS

If PCS is useful to you, you can help support its development. Support is optional.