joeljoseph_

3 ms·

1. 1.▲
   Show HN: OpenTimelineEngine – Shared local memory for Claude Code and codex(github.com)

   1 points by joeljoseph_ 7mo ago|0 comments
2. 2.▲
   by joeljoseph_ 7mo ago

   [Experimental Project] I use both OpenAI Codex and Claude Code daily on the same codebase. The biggest pain — they don't share memory. Claude fixes a bug, Codex repeats it next session. Every session starts from zero. So I built Open T
3. 3.▲
   Show HN: OpenTimelineEngine – Shared local memory for Claude Code and codex(github.com)

   3 points by joeljoseph_ 7mo ago|1 comments
4. 4.▲
   by joeljoseph_ 7mo ago

   Great point, and yes, that’s exactly where this is heading. policy driven persistence and compaction is planned, and parts of the lifecycle are already live.
5. 5.▲
   by joeljoseph_ 7mo ago

   [Experimental Project] I use both OpenAI Codex and Claude Code daily on the same codebase. The biggest pain — they don't share memory. Claude fixes a bug, Codex repeats it next session. Every session starts from zero. So I built Open T
6. 6.▲
   Show HN: OpenTimelineEngine – Shared local memory for Claude Code and codex(github.com)

   5 points by joeljoseph_ 7mo ago|2 comments
7. 7.▲
   by joeljoseph_ 7mo ago

   yeah that's a real concern. Few things I do: Patterns aren't blindly trusted — they carry confidence scores and need real evidence before they go active. Low-confidence stuff never drives autonomous execution. If something wrong g
8. 8.▲
   Open Timeline Engine – Local first behavioral cloning for AI agents via MCP(github.com)

   2 points by joeljoseph_ 7mo ago|3 comments
9. 9.▲
   by joeljoseph_ 7mo ago

   [Experimental Project] I use both OpenAI Codex and Claude Code daily on the same codebase. The biggest pain — they don't share memory. Claude fixes a bug, Codex repeats it next session. Every session starts from zero. So I built Open T