\n\n# memento\n\n**Bi-directional memory sync for AI coding agents**\n\nKeep Claude Code, Codex CLI, Gemini CLI, Antigravity, Cursor, and Windsurf memory files aligned without choosing a single permanent source of truth.\n\n[](https://www.npmjs.com/package/@dantelabs/memento)\n[](https://github.com/dandacompany/memento/actions/workflows/ci.yml)\n[](LICENSE)\n\n[Quick Setup](#quick-setup) | [Provider Matrix](#provider-matrix) | [CLI](#cli) | [Configuration](#configuration) | [Safety](#safety-model)\n\n[Korean](README.ko.md)\n\n
\n\n---\n\n## What is memento?\n\nmemento is a Node.js CLI that synchronizes long-lived instruction and memory files used by AI coding agents.\n\nDifferent agents store context in different places:\n\n- Claude Code: `CLAUDE.md`, `~/.claude/CLAUDE.md`\n- Codex CLI: `AGENTS.md`, `~/.codex/AGENTS.md`\n- Gemini CLI: `GEMINI.md`, `~/.gemini/GEMINI.md`\n- Cursor: `.cursor/rules/*.mdc`\n- Windsurf: `.windsurf/rules/*.md`\n- Antigravity: `.agent/skills/**`, `memory-bank/**`, selected global memory paths\n\nWhen you switch tools or use several agents in the same repository, those files can drift. memento reads each provider's native file format, normalizes it into a shared internal document model, resolves conflicts, writes changes back to the original provider files, and creates backups before modifying anything.\n\nThe design goal is practical local synchronization:\n\n```text\nCLAUDE.md \\\nAGENTS.md > memento sync > same project memory everywhere\nGEMINI.md /\n\n.cursor/rules/typescript.mdc \\\n.windsurf/rules/typescript.md > same rule identity\n```\n\nmemento does not run a server, does not upload memory files, and does not replace git. It is a local CLI for keeping agent context consistent on your machine and in your repository.\n\n### What's new in 0.3.0\n\nVersion `0.3.0` includes the broader assistant context portability added across the 0.2 and 0.3 line:\n\n- Skills: synchronize provider skill bundles such as Claude Code `.claude/skills/*` and Codex `.agents/skills/*`.\n- MCP servers: synchronize project and local MCP server definitions across supported providers.\n- Resource-aware commands: `status`, `sync`, `diff`, and `watch` accept `--resources`, `--scope`, `--no-skills`, and `--no-mcp`.\n- Cross-project import: `memento import ` brings memory from another project into the current project.\n- Safer automation: release CI skips already published npm versions, and CLI help/version/install output includes the memento ANSI banner.\n\n---\n\n## Quick Setup\n\n### Prerequisites\n\n- Node.js 18 or newer\n- npm\n- At least one supported agent memory file in the project, or an explicit provider list passed to `memento init`\n\n### 1. Install the CLI\n\n```bash\nnpm i -g @dantelabs/memento\n```\n\nVerify the install:\n\n```bash\nmemento --version\nmemento --help\n```\n\n### 2. Initialize a project\n\nRun this from the repository root:\n\n```bash\nmemento init\n```\n\n`init` creates `.memento/config.toml` and adds these runtime files to `.gitignore`:\n\n```gitignore\n.memento/cache.json\n.memento/backup/\n```\n\nIf memento cannot auto-detect a provider, force the providers you want:\n\n```bash\nmemento init --providers claude-code,codex,gemini-cli,cursor,windsurf\n```\n\nValid provider ids are:\n\n```text\nclaude-code, codex, gemini-cli, antigravity, cursor, windsurf\n```\n\n### 3. Inspect status\n\n```bash\nmemento status\n```\n\nTypical output shows which providers are active and how memory files are grouped:\n\n```text\nmemento status\n\nProviders\nok claude-code (active)\nok codex (active)\nok gemini-cli (active)\n\nproject\nok synced agents-md:main claude-code, codex, gemini-cli\n```\n\n### 4. Preview or run a sync\n\nPreview first:\n\n```bash\nmemento sync --dry-run\n```\n\nThen write changes:\n\n```bash\nmemento sync\n```\n\nSync skills and MCP definitions too:\n\n```bash\nmemento sync --resources memory,skills,mcp --scope project\n```\n\nFor an interactive conflict prompt:\n\n```bash\nmemento sync --strategy prompt\n```\n\nFor CI or scripts that should fail on unresolved conflicts:\n\n```bash\nmemento sync --strategy fail\n```\n\n### 5. Keep files synchronized while you work\n\n```bash\nmemento watch\n```\n\n`watch` uses last-write-wins conflict handling and is designed for local development sessions where provider memory files may change as you switch tools.\n\n---\n\n## Core Concepts\n\n### Memory tiers\n\nmemento treats memory files as one of three tiers:\n\n| Tier | Meaning | Typical location | Git behavior |\n| --- | --- | --- | --- |\n| `project` | Shared repository memory | `CLAUDE.md`, `AGENTS.md`, `GEMINI.md`, `.cursor/rules/*.mdc` | Usually committed |\n| `project-local` | Local project memory for one machine | `CLAUDE.local.md`, `AGENTS.local.md`, `*.local.mdc` | Usually ignored |\n| `global` | User-level memory outside a project | `~/.claude/CLAUDE.md`, `~/.codex/AGENTS.md` | Not committed |\n\nBy default, project commands sync `project` and `project-local` tiers. Use `--include-global` to include global files, or use `memento global ...` to operate only on global memory.\n\n### Memory identities\n\nmemento does not simply copy every file to every other file. It groups files by semantic identity.\n\n| File | Identity |\n| --- | --- |\n| `CLAUDE.md` | `agents-md:main` |\n| `AGENTS.md` | `agents-md:main` |\n| `GEMINI.md` | `agents-md:main` |\n| `.cursor/rules/typescript.mdc` | `rule:typescript` |\n| `.windsurf/rules/typescript.md` | `rule:typescript` |\n| `.agent/skills/git-flow/SKILL.md` | `skill:git-flow` |\n| `memory-bank/core/state.md` | `memory-bank:core/state` |\n\nFiles with the same tier and identity are compared and synchronized as a group, for example `project/agents-md:main`.\n\n### No permanent source of truth\n\nmemento is bi-directional. The winning version for a group is chosen during each sync:\n\n- if all files are identical, nothing is written\n- if one file changed since the last sync, that change is propagated\n- if multiple files changed differently, the configured conflict strategy decides what happens\n\nThis lets you edit memory in whichever agent you are using at the moment.\n\n### Resource sync\n\nIn addition to markdown memory files, memento can synchronize structured assistant resources.\n\n| Resource | What it represents | Examples |\n| --- | --- | --- |\n| `memory` | Long-lived instruction files and rules | `CLAUDE.md`, `AGENTS.md`, `GEMINI.md`, Cursor/Windsurf rules |\n| `skill` | Skill directories with a `SKILL.md` entry file and related files | `.claude/skills/review`, `.agents/skills/review` |\n| `mcp` | MCP server definitions in provider config files | `.mcp.json`, `.codex/config.toml`, `.codeium/mcp_config.json` |\n\nResource commands use scopes:\n\n| Scope | Meaning |\n| --- | --- |\n| `local` | Include the provider's local/default resource locations for the current machine |\n| `project` | Use project-level resource files inside the current repository |\n| `cross-cli` | Use shared or global resource locations where supported |\n\nDefault `sync`, `status`, `diff`, and `watch` resource selection is `memory,skill,mcp`. `memento import` is more conservative and imports `memory` only unless `--resources` is provided.\n\n---\n\n## Provider Matrix\n\n| Provider | Provider id | `project` | `project-local` | `global` |\n| --- | --- | --- | --- | --- |\n| Claude Code | `claude-code` | `CLAUDE.md`, `AGENTS.md` | `CLAUDE.local.md` | `~/.claude/CLAUDE.md` |\n| Codex CLI | `codex` | `AGENTS.md` | `AGENTS.local.md` | `~/.codex/AGENTS.md` |\n| Gemini CLI | `gemini-cli` | `GEMINI.md` | `GEMINI.local.md` | `~/.gemini/GEMINI.md` |\n| Antigravity | `antigravity` | `.agent/skills/**`, `memory-bank/**` | `memory-bank/**.local.md` | `~/.gemini/antigravity/skills/**`, `~/.gemini/GEMINI.md`, `~/.antigravity/` |\n| Cursor | `cursor` | `.cursor/rules/*.mdc`, legacy `.cursorrules` | `.cursor/rules/*.local.mdc` | `~/.cursor/rules/*.mdc` |\n| Windsurf | `windsurf` | `.windsurf/rules/*.md`, legacy `.windsurfrules` | `.windsurf/rules/*.local.md` | `~/.windsurf/rules/*.md` |\n\nGemini CLI and Antigravity can both reference `~/.gemini/GEMINI.md`; memento deduplicates that shared global path.\n\n### 0.2.0 resource coverage\n\n| Provider | Skills | MCP |\n| --- | --- | --- |\n| Claude Code | `.claude/skills/*`, `~/.claude/skills/*` | `.mcp.json` |\n| Codex CLI | `.agents/skills/*`, `~/.agents/skills/*`, read-only `/etc/codex/skills` | `.codex/config.toml`, `~/.codex/config.toml` |\n| Windsurf | `.windsurf/skills/*`, `.agents/skills/*` | `.codeium/mcp_config.json` |\n| Cursor | Memory/rules only in this release | Not enabled in this release |\n| Gemini CLI | Memory only in this release | Not enabled in this release |\n| Antigravity | Existing memory-bank and skill-like memory paths | Not enabled in this release |\n\nMCP values are copied as provider configuration text. Dry-run and diff output redact secret-like fields by default.\n\n---\n\n## Common Workflows\n\n### Start with Claude Code and Codex only\n\n```bash\nmemento init --providers claude-code,codex\nmemento status\nmemento sync --strategy prompt\n```\n\n### Sync only one provider\n\n```bash\nmemento sync --provider codex\n```\n\nThis is useful when you want to write the resolved memory back to one provider after changing another provider's file.\n\n### Sync only one tier\n\n```bash\nmemento sync --tier project\nmemento sync --tier project-local\n```\n\n### Include global memory from a project sync\n\n```bash\nmemento sync --include-global\n```\n\n### Sync skills and MCP servers\n\nPreview resource writes first:\n\n```bash\nmemento sync --resources memory,skills,mcp --scope project --dry-run\n```\n\nThen run the sync:\n\n```bash\nmemento sync --resources memory,skills,mcp --scope project\n```\n\nTo skip one resource type:\n\n```bash\nmemento sync --resources memory,skills --no-mcp\nmemento status --resources mcp --scope project\n```\n\n### Import memory from another project\n\nFrom the target project root:\n\n```bash\nmemento import ../old-project --dry-run\nmemento import ../old-project --to codex --strategy replace\n```\n\nImport skills explicitly:\n\n```bash\nmemento import ../old-project --resources memory,skills --scope project\n```\n\nImport MCP definitions only after reviewing the dry-run output:\n\n```bash\nmemento import ../old-project --resources mcp --scope project --dry-run\nmemento import ../old-project --resources mcp --scope project --strategy prompt\n```\n\n### Manage only global memory\n\n```bash\nmemento global init --providers claude-code,codex,gemini-cli\nmemento global status\nmemento global sync --strategy prompt\nmemento global watch\n```\n\nGlobal commands use `~/.memento/config.toml` and operate on global provider paths only.\n\n### Use memento in CI\n\nUse `--strategy fail` to make the command fail when provider memory files disagree:\n\n```bash\nmemento sync --strategy fail --dry-run\n```\n\nExit code `2` means unresolved conflicts were found.\n\n### Restore a previous version\n\n```bash\nmemento restore --list\nmemento restore --at 2026-04-30T07-37-00_342Z\n```\n\nRestore a single group:\n\n```bash\nmemento restore --at 2026-04-30T07-37-00_342Z --group project/agents-md:main\n```\n\n---\n\n## CLI\n\n### Global options\n\n| Option | Description |\n| --- | --- |\n| `-v, --version` | Print the installed memento version |\n| `--debug` | Print debug output and stack traces |\n| `--json` | Emit JSON lines where supported |\n| `--quiet` | Suppress non-error output |\n\n### Commands\n\n| Command | Description |\n| --- | --- |\n| `memento init` | Create `.memento/config.toml` for the current project |\n| `memento status` | Show provider detection, tiers, and sync state |\n| `memento sync` | Synchronize memory files across active providers |\n| `memento watch` | Watch memory files and synchronize changes continuously |\n| `memento diff` | Show differences between grouped memory documents |\n| `memento import` | Import assistant memory from another project into the current project |\n| `memento restore` | List, restore, or prune automatic backups |\n| `memento global` | Run `init`, `status`, `sync`, `watch`, `diff`, or `restore` against global memory |\n| `memento update` | Update the global memento CLI install |\n| `memento install-skill` | Install the bundled Claude Code skill manually |\n| `memento uninstall-skill` | Remove the installed Claude Code skill |\n\nRun `memento --help` for the exact options supported by your installed version.\n\n### `memento init`\n\n```bash\nmemento init [--force] [--providers ]\n```\n\n| Option | Description |\n| --- | --- |\n| `--force` | Overwrite an existing `.memento/config.toml` |\n| `--providers ` | Comma-separated provider ids to enable |\n\n`init` probes all supported providers, creates a config, and updates `.gitignore` for runtime cache and backup files.\n\n### `memento status`\n\n```bash\nmemento status [--tier ] [--resources ] [--scope ] [--include-global] [--json]\n```\n\n| Option | Description |\n| --- | --- |\n| `--tier ` | Filter to `project`, `project-local`, or `global` |\n| `--resources ` | Filter resource kinds: `memory`, `skills`, `mcp` |\n| `--scope ` | Resource scope: `local`, `project`, or `cross-cli` |\n| `--no-mcp` | Exclude MCP resources |\n| `--no-skills` | Exclude skill resources |\n| `--include-global` | Include global files in project status |\n| `--json` | Emit JSON output |\n\n### `memento sync`\n\n```bash\nmemento sync [--dry-run] [--strategy ] [--tier ] [--provider ] [--resources ] [--scope ] [--yes] [--include-global]\n```\n\n| Option | Description |\n| --- | --- |\n| `--dry-run` | Preview the sync without writing files |\n| `--strategy ` | Conflict strategy: `lww`, `prompt`, or `fail` |\n| `--tier ` | Filter to one memory tier |\n| `--provider ` | Filter to one provider id |\n| `--resources ` | Resource kinds to sync: `memory`, `skills`, `mcp` |\n| `--scope ` | Resource scope for skills and MCP |\n| `--no-mcp` | Exclude MCP resources |\n| `--no-skills` | Exclude skill resources |\n| `--allow-project-secrets` | Allow project MCP secret writes when policy permits it |\n| `--yes` | Accept non-interactive defaults; currently uses `lww` |\n| `--include-global` | Include global memory in a project sync |\n\n### `memento watch`\n\n```bash\nmemento watch [--debounce ] [--tier ] [--provider ] [--resources ] [--scope ] [--include-global]\n```\n\n`watch` monitors provider memory files and runs sync after changes settle.\n\n| Option | Description |\n| --- | --- |\n| `--debounce ` | Debounce interval in milliseconds; default is `500` |\n| `--tier ` | Watch only one tier |\n| `--provider ` | Watch only one provider |\n| `--resources ` | Resource kinds to watch and sync |\n| `--scope ` | Resource scope for skills and MCP |\n| `--no-mcp` | Exclude MCP resources |\n| `--no-skills` | Exclude skill resources |\n| `--include-global` | Include global memory in project watch mode |\n\n### `memento diff`\n\n```bash\nmemento diff [--group ] [--all] [--unified] [--tier ] [--provider ] [--resources ] [--scope ] [--include-global] [--json]\n```\n\n| Option | Description |\n| --- | --- |\n| `--group ` | Show one conflict group, such as `project/agents-md:main` |\n| `--all` | Show all diff groups |\n| `--unified` | Print unified diff output |\n| `--tier ` | Filter to one memory tier |\n| `--provider ` | Filter to one provider id |\n| `--resources ` | Resource kinds to diff |\n| `--scope ` | Resource scope for skills and MCP |\n| `--no-mcp` | Exclude MCP resources |\n| `--no-skills` | Exclude skill resources |\n| `--show-secrets` | Show raw secret-like values in diff output after explicit use |\n| `--include-global` | Include global memory in project diff mode |\n| `--json` | Emit JSON output |\n\n### `memento import`\n\n```bash\nmemento import [--dry-run] [--from ] [--to ] [--strategy ] [--resources ]\n```\n\n`import` reads assistant memory from another project directory and writes it into the current initialized project. By default it imports memory only. Add `--resources skills,mcp` when you explicitly want skills or MCP server definitions copied too.\n\n| Option | Description |\n| --- | --- |\n| `--dry-run` | Preview the import without writing files |\n| `--from ` | Comma-separated source provider ids |\n| `--to ` | Comma-separated target provider ids enabled in the current config |\n| `--strategy ` | Existing-target strategy: `prompt`, `skip`, `replace`, or `append` |\n| `--resources ` | Resource kinds to import: `memory`, `skills`, `mcp` |\n| `--scope ` | Resource scope for skills and MCP: `local`, `project`, or `cross-cli` |\n| `--tier ` | Import one memory tier |\n| `--yes` | Accept non-interactive defaults; currently replaces existing target content |\n\n### `memento restore`\n\n```bash\nmemento restore [--list] [--at ] [--group ] [--prune ]\n```\n\n| Option | Description |\n| --- | --- |\n| `--list` | List available restore points |\n| `--at ` | Restore from a timestamp listed by `--list` |\n| `--group ` | Restore one memory group |\n| `--prune ` | Keep the newest N backups and remove older backups |\n\n### `memento global`\n\n```bash\nmemento global init\nmemento global status\nmemento global sync\nmemento global watch\nmemento global diff\nmemento global restore\n```\n\nThe global subcommands mirror the project commands but use the global memento context at `~/.memento`.\n\n### `memento update`\n\n```bash\nmemento update\nmemento update --dry-run\n```\n\n`update` runs the npm global install command for the latest published release and shows the same memento ANSI header used by help and version output.\n\n### Exit codes\n\n| Code | Meaning |\n| --- | --- |\n| `0` | Success |\n| `1` | Generic error |\n| `2` | Unresolved conflict, usually from `--strategy fail` |\n| `3` | Not initialized; run `memento init` |\n| `4` | No active providers |\n\n---\n\n## Configuration\n\nProject configuration lives at:\n\n```text\n.memento/config.toml\n```\n\nGlobal configuration lives at:\n\n```text\n~/.memento/config.toml\n```\n\nExample:\n\n```toml\n[providers.claude-code]\nenabled = true\nauto = true\ninclude_orphan = false\n\n[providers.codex]\nenabled = true\nauto = true\ninclude_orphan = false\n\n[providers.gemini-cli]\nenabled = true\nauto = true\ninclude_orphan = false\n\n[providers.cursor]\nenabled = true\nauto = true\ninclude_orphan = false\n\n[providers.windsurf]\nenabled = true\nauto = true\ninclude_orphan = false\n\n[providers.antigravity]\nenabled = false\nauto = true\ninclude_orphan = false\n\n[resources.memory]\nenabled = true\n\n[resources.skill]\nenabled = true\ninclude = []\nexclude = []\n\n[resources.mcp]\nenabled = true\nredact_output = true\nproject_secret_policy = \"wizard\"\n\n[mapping]\n\"rule:typescript\" = [\n \"cursor:.cursor/rules/typescript.mdc\",\n \"windsurf:.windsurf/rules/typescript.md\",\n]\n\n[exclude]\npaths = [\n \"**/private/**\",\n \"**/generated/**\",\n]\n```\n\n### Provider settings\n\n| Field | Meaning |\n| --- | --- |\n| `enabled` | Whether the provider participates in sync |\n| `auto` | Whether automatic detection should be respected |\n| `include_orphan` | Include memory files even when the provider app or CLI is not installed |\n\n### Resource settings\n\n| Field | Meaning |\n| --- | --- |\n| `resources.memory.enabled` | Enable markdown memory synchronization |\n| `resources.skill.enabled` | Enable skill bundle synchronization |\n| `resources.skill.include` | Optional include patterns for skill resources |\n| `resources.skill.exclude` | Optional exclude patterns for skill resources |\n| `resources.mcp.enabled` | Enable MCP server definition synchronization |\n| `resources.mcp.redact_output` | Redact secret-like MCP values in command output |\n| `resources.mcp.project_secret_policy` | Policy for project-level MCP secrets; default is `wizard` |\n\n### Mapping overrides\n\nUse `[mapping]` when two files should be treated as the same identity but their default filenames would not match.\n\n```toml\n[mapping]\n\"rule:backend-style\" = [\n \"cursor:.cursor/rules/backend.mdc\",\n \"windsurf:.windsurf/rules/api-style.md\",\n]\n```\n\n### Excludes\n\nUse excludes for private, generated, large, or high-churn files.\n\n```toml\n[exclude]\npaths = [\n \"**/secrets/**\",\n \"**/scratch/**\",\n]\n```\n\n---\n\n## Conflict Resolution\n\nmemento compares normalized document bodies and the previous sync cache.\n\n| Strategy | Behavior | Best for |\n| --- | --- | --- |\n| `lww` | Last write wins; the newest modified file becomes the winner | automation, watch mode, quick local sync |\n| `prompt` | Ask which version should win, show diff, or edit manually | interactive terminal sessions |\n| `fail` | Exit with code `2` without writing conflicting groups | CI, pre-commit checks, strict workflows |\n\nExamples:\n\n```bash\nmemento sync --strategy lww\nmemento sync --strategy prompt\nmemento sync --strategy fail --dry-run\n```\n\n`memento watch` always uses `lww`, because a long-running file watcher cannot safely stop for interactive prompts.\n\n---\n\n## Backup & Restore\n\nBefore writing provider memory files, memento saves the previous contents under:\n\n```text\n.memento/backup//\n```\n\nBackups are local runtime artifacts and should not be committed.\n\nCommon commands:\n\n```bash\nmemento restore --list\nmemento restore --at \nmemento restore --at --group project/agents-md:main\nmemento restore --prune 10\n```\n\nUse restore when a sync chose the wrong winner, when you want to inspect older memory contents, or when a provider file was manually damaged after a sync.\n\n---\n\n## Claude Code Skill\n\nThe npm package includes a Claude Code skill for operating memento from inside Claude Code.\n\nDuring `npm i -g @dantelabs/memento`, the package postinstall step attempts to copy the skill into Claude's skills directory when that directory is available. If auto-install is skipped or you want to reinstall manually:\n\n```bash\nmemento install-skill\n```\n\nRemove it with:\n\n```bash\nmemento uninstall-skill\n```\n\nSkip automatic skill installation during npm install:\n\n```bash\nMEMENTO_SKIP_SKILL_INSTALL=1 npm i -g @dantelabs/memento\n```\n\n---\n\n## Safety Model\n\nmemento is intentionally conservative around writes.\n\n- Local-only: files are read and written on your machine; memento does not upload memory content.\n- Explicit config: project sync requires `.memento/config.toml`.\n- Dry-run support: use `memento sync --dry-run` before writing.\n- Resource dry-run support: preview skills and MCP changes with `--resources ... --dry-run`.\n- Automatic backups: every write has a restore point.\n- Conflict strategies: choose `prompt` for manual control or `fail` for CI.\n- MCP secret awareness: secret-like fields are redacted in output by default.\n- Shared global dedupe: shared Gemini/Antigravity global paths are handled once.\n- Watch ignore rules: `.memento` cache and backup writes do not retrigger sync loops.\n\nRecommended team practice:\n\n- Commit shared `project` memory files when they are meant for the whole repository.\n- Keep `project-local` and `.memento/cache.json` out of git.\n- Review `memento diff --all --unified` before the first sync in an existing repository.\n- Use `memento sync --strategy fail --dry-run` in CI if memory drift should block merges.\n\n---\n\n## Developer & Support\n\nmemento is built and maintained by **Dante Labs** as part of a broader toolkit for practical AI-agent workflows.\n\n| Link | Description |\n| --- | --- |\n| **GitHub** | [dandacompany/memento](https://github.com/dandacompany/memento) |\n| **npm** | [@dantelabs/memento](https://www.npmjs.com/package/@dantelabs/memento) |\n| **YouTube** | [@dante-labs](https://youtube.com/@dante-labs) |\n| **Email** | [dante@dante-labs.com](mailto:dante@dante-labs.com) |\n| **Support** | [Buy Me a Coffee](https://buymeacoffee.com/dante.labs) |\n\nIf memento saves you time, helps keep your agent context clean, or becomes part of your daily workflow, sponsorship is appreciated and helps fund continued maintenance, new provider adapters, and real-world compatibility testing.\n\nIssues, bug reports, and provider mapping requests are welcome on GitHub.\n\n---\n\n## License\n\n[MIT](LICENSE) \nCopyright (c) 2026 Dante Labs.\n\n---\n\n
\n\n**Dante Labs** · **YouTube** [@dante-labs](https://youtube.com/@dante-labs) · **Email** [dante@dante-labs.com](mailto:dante@dante-labs.com) · **Support** [Buy Me a Coffee](https://buymeacoffee.com/dante.labs)\n\n