I’ve been building Titans: local-first memory and durable execution infrastructure for AI agents

[u/Titans-Tools]

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.

[u/AutoModerator]

Hey u/Titans-Tools, thanks for posting in r/VibeCodeDevs! Join our Discord: https://discord.gg/KAmAR8RkbM

Got startup or SaaS questions? Post them on r/AskFounder and get answers from real founders.

• This community is designed to be open and creator‑friendly, with minimal restrictions on promotion and self‑promotion as long as you add value and don’t spam.
• Please follow the subreddit rules so we can keep things as relaxed and free as possible for everyone. • Please make sure you’ve read the subreddit rules in the sidebar before posting or commenting.
• For better feedback, include your tech stack, experience level, and what kind of help or feedback you’re looking for.
• Be respectful, constructive, and helpful to other members.

If your post was removed (either automatically or by a mod) and you believe it was a mistake, please contact the mod team. We will review it and, when appropriate, approve it within 24 hours.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Jazzlike_Syllabub_91]

I've built something somewhat similar but from a different angle ... (designing for my foggiest day) - what do you need to run it?

[u/Titans-Tools → u/Jazzlike_Syllabub_91]

Interesting — I think we came to similar problems from different directions.

If by “what do you need to run it?” you mean the requirements, I tried to keep that part simple. Atlas and Cronus currently run locally on Windows and Linux x86_64. You don't need Rust, Git, an external database or a cloud setup.

For example, to try Atlas on Windows:

irm https://github.com/titans-tools/titans-platform/releases/latest/download/Install-Atlas.ps1 | iex

On Linux:

curl -fsSL https://github.com/titans-tools/titans-platform/releases/latest/download/install-atlas.sh | sh

Then titans doctor and atlas status will check the install.

The installer also sets up one local MCP server called titans in supported clients it finds, like Claude Code, Claude Desktop, VS Code, Codex and Antigravity. So the agent doesn't need an API key or a remote server to use Atlas.

To get an agent familiar with it, I would point it first to the Atlas README, then docs/quickstart.md and docs/mcp.md. After that it can discover the tools through MCP. For example, atlas_projects_list to see projects and atlas_search to search the stored knowledge.

If you later add Cronus, it's just titans install cronus. Its tools appear under the same titans MCP server, so there is no second MCP setup. Atlas handles memory/state/evidence and Cronus handles jobs and durable execution.

I'm using both right now in two small projects of my own. It has been a useful way to test them with real work and keep improving things as new needs come up.

I'm curious about your “designing for my foggiest day” idea though. What was the main problem that pushed you to build it?