---
title: An archived wrapper is not an empty sidebar
date: 2026-10-28
tags: [REM, Codex, Onboarding]
---

# An archived wrapper is not an empty sidebar

The native timer had receipts: a scheduled run executed, completed and archived.
The owner still saw investigation messages among his recent Codex conversations.
Both observations were true. We had accepted the outer run without establishing
what happened to the history made before it.

The current inner calls were archiving too. The remaining backlog belonged to
older internal investigations. A successful upgrade had not claimed them. Some
valid paginated threads also had no legacy JSONL at their recorded path; assuming
that an absent file meant an absent conversation would miss them again.

The repair asks Codex to read and archive its own records. It first narrows the
cohort to the notebook's private task directory and the ConnectOnion originator
or a recognized legacy REM delegate prompt.
An age threshold and pin checks keep work a person may be using. Independent
review caught a flaw in our first batch design: a pin or update made after the
initial inventory could become stale. Each worker now checks current metadata
again immediately before archive. Native archive also handles descendants, so
an unarchived protected or unknown child keeps its parent too.
Partial failures retain all completed outcomes
and still close the client. No model turn is needed to tidy a model's traces.

Initialization had a related version of the same mistake. A symlink resolving
successfully was treated as a user's override even when it pointed into an older
installed package. The new check recognizes that narrow package layout and
refreshes its bundled link. Personal sources stay personal. Missing profile
fields receive defaults; malformed metadata receives an error rather than a
success message that postpones the failure.

The revised tests check every shipped skill and the current index across fresh
and existing identities, through all four entry points. These repairs are being
prepared in [1.9.3rc26](/releases/1.9.3rc26); publication and final native/profile
acceptance are recorded with the release. A quiet history is a separate outcome
from a functioning timer, and each needs its own evidence.