Getting Started
Install claude-smart, verify it's running, and see your first learned rule injected into Claude.
Prerequisites
- Claude Code installed and signed in
- Node.js ≥ 18
- Python ≥ 3.12
uvon your PATH — the plugin's hooks shell out touv run
claude CLI and uses an in-process ONNX embedder for semantic search.Install
Add the marketplace and install the plugin
/plugin marketplace add EmendAI/claude-smart/plugin install claude-smart@emendaiBoth commands run the equivalent marketplace flow on your behalf.
Restart Claude Code
Close and reopen Claude Code so the plugin's hooks are registered. The first session will take a few extra seconds — the Setup hook syncs the Python environment, downloads the ONNX embedder (~80 MB), and prebuilds the dashboard.
Verify the backend is up
On SessionStart, claude-smart spawns a local Emend backend on localhost:8081 and a dashboard on localhost:3001. Check the backend:
curl -H "User-Agent: my-agent-emend" http://localhost:8081/health# {"status":"healthy"}Then open http://localhost:3001 in a browser to see the dashboard.
Check what Claude is being told
Inside Claude Code, run:
/showOn a brand-new install, this prints empty sections. As you work, profiles and playbook rules populate here — /show always reflects the exact markdown that SessionStart injects into Claude's system prompt.
Teach it your first rule
Have a short conversation that contains a correction, for example:
You: run the testsClaude: runs npm testYou: stop — in this repo always pass --run, watch mode hangs CIThen force extraction instead of waiting for the end of the session:
/learnWait 20–30 seconds, then run /show again. The new rule appears in the Project Playbook section. It will be reinjected on every future session in this project.
Update or Uninstall
npx claude-smart update# Or inside Claude Code:/plugin update claude-smart@emendaiNext Steps
- How It Works — Dig into the hook lifecycle and what triggers rule extraction.
- Slash Commands — Full reference for the commands the plugin installs.
- Configuration — Environment variables, data layout, and troubleshooting.