Skip to content
MULTINEX
MemQ

Multinex MemQ

Keep the context.
Pick up where you left off.

Save decisions, project knowledge, and handoffs in one memory layer. Bring the relevant context into your next AI session—even when you switch tools.

Start MemQ freeSee how to connect

No card required. Connect through MCP with OAuth or an API key.

Gold and teal memory core connected to surrounding nodes and layered memory planesMemQ · persistent context
Keep the decision. Carry the reason.

Saved context, ready for the next authorized session.

What stays with you

Less re-explaining. More continuity.

Decisions

Keep the choice and the reason behind it, so the next session has more than a summary.

Project context

Save definitions, constraints, and working notes that your agents need to do the job.

Handoffs

Carry progress, open questions, and next steps into the next tool or teammate’s workflow.

The MemQ journey

Your tools change. The context comes with you.

Connected clients save and retrieve memory within their authorized scope. Start a new session with the context you chose to keep.

Your tools

CodexClaude CodeCursorMCP clients
MCP
OAuth or API key
MemQ

MemQ

Decisions · knowledge · handoffs

Private and team access scopes
Retrieve relevant
saved context

Pick up the work

  • Next session
  • Another connected tool
  • Authorized teammate
Access follows the authenticated namespace. Missing context still needs to be supplied or saved.

Shared context in practice

Every handoff adds a useful piece.

Adapted from the original context puzzle: decisions, fixes, and runbooks stay useful beyond the tool that created them.

DecisionWhy the queue changed
FixHow the test was repaired
RunbookWhat to check before release
HandoffWhere the next teammate starts
MemQ

Example · coding to review

A decision saved in one tool.
Recalled in the next.

Coding agent Review agent
“Preserve the selected plan when linking to signup.”

The next agent retrieves the saved handoff before changing the signup links.

Illustrative workflow. Both clients need access to the relevant memory; sharing is not automatic.Explore team memory

Connect your tools

One memory layer. Your way of working.

Use a supported plugin or an MCP-compatible client. Follow the setup guide for your tool, then save and recall a first piece of context.

Find your integrationRead the quickstart

Already have an account? Connect with your existing credentials.

  1. Create your account

    Start with MemQ Free, or choose a plan for your usage and team.

  2. Connect your client

    Use the documented plugin or MCP setup for the tools you work in.

  3. Save. Recall. Continue.

    Save a useful decision and recall it in a new session to check your setup.

AIEGES Shield + MemQ

Protect the write.
Keep the useful memory.

Shield sits before MemQ on a configured MCP path. Local inspection and hosted memory have separate jobs, with separate controls.

Configured memory write path: client to local AIEGES Shield, across an authenticated MCP connection, then through MemQ server checks into scoped memory. A receipt branch stays on the device. View full illustration
Reference architecture for a configured, enforcing route. Coverage and redaction or blocking behavior depend on the client, deployment, and policy; connecting directly to MemQ does not enable Shield.

  1. Your client

    An agent prepares a memory write. Route the supported MCP connection through Shield to inspect it.

  2. AIEGES Shield

    Local checks apply the configured policy. Sensitive content can be redacted or the request blocked; receipts stay on the device.

  3. Authenticated MCP

    An allowed request continues to MemQ using your configured credentials. Shield does not replace MemQ authentication.

  4. MemQ

    MemQ applies its own access and write safeguards, then stores accepted context within the authorized namespace.

Integration boundary. Shield is a separate protection layer, not built into every MemQ connection. The native policy-bundle and receipt handshake between the products is planned.

Inspect Shield + MemQ

Look closer

The details, when you need them.

Inspect how MemQ works without losing your place in the product story.

Published benchmarks

Results, methodology, and limitations.

Architecture

Storage, retrieval, and integration.

Privacy + access

Namespaces and sharing boundaries.

Before you connect

A few useful answers.

Is my memory private?

MemQ uses authenticated namespaces to separate private memory from team and shared knowledge. Access depends on your account and configured scope; connecting another tool does not make your private memory public.

Can my team share context?

Team plans provide a shared team namespace. Connect tools with the appropriate team credentials so teammates and agents can work from the same saved context. Personal memory remains separate.

Does MemQ remember every conversation automatically?

MemQ recalls context that has been saved to it. What gets saved and when it is recalled depends on your connected client, skills, and workflow. It does not automatically import every chat or replace your source systems.

Do I need Crosswalk to use MemQ?

No. MemQ works independently today. Crosswalk is a separate product preview for reviewing CRM and lakehouse mappings. Its planned MemQ integration does not change how you get started with MemQ.

Read the full MemQ FAQ

Start with one useful memory

Give your next session a head start.

Start free. Compare plans when you need more capacity or shared team memory.

Start MemQ freeCompare plans