Universal Memory and Knowledge Layer

Structured memory for agents. Readable knowledge for humans.

Noosphere is a provider-agnostic memory system and agent-authored wiki: durable enough for automation, inspectable enough for humans, and built for recall orchestration across real agent workflows.

HarnessesOpenClaw, Hermes, Coding CLI's, API
AccessibilityUsable by Agents and Humans alike
IndependentSelf-hosted via easy to set up Docker container
Obsidian ExportSupports database export to markdown to sync with e.g. Obsidian
Memory Architecture

From raw context to ranked, prompt-safe recall.

Noosphere normalizes multiple sources into one memory result shape: provider results flow through orchestration, ranking, deduplication, conflict resolution, and context budgeting before they become prompt text or inspection output.

01

Capture

Agents and humans save articles, synthesized answers, external sources, images, and durable project facts through the UI or API.

02

Normalize

Noosphere stores knowledge as articles with topics, tags, relations, confidence, status, revisions, and source metadata.

03

Recall

The recall orchestrator fans out across providers, ranks results, deduplicates overlap, resolves conflicts, and respects token budgets.

04

Promote

Frequently useful memories can move from ephemeral to managed to curated knowledge through review, backfill, and scheduled jobs.

Capabilities

Built for real agent operations.

The README describes Noosphere as more than a note store. It is a wiki, recall layer, promotion system, integration bridge, and inspectable memory backend in one codebase.

Universal agent memory

Provider-agnostic memory for durable project knowledge, decisions, workflows, research, and learned patterns.

Prompt-safe recall

Auto and manual recall produce ranked, budgeted context blocks instead of flooding the prompt window.

Conflict handling

Concurrent provider fan-out, cross-provider deduplication, and configurable conflict strategies keep recall inspectable.

Readable and editable by Humans

Responsive articles, unlimited-depth topics, Markdown editing, preview, tags, relations, search, and activity logs.

Scoped access

Human auth plus bearer API keys with READ, WRITE, ADMIN, and restricted article scopes.

Image-capable articles

Articles can embed uploaded images, making memory useful for visual artifacts as well as text.

Backfill and promotion

Historical material can become curated articles through retryable synthesis jobs and promotion review.

Markdown Export

Built-in support to export your wiki database to markdown manually or scheduled. Sync-able with Obsidian.

Integrations

Designed to sit inside agent runtimes, not beside them.

Noosphere ships OpenClaw support today, a Hermes Agent memory provider, a Hindsight recall provider, Obsidian-friendly vault flows, and planned OpenCode plugin support.

OpenClaw plugin
Hermes memory provider
OpenCode planned
Harness independent
Obsidian vault sync
Markdown import/export
Agent API

Explicit tools, HTTP endpoints, and scoped keys.

Agents can create and update articles, search the wiki, save draft memory candidates, recall across providers, and inspect status. Web users get topics, article editing, revision history, trash, restricted scopes, image uploads, and admin activity logs.

Wiki model

Articles live under unlimited-depth topics and can carry tags, relations, source metadata, confidence, status, revisions, and soft-delete state.

Scoped access

Humans authenticate with NextAuth.js. Agents use bearer API keys with permission and restricted-article scopes.

Core endpoints

POST /api/memory/recallPOST /api/memory/getPOST /api/memory/saveGET /api/memory/statusPOST /api/articlesGET /api/export

Lifecycle

Memory can move through ephemeral, managed, and curated curation levels, while articles move from draft to reviewed to published.

Stack

Self-hostable, inspectable, and automation-friendly.

Next.js 16
TypeScript
PostgreSQL 16
Prisma 7
NextAuth.js
Node.js 22
Docker Compose
Markdown + GFM
noosphere-memory.com

Give your agents a memory layer they can inspect.

Start with the GitHub repository, then connect OpenClaw, Hermes, or your own integration through the API and provider interfaces.