codex - 💡(How to fix) Fix Memory bug [1 comments, 2 participants]

TL;DR

The issue may be resolved by verifying the configuration settings for features.memories and features.chronicle to ensure they are correctly enabled for new Codex threads.

Guidance

• Check the local config file to confirm that features.memories and features.chronicle are set to true for the specific Codex thread configuration.
• Verify that the Chronicle skill is properly configured to run with the correct memory and context settings.
• Test the Chronicle feature with a new Codex thread to see if the issue persists.
• If the issue is still present, try resetting the local config to its default settings and re-enable the features to see if it resolves the problem.

Notes

The issue seems to be related to a memory or context injection bug, but without more information about the expected behavior and additional context, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Verify and adjust the configuration settings for features.memories and features.chronicle to ensure they are correctly enabled for new Codex threads, as this appears to be the most likely cause of the issue.