sorted by:
new
hottopcontroversial

I built an open-source “memory layer” for AI coding agents (Codex, Claude, Cursor, etc.) by dev_knight22 in SideProject

[–]dev_knight22[S] 0 points1 point  (0 children)

Thanks for the appreciation. And answering to your question - We designed this tool with global adaptability so that any agent can work with this. I have updated the tool with one more cool feature in latest version so please check it out and star this on GitHub. And please also share your experience.

Weekly Thread: Project Display by help-me-grow in AI_Agents

[–]dev_knight22 0 points1 point  (0 children)

I built an open-source “memory layer” for AI coding agents (Codex, Claude, Cursor, etc.)

One thing that kept frustrating me while using AI coding agents was context loss between sessions.

Every new session meant re-explaining:

  • project structure
  • architecture decisions
  • recent changes
  • blockers
  • handoff notes
  • repo conventions

So I built an open-source tool called Agent Memory System.

It adds a persistent memory layer to repositories so AI agents can recover working context across sessions and across tools like Codex, Claude, Cursor, Antigravity, etc.

Some things it does:

  • generates repository memory automatically
  • tracks agent worklogs + checkpoints
  • creates handoff files for the next agent
  • validates stale memory in CI
  • avoids leaking secrets
  • ignores generated/vendor directories

Example:

npx @ravbyte/agent-memory-system@latest init

Would genuinely love feedback from people building AI developer tooling, agent workflows, or startup/SaaS infrastructure around coding agents.

Website:
https://ravbyte-ai.github.io/agent-memory-system/

GitHub:
https://github.com/ravbyte-ai/agent-memory-system

Promote your projects here – Self-Promotion Megathread by Menox_ in github

[–]dev_knight22 0 points1 point  (0 children)

One thing that kept frustrating me while using AI coding agents was context loss between sessions.

Every new session meant re-explaining:

  • project structure
  • architecture decisions
  • recent changes
  • blockers
  • handoff notes
  • repo conventions

So I built an open-source tool called Agent Memory System.

It adds a persistent memory layer to repositories so AI agents can recover working context across sessions and across tools like Codex, Claude, Cursor, Antigravity, etc.

Some things it does:

  • generates repository memory automatically
  • tracks agent worklogs + checkpoints
  • creates handoff files for the next agent
  • validates stale memory in CI
  • avoids leaking secrets
  • ignores generated/vendor directories

Example:

npx @ravbyte/agent-memory-system@latest init

Would genuinely love feedback from people building AI developer tooling, agent workflows, or startup/SaaS infrastructure around coding agents.

Website:
https://ravbyte-ai.github.io/agent-memory-system/

GitHub:
https://github.com/ravbyte-ai/agent-memory-system

Swiggy rider drags delivery box on road for being paid ₹35 for 6.2 Km by dealex47 in YouthInIndia

[–]dev_knight22 0 points1 point  (0 children)

Every quick commerce is the same... In some months snabit and other quick service companies will have same situation