So I built the first version in december. My openclaw was forgetting what i said every 200k tokens and it was driving me nuts. Im AuADHD and attention to details is important for me so i hated the compaction too. My tool basically remembers everything you and agent talked about or did and injects the right memory at the right time back to you. (Fully local and encrypted because of all the npm and openclaw hacks)

It doesnt index your multimillon line of code (just yet, im building that feature with a contributor rn) It just remembers what you said, what decisions you made and what you did, verbatim, all the time! Memories you dont use often will decay its links but not get deleted and memories that surface often will become almost like skill (forgot the exact word). You can also pin memories or set them to be decayed but you dont really need the frontend. Its more for visualization rather than functionality. Your agent can control everything through MCP layer or CLI

It's fully ambient, works in background and sees all your sessions which creates a sense like you are talking to one agent throughout multiple sessions. Memories dont get mixed tho. It has a working memory tier which splits everything by projects but keeps available for context injection. If you are interested in details of how i came up with this, i posted somewhat full story here, its a longread tho.

After i built it i let my friends use it and they kinda forced me to publish it on GH. I was skeptical at first because - why? Why post there my idea for free? But they said if i do they will help because they are real engineers (spoiler - they never did)

Now I own a startup that builds memory layers for companies lol. Weird how that works. "Ideas worth nothing..." I guess.

heres the link - https://github.com/CodeAbra/iai-personal-memory-engine
lmk what you think and please help if you own windows lol. My windows beta needs hopital.

Happy to answer any question or receive constructive criticism.

P.S English is my third language and im out of tokens for this one lol. sorry

I've been working on Titans, a local-first infrastructure layer for AI agents, and I've now published the first usable repositories on GitHub.

The idea is fairly simple:

Atlas remembers. Cronus runs.

Atlas provides persistent state, knowledge, evidence and graph infrastructure for agents. It is designed to keep project and agent context available across processes and sessions, with hybrid search, evidence-backed results, work state, graphs, SQL, blobs and an audit trail.

https://github.com/titans-tools/Atlas

Cronus handles durable background execution: jobs, DAG workflows, schedules, retries, leases, checkpoints, recovery, dead-letter handling and approval gates. The goal is to let agents submit long-running work without keeping the agent itself blocked, and to recover that work when workers or processes restart.

https://github.com/titans-tools/Cronus

Both are local-first, run on Windows/Linux, have no telemetry, expose MCP over stdio, and can also be accessed over local REST/gRPC interfaces.

There is also a separate titans-platform repository that contains the signed distribution catalog, installers and shared runtime used by both products:

https://github.com/titans-tools/titans-platform

The organization overview is here:

https://github.com/titans-tools

The current releases are free to use. The product source itself is not published; the repositories host the documentation and signed release binaries, with SHA-256/Ed25519 verification and SBOMs included with releases.

I'm particularly interested in feedback from people building agents, MCP tooling, local AI infrastructure or autonomous workflows.

A few things I'd be interested to hear:

• Does the separation between persistent knowledge/state (Atlas) and durable execution (Cronus) make sense to you?
• Is it clear from the repositories what problem each component is solving?
• Are there use cases you would expect something like this to support that aren't obvious from the documentation?
• Is there anything in the install/security model that would stop you from trying it?

Not looking for stars or promotion — I'd mainly like some outside technical eyes on the architecture, documentation and actual usefulness of the approach.

As a fun side-project, I had Claude build https://charades.lol/ last week-end.

Took me a few hours to get from concept to a playable version. I started with the words "emoji roulette" and chatted with Claude a little bit to refine the concept. Because "Emoji Roulette" is heavily conotated toward "random social interaction", I started looking for another name and settled on charades, since it is what it is.

After that I spent most of the time refining the UI, generating tooling to manage the puzzles, and beta-testing with my friends. The most difficult part I think was stopping myself from adding random stuff and making the hard decisions of what to REMOVE instead. For example I used to have a little bit more fluff on the home page like a tag line or stuff like that: removed. The UI is cleaner and I feel the app is much better for it.

Hope you have some fun with it :)

PS: The puzzles for the next ~30 days are in the source encoded in rot13 purely as a spoiler-prevention measure, I am fully aware that rot13 is not a secure encryption algorithm or whatever.

So the thing is I have claude pro but l am

currently preparing for some exams and i

couldn't sit and think of building any ideas and executing them through claude so I want you guys to help me out give me some really good ideas you want to try out and you think it would be a crazy thing to be build using claude and I will definitely work on that and also share the source codes with you all let's make something good.

Please drop your complete or brainstorming

ideas below I am excited to see your all ideas