Agents that build what your team decided, not vibe-coded guesses.

Memex is the docs and task management system built for agents and human teams to ship quality code at AI speed. Teams use Memex to build the project plans that humans and agents both follow. Every decision your team makes — in planning, in Slack, in PR comments, in chat threads — gets captured as a tracked record linked to the plan, then injected into the agent’s context the moment it claims that specific task. Each agent updates each task with the decisions it made. Professional engineering with agents, not vibe coding.

Sign up now

We’ll be in touch when Memex is ready for your team.

Deployment preference

Keeping humans and agents on the same plan breaks down — because the decisions live in tools agents can’t read.

The result: the agent fills the gap with a guess. Vibe coding by default.

  1. The team made the call in yesterday’s planning session. The agent picking up the task this morning never saw the thread it was decided in.
  2. The agent fills the gap with its own interpretation — picking the obvious-looking option that wasn’t what the team agreed.
  3. The PR ships the wrong thing on Tuesday morning. Your senior engineer spots it on Wednesday review. Three days of work lost to a call that was made in a tool the agent couldn’t read.

Memex is the docs and task management system built for agents and human teams to ship quality code at AI speed.

One Mission holds the whole plan — the objective, the architecture, the open decisions and the tasks. Every decision gets captured automatically, linked to the work it affects, and injected into the agent’s context the moment it claims that task. The whole team ships against the same plan.

Three steps to agents that stay on plan

Start in minutes. Works with the tools your team already uses.

  1. 01

    Install, index & connect

    One command connects Memex to your tools. Works with Cursor, Replit, Claude Code, ChatGPT and Slack. Point Memex at your repo. The indexer runs in your own infrastructure — self-hosted, fully private.

  2. 02

    Spec: create the plan

    Plan a Mission — the objective, the architectural vision, the open decisions. Decisions are made and captured directly in Memex, your IDE, Claude or GPT. Open decisions notify the right people and are resolved before agents start building. Tasks flow from confirmed decisions, each scoped with exactly what an agent needs.

  3. 03

    Execute and validate — ask Memex from your IDE

    Agents execute one task at a time against the plan, triggered from your IDE. Every decision is recorded. Work is validated against the plan automatically, flagging issues before QA. Conventions and docs update when the code changes. The next agent starts from the last decision made, automatically.

Everything you need to run coding agents at scale

Not a folder. Not a wiki. A complete system.

01

Index the codebase and plan against what’s real

Memex indexes your repo continuously, so every plan is grounded in the architecture and conventions that actually exist today — not the ones a wiki described last quarter.

02

Every task scoped to exactly what the agent needs

Tasks aren’t bullet lists. They’re fully scoped briefs, with the relevant decisions, conventions and constraints already attached. The agent picks up the task with the context it needs to ship.

03

Decisions made once. Automatically everywhere.

Decisions are captured at the moment they’re made — in planning, in chat, in PR review — and propagate to every task and agent that depends on them. No re-litigation. No drift.

04

Knowledge that does not go stale

Conventions, ADRs and runbooks update when the code does. Memex keeps the docs and the codebase in lockstep, so what an agent reads tomorrow reflects what shipped today.

Simple, transparent pricing.

Cloud

$50/user/month

Managed by us. Start building in minutes.

Sign up now
  • Unlimited Missions, decisions & tasks
  • Standard authoring & drift detection
  • Decision extraction from agent sessions
  • Full MCP server for all compatible agents
  • Dependency graph & impact analysis
  • Multi-agent coordination
  • Team collaboration & permissions
  • Cloud CDN & automatic backups
  • Email & chat support

Self-Hosted

Custom

Your infrastructure. Your data. Your LLM keys.

Contact Sales
  • Everything in Cloud, plus:
  • Deploy on your own infrastructure
  • Complete data sovereignty
  • Use your own LLM API keys
  • SSO & enterprise authentication
  • Priority support & onboarding
Requires Docker + PostgreSQL 15+

We built Memex because we lived the problem.

Mindset AI is the agentic platform powering in-app AI agents at a growing list of B2B SaaS companies. Every engineer on our team works with coding agents daily. Our product people design in conversation with AI. Our support team uses AI to triage and respond. We aren't just building AI agents — we're running an AI-native company.

The bottleneck shifted

When we started, we assumed the hardest part of AI-assisted engineering would be code quality. It wasn't. Modern coding agents produce good code when they know what they're trying to build.

The hard part turned out to be context. Two engineers, each with their own agent, arriving at contradictory decisions. An agent loading a wiki that was last updated two quarters ago. A re-prioritisation that silently invalidates half the decisions that shaped the previous plan.

We run Mindset on a set of mental models that take bottlenecks seriously. One of them is the Theorem of Constraints: any interconnected process operates at the speed of its slowest part. We're allergic to bottlenecks in our own organisation, and we look for them constantly.

When we applied that lens to AI-assisted development, the bottleneck was unmistakable: it wasn't writing code, it was capturing, propagating, and maintaining decisions across humans and agents.

Memex AI is the system we built to remove that bottleneck. It started as internal infrastructure. We use it every day. It's now the decision layer behind everything Mindset builds — and Memex itself runs on the Mindset agentic platform, so the product you're looking at is a working example of what both can do together.

Sign up now

Deployment preference

Free to start. Self-hosted. No credit card required.

Common questions

How is this different from just maintaining a good CLAUDE.md or cursor rules file?

CLAUDE.md and cursor rules are static — they reflect what was true when someone last edited them. Memex updates automatically as decisions are made and work progresses, so every agent reads the current state, not a snapshot from three months ago.

Does this mean I have to change how my team works?

No. Memex connects to the tools your team already uses — Slack, your IDE, your repo. Decisions and context get captured automatically from where they happen. You don’t have to write anything new.

Our codebase is private. Where does the indexing happen?

The indexer runs in your own infrastructure. Nothing leaves your environment. Memex is self-hosted and fully private.

Does this work with Cursor, Claude Code, ChatGPT?

Yes. Memex connects to Cursor, Replit, Claude Code, ChatGPT and Slack. One command to set up.

What if decisions conflict across Missions or teams?

Memex checks dependencies across Missions before any agent claims a task — so two agents can’t pick up conflicting work. When a decision changes, Memex automatically marks everything downstream that needs rechecking.

We’re already using Linear / Jira / Notion. Does this replace them?

Memex integrates with Linear, Jira, and Notion — it sits underneath them as the decision and context layer they were missing. It doesn’t replace them.