nowfound

Alternatives

Products that do what Decispher – persistent engineering context and memory for coding agents does

Hello HN, I'm Ali, building Decispher. The problem we're working on is that coding agents repeatedly rediscover context that already exists inside an engineering organization. A developer working on a feature can combine information from previous PRs, Jira tickets, Slack discussions, ownership boundaries, architectural decisions and their own experience. Coding agents usually start with a prompt and a repository, then spend tokens searching for that same context—or miss it entirely. Decispher is a context and memory layer for engineering agents. It currently has three parts: 1) Context…

  1. 1

    Memory for coding agents that learns how your team works

    4d ago · decispher.com

  2. 2

    Persistent memory for AI coding agents

    Apr 2026

  3. 3

    Portable memory for agent workflows

    Apr 2026

  4. 4

    Repo-native memory for coding agents

    Jul 2026 · github.com

  5. 5
    Greplica186

    Self updating wiki for coding agents

    Jul 2026 · github.com

  6. 6
    Actx0100

    Memory infrastructure for AI agents.

    16d ago · actx0.com

  7. 7

    Models matter. Context matters more. Give your agent a plan.

    Jun 2026

  8. 8

    The AI coding agent that never compacts

    Feb 2026

  9. 9

    Persistent, structured memory for AI Agents

    Jan 2026

  10. 10
    N71141

    Give all your AI agents one shared context

    Jul 2026

  11. 11
    Memori168

    Persistent memory from agent trace, not just conversation

    May 2026

  12. 12MF

    Hello HN, I created Decispher (decispher.com) to enable human developers and AI agents working alongside each other to share their context. It has some pretty cool features, like Branch Story (explains why a branch's code looks the way it does) and Session Context Transfer (an MCP tool that can copy context from one chat, agent, or machine to another). You can also capture context from engineering platforms like Slack, JIRA, and Git(hub/lab) just by tagging @Decispher.

    Jul 2026

  13. 13DP

    devnexus is an open-source cli that gives agents persistent shared memory across repos, sessions, and engineers. It maps out dependencies and relations at the function level, builds a code graph, and writes it into a shared Obsidian vault that every agent reads before writing code. Past decisions are also linked directly to the code they touched, so no one goes down the same dead end twice. Still building it out but I would love to hear any thoughts/feedback

    Apr 2026 · github.com

  14. 14

    Your AI agents team, terminals, notes: one infinite canvas

    Jul 2026

  15. 15

    Memory infrastructure for AI coding agents

    Feb 2026

  16. 16

    Multi-project IDE with persistent terminals and 9 dev tools

    Mar 2026

  17. 17

    Persistent, project-local memory for AI coding agent via MCP

    7d ago · opencntx.dev

  18. 18

    We built an open sourced coordination layer for AI agents working on the same repository. Detects work duplication and design conflicts early

    8d ago · twing.dev

  19. 19RM

    recursive-mode is an installable skill package for coding agents. It gives your agent a file-backed workflow for requirements, planning, implementation, testing, review, closeout, and memory, instead of leaving the whole process scattered in context. Long-running agent work has a common failure mode: requirements, decisions, and plans live in the conversation. Once the session ends or the context window overflows, the agent loses track of what was decided, what was implemented, and why. recursive-mode solves context rot by making repository documents the source of truth for every phase.…

    Apr 2026 · recursive-mode.dev

  20. 20UM

    I was frustrated that memory is usually tied to a specific tool. They’re useful inside one session but I have to re-explain the same things when I switch tools or sessions. Furthermore, most agents' memory systems just append to a markdown file and dump the whole thing into context. Eventually, it's full of irrelevant information that wastes tokens. So I built this local memory layer that unifies memory across agents. Instead of a flat file, it builds a structured knowledge graph of "memory notes" inspired by the paper "A-MEM: Agentic Memory for LLM Agents"…

    Apr 2026 · github.com

  21. 21HP

    Hey Everyone, I'm neither the founder or affiliated with these guys. But when they showed me the product it really clicked a switch. I have been building products with AI since sonnet 4.0, and one of my issue, like many, consistency. Hopsule turns architecture decisions into enforceable context that AI tools must follow. Creates trackable, tasks which can be feed into your AI tools to do compound engineering. If you're building with Claude Code, Cursor, or Copilot. You can use their CLI or MCP.

    Mar 2026 · hopsule.com

  22. 22DG

    I got frustrated watching Claude Code fail at using modern APIs (ask it about GPT-5 and it says it doesn't exist). Existing solutions like Context7 dump thousands of tokens of irrelevant docs into context. So I built DeepCon. How it works: - Crawled 10,000+ official docs using agentic browser automation and structured them hierarchically - Query decomposer breaks down requests, searches in parallel, then merges only relevant context - Returns just what's needed: 2.4x fewer tokens than Context7 Results on our benchmark: DeepCon achieved 90% accuracy vs Context7's 65% on real-world tasks with…

    Nov 2025 · deepcon.ai

  23. 23
    Oynix2

    memory engine that actually remembers. built for AI agents.

    11d ago · oynix.dev

  24. 24HP

    Hi HN! I'm building Hopsule. If you use AI coding tools like Cursor, Copilot, or Claude, you’ve probably seen this happen: The AI writes good code - but it ignores your architecture. It doesn’t know: - why you chose a specific pattern - which conventions your team agreed on - which decisions are already locked in So it falls back to generic patterns, outdated examples, or random GitHub training data. Over time this slowly breaks the consistency of the codebase. Most teams try to fix this with: - giant Markdown files - wiki pages - long prompts - Slack threads But those aren't…

    Mar 2026

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