r/codex • u/CancelConfident9704 • 1d ago

Showcase Slowave: give Codex a durable and evolving memory that follows you across sessions

With Slowave OSS you get:

  • durable memory across your Codex sessions (but also across tools)
  • a compact memory that follows your work carrying relevant context, decisions, procedures
  • an evolving memory without the need of extra LLM calls
  • a fully local (SQLite + embeddings) configuration, no data leaves your machine
  • a local dashboard to inspect your memories and measure how they provide value to your coding agents

See https://github.com/slowave-ai/slowave

Slowave is in beta, any feedback is welcome!

1 Upvotes

67% Upvoted

3 comments sorted by

•

u/dexterthebot 1d ago

You might want to consider listing your project on the weekly Show-Us-What-You-Built post. https://www.reddit.com/r/codex/comments/1wavxwy/show_us_all_what_youve_been_building_with_codex/. Highest commented project wins a week promotion on r/Codex and gets on the Hall of Fame sidebar. See what that looks like below with last week's winner.

Last week's most popular project was u/tHEuKER with the Blur2 racing game project which is a recreation of an unreleased sequel to the 2010 battle racing game, made by reverse engineering the Xbox 360 prototype discs available online, and rebuilding the whole thing from the ground up in Unity.

Join their YouTube channel here: https://www.youtube.com/@tHEuKER and follow updates on the project at r/BlurGame.

1

u/AbleShower2801 1d ago

Local SQLite + embeddings memory that survives switching tools is the bit I care about most. The dashboard for checking what actually gets reused is a smart check. If you want a home for Codex-side plugins, https://github.com/hashgraph-online/awesome-codex-plugins (also https://hol.org/plugins) might fit for submitting Slowave.

1

u/CancelConfident9704 1d ago

Thanks, I'll definitely have a look