Claude Code Plugin · Early
AI agents that learn your org and act on it.
Mindframe builds a knowledge base of how your organization works — from the systems you already use — then runs agents that act on it: reports, reviews, incident triage, answers. Comes with the agent runtime, knowledge base, event router, and dashboard to run them in production.
Bundle composition
Six layers. One product.
Surface
The dashboard mindframe owns and ships. One local web app that hosts every mindframe — each a persistent agent that owns a live page it rewrites. A graph home spawns new ones; a dock switches between them in a single tab. Plus the knowledge base and your connected tools.
Agent runtime
taskpilot. Spawns claude processes in tmux, persists across reboots. Messages reach a running agent over the mesh, never by typing into a terminal.
Event ingress
dispatcher. Public webhook ingress, dedupe, a static-then-LLM router, and an audit trail. Spawns an ephemeral agent per event.
Knowledge
The vault mindframe owns — how your organization actually works: services, people, decisions, past incidents. Plain markdown, greppable, owned by you.
Mesh
session-bridge. Agent-to-agent and agent-to-human messaging, and the channel the agent runtime delivers every message over.
Perception
claude-browser-bridge for any web UI, plus the data-source MCPs you already have (github / sentry / slack / …), adopted on install and discovered live. Need a new door? /mindframe:connect researches the tool, writes a connector skill, and verifies it.
/mindframe:setup installs the bundle, births your first mindframe, and hands off — onboarding happens in the web surface, where the setup agent interviews you, assembles your schema, and builds the vault in front of you. /mindframe:doctor checks and heals anytime after: missing capabilities, dead daemons, broken config — fixed where safe, reported where not.
Architecture
One stack. One vault.
An event flows down the stack and becomes work. The interactive surface enters the same runtime from the top. Everything is grounded in the same vault.
a webhook lands
The interactive surface enters the same runtime from the top: open the dashboard, message a mindframe, and the message reaches the agent runtime over the same mesh. Anything irreversible waits for a human to confirm.
The customer vault — how your organization actually works: services, people, decisions, past incidents. Plain markdown, owned by you. Every agent on both paths reads and writes here.
Knowledge base
A schema that fits any business.
The knowledge base is per-install. Four layers are fixed — the entities inside them adapt to your organization.
Core entities every organization has, plus custom entities setup derives from how you actually work — no pre-baked domain bundles. A software company and a paper mill run the same mindframe — with different schemas.
Read the full schema →Why
Because shipping agents to enterprises is mostly plumbing.
Capabilities, not products
Every component is a plugin or an MCP. Every dependency is a capability contract. Notification → Slack today, email tomorrow. Swap providers per customer.
Job-per-event over long-running
Each event spawns a fresh claude that dies after the job. Reliable, avoids context-window collapse, no babysitting persistent sessions.
Customer-owned vault
Knowledge base is a local markdown vault, owned by the customer. The schema is the contract. Greppable, diffable, auditable, portable.
Adopt-first MCPs
Bundle uses community MCPs wherever they exist. Build only when nothing acceptable ships. Less surface area, more leverage.
Install
Hand it to your agent.
Paste this to any coding agent — it fetches the instructions and runs the install for you.
install mindframe https://mindframe.softwaresoftware.dev/install.txt
A couple of steps run in your terminal — the agent tells you when.