Memory bug

Open 💬 1 comment Opened Apr 25, 2026 by jonekberg

What version of the Codex App are you using (From “About Codex” dialog)?

Codex 26.422.30944

What subscription do you have?

Pro

What platform is your computer?

_No response_

What issue are you seeing?

Chronicle appears enabled and running locally. Recordings and Chronicle memory summaries are actively updating, and local config has features.memories = true and features.chronicle = true. However, new Codex threads are not exposing a ## Memories section to the model, so the Chronicle skill refuses to run. This appears to be a memory/context injection bug rather than a screen recording permission issue.

What steps can reproduce the bug?

can you assess whether Chronicle is working properly

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗