maenifold transforms isolated AI sessions into a persistent knowledge graph with WikiLinks, vectors, and emergent structure. Test-time reasoning that compounds.
Your AI is ephemeral. Your knowledge shouldn’t be.
maenifold enhances AI agents with persistent graphs of thought that compound over time. Every tool creates [[WikiLink]] connections that survive conversations. Every session builds on the last. Knowledge compounds instead of resets. It transforms ephemeral AI sessions into continuous collective intelligence.

Our demo shows this at scale: 25 AI agents across 68 minutes discovered a critical production bug not through programmed coordination, but through emergent understanding. No orchestration code was written, yet agents perfectly orchestrated themselves across 4 waves, building on each other’s discoveries through a shared knowledge graph.
The critical move operation bug emerged from the intersection of multiple test patterns seen across different agent sessions - something no single agent could have found alone. This is maenifold’s core: making every AI session additive rather than isolated.
[[WikiLinks]] in memory files85% test success rate. Real production bug found. Zero orchestration code written.
That’s what maenifold does: It provides the substrate (WikiLinks, memory, graph) and steps back. Intelligence fills the space.
maenifold ships with 54 pre-configured cognitive frameworks that agents can adopt dynamically:
From reasoning patterns to development processes:
Each with personality, principles, and transition triggers:
Thinking modes for different cognitive approaches:
Language-influenced cognitive styles based on linguistic relativity:
These aren’t just templates - they’re cognitive substrates that combine with the knowledge graph to create emergent reasoning capabilities. An agent can start with strategic thinking, switch to red team perspective when finding vulnerabilities, then adopt the writer role to document findings - all while building on the persistent knowledge graph.
graph TD
subgraph OVERALL["maenifold"]
subgraph AGENT["AI Agent"]
LLM[🧠 LLM Agent]
end
subgraph PERSP["Perspectives"]
A[🎭 Adopt]
end
subgraph THINK["Thinking"]
ST[🌊 SequentialThinking]
WF[📋 Workflow]
end
subgraph MEMORY["Memory System"]
MEM[🗄️ Memory]
GRPH[🕸️ Graph]
end
end
A --> LLM
LLM --> WF
LLM --> ST
WF -.-> ST
ST --> MEM
WF --> MEM
MEM --> GRPH
GRPH --> LLM
MEM --> LLM
Where test-time computation happens:
memory://) - Where Data is StoredAutomatic graph construction from [[WikiLinks]] with:
memory:// protocolnpm install -g @ma-collective/maenifold
Claude Code, Continue, Cline - Add to MCP config:
{
"mcpServers": {
"maenifold": {
"command": "maenifold",
"args": ["--mcp"],
"env": {"MAENIFOLD_ROOT": "~/maenifold"}
}
}
}
Codex - Add to ~/.codex/config.toml:
[mcp_servers.maenifold]
type = "stdio"
command = "maenifold"
args = ["--mcp"]
startup_timeout_sec = 120
tool_timeout_sec = 600
env = { MAENIFOLD_ROOT = "~/maenifold" }
Try it: "Write a memory about our architecture decisions"
Use maenifold directly in scripts, pipelines, or with non-MCP clients:
# Write a memory with WikiLinks
maenifold --tool WriteMemory --payload '{
"title": "Architecture Decisions",
"content": "Our [[microservices]] use [[event-sourcing]] for [[audit-trails]]"
}'
# Continue a sequential thinking session
maenifold --tool SequentialThinking --payload '{
"sessionId": "session-1234567890",
"response": "After analyzing the architecture...",
"nextThoughtNeeded": true
}'
# Search memories with hybrid mode
maenifold --tool SearchMemories --payload '{
"query": "authentication patterns",
"mode": "Hybrid",
"pageSize": 10
}'
MCP and CLI have full feature parity. Start a session via MCP and continue it via CLI, or vice versa. The system supports concurrent agents using the same memory location - perfect for multi-agent pipelines or parallel workflows.
.NET 9.0 · SQLite · ONNX · MCP · MIT License
Your AI’s extended mind