Summary
Jules' agent journal files (e.g. .jules/bolt.md) get entries with wrong/hallucinated dates: neither today's date nor even a consistent date. The date in the ## YYYY-MM-DD - ... heading appears to be either hallucinated or copied from an existing entry.
Repro / examples (2026-08-11)
Observed on PRs Jules generated against nickdesi/FFBB-MCP-Server today:
- A PR adding an entry to
.jules/bolt.md titled ## 2025-10-18 - [Fast-path redundant truthiness checks and uppercase conversions] — written on 2026-08-11.
- Another PR titled
## 2026-07-22 - Fast-path Integer Type Checking before try-except casting — also written on 2026-08-11, the date was copied from an older entry.
The journal therefore mixes dates (2024-xx, 2025-xx, 2026-07, 2026-08) with no relation to when each entry was actually appended, so the "most recent learning" order is unreliable.
Expected behavior
When Jules appends a learning entry to .jules/*.md, the heading date should be the current real date (same source as the timestamp it uses for branch names like bolt-*-<timestamp>), never a date reused from an existing entry and never a hallucinated one.
Impact
- Inconsistent bot memory: entry order no longer reflects reality.
- Risk the agent relies on stale dates for later tasks (e.g. dedup/triage of obsolete entries).
Workaround applied by the user
Dates were manually corrected to the real date before merging the PRs.
Summary
Jules' agent journal files (e.g.
.jules/bolt.md) get entries with wrong/hallucinated dates: neither today's date nor even a consistent date. The date in the## YYYY-MM-DD - ...heading appears to be either hallucinated or copied from an existing entry.Repro / examples (2026-08-11)
Observed on PRs Jules generated against
nickdesi/FFBB-MCP-Servertoday:.jules/bolt.mdtitled## 2025-10-18 - [Fast-path redundant truthiness checks and uppercase conversions]— written on 2026-08-11.## 2026-07-22 - Fast-path Integer Type Checking before try-except casting— also written on 2026-08-11, the date was copied from an older entry.The journal therefore mixes dates (2024-xx, 2025-xx, 2026-07, 2026-08) with no relation to when each entry was actually appended, so the "most recent learning" order is unreliable.
Expected behavior
When Jules appends a learning entry to
.jules/*.md, the heading date should be the current real date (same source as the timestamp it uses for branch names likebolt-*-<timestamp>), never a date reused from an existing entry and never a hallucinated one.Impact
Workaround applied by the user
Dates were manually corrected to the real date before merging the PRs.