nowfound

Alternatives

Products that do what OperatorX02 AI Code IDE does

Open-source AI IDE with memory that never forgets your code

  1. 1
    Actx0100

    Memory infrastructure for AI agents.

    17d ago · actx0.com

  2. 2

    Persistent memory for Claude Code, Codex & coding agents

    May 2026 · agent-memory.dev

  3. 3

    Persistent memory for AI coding agents

    Apr 2026 · contextpool.io

  4. 4

    Persistent memory for Claude, ChatGPT & Cursor. Free.

    May 2026 · github.com

  5. 5SC

    I got tired of Claude Code forgetting all my context every time I open a new session: set-up decisions, how I like my margins, decision history. etc. We built a shared memory layer you can drop in as a Claude Code Skill. It’s basically a tiny memory DB with recall that remembers your sessions. Not magic. Not AGI. Just state. Install in Claude Code: /plugin marketplace add https://github.com/mutable-state-inc/ensue-skill /plugin install ensue-memory # restart Claude Code What it does: (1) persists context between sessions (2) semantic & temportal search (not just…

    Dec 2025 · github.com

  6. 6AO

    Hi! I’m Nathan: an ML Engineer at Mozilla.ai: I built agent-of-empires (aoe): a CLI application to help you manage all of your running Claude Code/Opencode sessions and know when they are waiting for you. - Written in rust and relies on tmux for security and reliability - Monitors state of cli sessions to tell you when an agent is running vs idle vs waiting for your input - Manage sessions by naming them, grouping them, configuring profiles for various settings I'm passionate about getting self-hosted open-weight LLMs to be valid options to compete with proprietary closed models. One…

    Jan 2026 · github.com

  7. 7
    Atlaso216

    One memory for every AI you use

    Aug 2026 · atlaso.ai

  8. 8MO

    Hey HN! We're Taranjeet and Deshraj, the founders of Mem0 (https://mem0.ai). Mem0 adds a stateful memory layer to AI applications, allowing them to remember user interactions, preferences, and context over time. This enables AI apps to deliver increasingly personalized and intelligent experiences that evolve with every interaction. There’s a demo video at https://youtu.be/VtRuBCTZL1o and a playground to try out at https://app.mem0.ai/playground. You'll need to sign up to use the playground – this helps ensure responses are more tailored to you by…

    2024 · github.com

  9. 9

    The AI teammate for your editor

    Oct 2025

  10. 10

    Comprehensive memory management for Claude Code

    Mar 2026 · codeyam.com

  11. 11

    Portable context for every AI. Never explain yourself twice.

    Jun 2026 · ao2.ai

  12. 12RA

    Hey HN! I built Retain as the evolution of claude-reflect (github.com/BayramAnnakov/claude-reflect). The original problem: I use Claude Code/Codex daily for coding, plus claude.ai and ChatGPT occasionally. Every conversation contains decisions, corrections, and patterns I forget existed weeks later. I kept re-explaining the same preferences. claude-reflect was a CLI tool that extracted learnings from Claude Code sessions. Retain takes this further with a native macOS app that: - Aggregates conversations from Claude Code, claude.ai, ChatGPT, and Codex CLI - Instant full-text…

    Jan 2026 · github.com

  13. 13

    Persistent AI memory across Claude Desktop & Cursor IDE

    Oct 2025

  14. 14

    Persistent, structured memory for AI Agents

    Jan 2026

  15. 15BA

    Tired of AI coding tools that forget everything between sessions? Every time I open a new chat with Claude or fire up Copilot, I'm back to square one explaining my codebase structure. So I built something to fix this. It's called In Memoria. Its an MCP server that gives AI tools persistent memory. Instead of starting fresh every conversation, the AI remembers your coding patterns, architectural decisions, and all the context you've built up. The setup is dead simple: `npx in-memoria server` then connect your AI tool. No accounts, no data leaves your machine. Under the hood it's TypeScript +…

    2025 · github.com

  16. 16
    GPS83

    Memory layer for LLMs that stores repo rules + past lessons

    May 2026 · github.com

  17. 17

    AI-native coding assistant that helps developers in any IDE

    Jun 2026 · polygram.dev

  18. 18TV

    I’m a former Systems Architect (Cisco/VMware) turned builder in Thailand. TheAuditor v2.0 is a complete architectural rewrite (800+ commits) of the prototype I posted three months ago. The "A-ha" moment for me didn't come from a success; it came from a massive failure. I was trying to use AI to refactor a complex schema change (a foundation change from "Products" to "ProductsVariants"), and due to the scope of it, it failed spectacularly. I realized two things: * Context Collapse: The AI couldn't keep enough files in its context window to understand the full scope of the refactor, so it…

    Dec 2025 · github.com

  19. 19
    GitHub10

    Local-first memory for your AI coding agent

    Jun 2026 · github.com

  20. 20MO

    Hey HN! I'm Arindam, part of the team behind Memori (https://memori.gibsonai.com/). Memori adds a stateful memory engine to AI agents, enabling them to stay consistent, recall past work, and improve over time. With Memori, agents don’t lose track of multi-step workflows, repeat tool calls, or forget user preferences. Instead, they build up human-like memory that makes them more reliable and efficient across sessions. We’ve also put together demo apps (a personal diary assistant, a research agent, and a travel planner) so you can see memory in action. Current LLMs are stateless…

    2025 · github.com

  21. 21

    Your AI has your code's text, never its map. Fix that.

    Jun 2026 · luuuc.github.io

  22. 22
    Vexp12

    Cut AI coding costs 58% with pre-indexed codebase context

    Mar 2026 · vexp.dev

  23. 23CO

    Hi HN, I keep running in the same problem of each AI app “remembers” me in its own silo. ChatGPT knows my project details, Cursor forgets them, Claude starts from zero… so I end up re-explaining myself dozens of times a day across these apps. The deeper problem 1. Not portable – context is vendor-locked; nothing travels across tools. 2. Not relational – most memory systems store only the latest fact (“sticky notes”) with no history or provenance. 3. Not yours – your AI memory is sensitive first-party data, yet you have no control over where it lives or how it’s queried. Demo video:…

    2025 · github.com

  24. 24

    Give AI agents long-term memory. Not vector search or RAG

    Dec 2025

Ranked by how close each launch is in meaning, then by votes. Refine with a description →