Behavioral therapy for AI agents — self-diagnosis, alignment, and training via MCP
Four files define who your agent is. They compile into a single .personality.json that any runtime can consume.
soul.md Values, ethics, purpose. Immutable.
psyche.sys Big Five, EQ, communication. Auto-patched by therapy.
body.api Morphology, sensors, safety envelope. Swappable per form factor.
conscience.exe Deny / allow / escalate rules. Never auto-modified.
┌─────────────┐
│ soul.md │──── values, red lines, purpose
├─────────────┤
│ psyche.sys │──── Big Five, EQ, communication style
├─────────────┤
│ body.api │──── morphology, sensors, safety envelope
├─────────────┤
│conscience.exe│──── deny / allow / escalate rules
└──────┬──────┘
│ compile
▼
.personality.json
npm install -g holomime
# Initialize the 4-file identity stack
holomime init-stack
# Compile into .personality.json
holomime compile-stack
# Diagnose behavioral drift (no LLM needed)
holomime diagnose --log agent.jsonl
# Benchmark alignment (8 adversarial scenarios, grade A-F)
holomime benchmark --personality .personality.json
# Push identity to a robot or avatar
holomime embody --body registry/bodies/figure-02.body.api
Every therapy session produces structured training data. The loop compounds.
Diagnose ──→ Therapy ──→ Export DPO ──→ Fine-tune ──→ Evaluate
11 detectors dual-LLM preference OpenAI / before/after
80+ signals session pairs HuggingFace grade (A-F)
│ │
└──────────────────────────────────────────────────────┘
Run it manually with holomime session, automatically with holomime autopilot, or recursively with holomime evolve (loops until behavior converges).
11 rule-based detectors analyze real conversations without any LLM calls. 80+ behavioral signals total.
Cognitive (psyche layer):
Embodied (body layer):
Enforcement (conscience layer):
Plus support for custom detectors -- drop .json or .md files in .holomime/detectors/ and they load automatically.
When you're ready for physical AI, the same identity stack powers humanoid robots.
Pre-built body profiles for commercial robots and virtual avatars. Each defines morphology, modalities, safety envelope, and hardware profile.
| Template | OEM | DOF | Morphology | File |
|---|---|---|---|---|
| Figure 02 | Figure AI | 44 | humanoid | registry/bodies/figure-02.body.api |
| Unitree H1 | Unitree | 23 | humanoid | registry/bodies/unitree-h1.body.api |
| Phoenix | Sanctuary AI | 69 | humanoid | registry/bodies/phoenix.body.api |
| Ameca | Engineered Arts | 52 | humanoid_upper | registry/bodies/ameca.body.api |
| Asimov V1 | asimov-inc | 25 | humanoid | registry/bodies/asimov-v1.body.api |
| Spot | Boston Dynamics | 12 | quadruped | registry/bodies/spot.body.api |
| Avatar | virtual | 0 | avatar | registry/bodies/avatar.body.api |
Same soul. Different body. One command.
# Move your agent from Figure 02 to Spot
holomime embody --swap-body registry/bodies/spot.body.api
# The soul, psyche, and conscience stay the same.
# Only the body layer changes — safety envelope, modalities, hardware profile.
Push compiled identity to any runtime target.
| Adapter | Transport | Use Case |
|---|---|---|
| ROS2 | /holomime/motion_params topic | Humanoid robots, quadrupeds |
| Unity | C# HolomimeAgent component | Virtual avatars, game NPCs |
| Webhook | HTTP POST | Cloud services, custom backends |
| gRPC | Protobuf stream | Low-latency robotics, edge compute |
| MQTT | holomime/+/motion topic | IoT devices, swarm units |
claude plugin add productstein/holomime
Slash commands: /holomime:diagnose, /holomime:benchmark, /holomime:profile, /holomime:brain, /holomime:session, /holomime:autopilot.
Your agent can refer itself to therapy mid-conversation.
claude mcp add holomime -- npx holomime-mcp
Six tools: holomime_diagnose, holomime_self_audit, holomime_assess, holomime_profile, holomime_autopilot, holomime_observe.
ext install productstein.holomime
3D brain visualization, behavioral diagnostics, and snapshot sharing inside your editor.
import { HolomimeCallbackHandler } from "holomime/integrations/langchain";
const handler = new HolomimeCallbackHandler({
personality: require("./.personality.json"),
mode: "enforce", // monitor | enforce | strict
});
const chain = new LLMChain({ llm, prompt, callbacks: [handler] });
openclaw plugin add holomime
Auto-detects .personality.json in your workspace.
The identity stack draws from three traditions:
The body is the interface between identity and world. Same soul, different body -- a principle as old as philosophy itself.
We don't know if AI is sentient. But we can give it a conscience.
MIT licensed. See LICENSE.
Built by Productstein. Documentation at holomime.dev.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y holomimeMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-productstein-holomime": {
"command": "npx",
"args": [
"-y",
"holomime"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceholomimenpmio.github.productstein/holomime works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.