Documentation
**Public Docs**: https://docs.claude-mem.ai (Mintlify)
**Source**: `docs/public/` - MDX files, edit `docs.json` for navigation
**Deploy**: Auto-deploys from GitHub on push to main
## Important
No need to edit the changelog
From project root - regenerate components.json
cd ..
python scripts/generate_components_json.py
# This creates/updates docs/components.json with all components
```
### Deployment
- Site is automatically deployed to GitHub Pages when changes are pushed to `docs/` directory
- Deployed
crates.io v53).
The previous WrenAI services (`wren-ui/`, `wren-ai-service/`, `wren-launcher/`, `docker/`, `deployment/`) were moved to the `legacy/v1` branch (tag `v1-final`) as of the wren-engine import
which client they're targeting (Claude Desktop or Claude Code → stdio path, claude.ai → HTTP + deploy + connector), then follow that path's checklist. Both end with the same `send_message → wait
Sentry triage × Claude Managed Agents
Scheduled deployment: cron → Managed Agents session with `sentry-cli` and a vault env-var credential → triage report in `/mnt/session/outputs/`.
## When the user asks
agent.(AgentDoctorInfo); ok {
bin = info.CLIBinaryName()
}
```
### 3. Configuration Over Code
- Features that may vary per deployment should be configurable in `config.toml`
- Use `map[string]any` options for agent/platform factories to stay
Declarative Automation Bundles Project
This project uses Declarative Automation Bundles for deployment.
## Prerequisites
Install the Databricks CLI 0.292.0 or newer and verify with `databricks -v`.
## For AI Agents
Read
role:** *Not set at company level.* Under the EU AI Act, role (provider,
deployer, importer, distributor, authorized representative, product
manufacturer) is assessed **per AI system** — see `## AI system inventory`
below
assembles `bin/containerization-x86_64- .tar.gz` (cctl + cloud-hypervisor + virtiofsd + initfs.ext4 + kernel) for x86_64 Linux deployment, cross-compiled inside the aarch64 dev container via the Static Linux SDK (Swift) and `cargo zigbuild
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.