Agents lose context
Restarts break memory. Preferences, decisions, and prior work disappear unless memory is made portable.
Built on AMCP
Nunchi AI builds connected products for thinking, building, and operating with long-term agent memory. The platform starts with AMCP, the open protocol for agent memory continuity, and extends into production tools.
Portable memory continuity across sessions, runtimes, and clients.
Managed server for long-term agent memory and recall workflows.
Nunchi AI products stand alone, but they fit better together than apart.
Why this exists
Restarts break memory. Preferences, decisions, and prior work disappear unless memory is made portable.
AMCP gives agent memory a transportable contract instead of leaving it trapped inside one product.
Nunchi AI turns the standard into a usable system with docs, hosted runtime, and connected workflows.
Latest proof
The public story is simple: AMCP is the memory layer, Nexus is the implementation, and Channels show where persistent context becomes immediately practical.
Writing
A narrow verified proof that Claude Code Channels handles live reachability while Nexus preserves memory across restarts.
Read postA practical explanation of why larger context windows do not automatically become reliable memory.
Read postPositioning AMCP as the missing memory layer beside tools and agent collaboration.
Read postProduct stack
Each product has a narrow job. Together they describe the operating surface of Nunchi AI.
Managed memory infrastructure for agents, built around AMCP and long-term recall workflows.
Open NexusCapture-first knowledge workflows that turn raw notes and sources into reusable memory.
Open NorfolkDependency and API change awareness before outdated assumptions hit production.
Open VesselDeveloper operations automation packaged into a direct and narrow toolchain.
Open StackpilotResearch and publishing workflows aimed at builders, products, and market signals.
Open Indie PulseOperational software for ordering flows and real-world service interfaces.
Open QodrConnected knowledge workflows where notes, structure, and agent memory meet.
Open SynapsisHow it fits
AMCP defines how memory survives beyond one client or one session.
Nexus exposes the memory system as something teams can actually run and adopt.
The surrounding products turn that memory layer into practical workflows across coding, media, and operations.