AtMem 2.3.1 — publication failed

Not published. The release workflow exposed a Python 3.10 compatibility defect before package publication and stopped. No GitHub Release, PyPI AtMem package, or npm bridge was published for this tag. Use AtMem 2.3.2 or newer.

AtMem 2.3.1 was intended to be the first published stable release of the standalone encrypted Agent Black Box developed after 2.2.6. Its publication failed before artifacts were uploaded. The release contents below are retained as historical review evidence; 2.3.2 carries the corrected stable release.

What changed since 2.2.6

• Exact host-observed prompts, model input/output, memory context, tool calls, targets, results and errors are encrypted and retained by default. Operators can choose metadata-only capture or switch the recorder off for new events.
• Image, audio, video and document evidence supplied by supported OpenClaw hooks is copied into the portable AtMem Home, encrypted, rendered or played for authorized users, and downloadable only by Evidence Collector or Administrator.
• Four local roles are enforced: Viewer sees metadata, hashes and integrity; Investigator can decrypt, view, play and reconstruct; Evidence Collector can export plaintext and control recording; Administrator also manages accounts, passwords, recovery, restore and home adoption.
• atmem init creates the first Administrator and prints a temporary password. The loopback dashboard supports sign-in, first-login password change, password recovery and compact user administration without an enterprise password policy.
• Memory, evidence, identities, keys, configuration, media and migration receipts resolve from one portable AtMem Home (--home, then ATMEM_HOME, then ~/.atmem). Snapshot, verify, migrate, restore and adopt workflows are included.
• Sessions now open from operational rates and a seven-day health view into a focused master/detail inspector with Summary, Findings and Timeline tabs, then return to the prior list and keyboard focus.
• Personal fact-key retrieval was corrected so a question such as “for my age” can retrieve an authorized age fact without broad unrelated persona injection.
• Delegated providers retain the v1 request/result JSON contract while exact requests and health checks use per-instance HMAC authentication, expiry and replay rejection before provider access; provider results remain Ed25519-signed.
• Native and delegated context delivery is available for OpenClaw, Pydantic AI and LangChain/LangGraph. Full-fidelity installed multimodal capture is currently verified for OpenClaw only.

Install or upgrade

New installation:

python -m pip install atmem==2.3.1
atmem atbot setup
atmem init
atmem dashboard

Upgrade from 2.2.6 or another supported 2.x release:

python -m pip install --upgrade atmem==2.3.1
atmem openclaw upgrade       # when OpenClaw is connected
atmem control verify
atmem home status

Optional framework integrations:

python -m pip install --upgrade 'atmem[pydantic-ai]==2.3.1'
python -m pip install --upgrade 'atmem[langgraph]==2.3.1'

AtMem installs stable atmem-atbot==0.1.0. The matching OpenClaw package is openclaw-memory-atmem@2.3.1.

Migration and opt-in behavior

• Existing databases remain supported in place and are not silently moved.
• For one-folder portability, stop AtMem and connected writers, migrate or snapshot to a destination, verify it, then adopt it. Keep the source until the copied home has been independently inspected.
• Existing capture choices remain unchanged. New configured recorders default to full encrypted capture; changing mode affects new events only.
• Delegated providers and Governed Task State remain opt-in. Old delegated registrations must add a per-instance HMAC credential before enablement.

Compatibility

• Python 3.10–3.13.
• Stable AtBot 0.1.0 as an exact dependency.
• OpenClaw bridge 2.3.1; locked-host tests use 2026.8.1 and the latest-host declaration fixture was verified against 2026.9.4 on 13 September 2026.
• Pydantic AI 2.x, LangChain/LangGraph 1.x and Mem0 2.x provider paths are tested as optional extras and do not enlarge the base install.

Honest limitations

AtMem records what a connected agent supplies at supported boundaries. It does not independently prove that a website, purchase, email, payment or other external effect occurred unless separate evidence is attached. Missing hooks remain unknown, and digest-only historical events cannot be reconstructed.

The portable home is local and single-writer, not cloud sync or multi-primary replication. Stop writers or use home snapshot before copying it. Recipient post-quantum export needs its optional cryptographic backend; local storage uses authenticated symmetric encryption and AtMem application authorization. Measured end-user usability is not yet claimed; static and browser interaction regressions cover the shipped dashboard behavior.