v1.6.1

The npm page for both @xmu-labs/xkg and mnemos-capture now shows the current README: connect commands use @xmu-labs/xkg, plus a trademark note, a homepage link (xkg.xmu.sh) and a bug-report link. Publishing builds the CLI first, so the “No bin file found” warning is gone.

v1.6.0

The CLI has a new npm name: @xmu-labs/xkg

npx -y @xmu-labs/xkg@latest serve-mcp --key YOUR_API_KEY

npm doesn't accept plain xkg as a name (it's too close to existing packages), so the package lives under the xmu-labs scope. The command you type is still xkg.

Nothing breaks

• mnemos-capture still works. Every release is published under both names, so existing MCP configs and npx mnemos-capture@latest keep updating.
• Hooks migrate themselves. Next time the MCP server starts, hooks that use mnemos-capture switch to @xmu-labs/xkg@latest, and --briefing is kept. Hooks from other packages are never touched.
• Self-update keeps each install on the name it was installed with.

Also in this release

• The app now runs on xkg.xmu.sh. Connectors set up with mnemos-capture.vercel.app keep working.
• Patched Next.js (security fix).
• Replaced the deprecated @vercel/postgres driver with Neon's driver.
• Upgraded to Tailwind CSS v4, with no visual change.
• Dependency updates.

For maintainers

Releases go through scripts/publish.sh, which publishes both names. It checks both before publishing either, so a failure can't leave them out of sync. The release workflow verifies the commit and the dist-tag for each name.

v1.5.0

Changes

• The CLI now defaults to https://xkg.xmu.sh. Existing setups on mnemos-capture.vercel.app keep working and update automatically.
• Captures from Wikipedia-style pages no longer include reference markup.

v1.4.1

Security

• kos no longer leaks plans into git. When xkg kos ran from a linked worktree or a submodule, the plan file was not excluded and could be committed by the agent. kos now asks git for the right exclude file, verifies the plan is ignored before writing it, and stops if it isn't. The plan file is now XKG_PLAN.md.

Changes

• The repository moved to xmu-labs/xkg; links and package metadata point there.
• Internal names continue the move from mnemos to xkg. Old names, config folders and env vars keep working.

v1.4.0 - xkg

v1.4.0 — xkg

The product is xkg. The npm package, GitHub repo, and hosted URL still say mnemos-capture.

New

• CLI binary xkg (also xmu and mnemos-capture)
• New MCP keys mint as xkg_; xmu_ and mnemos_ still work
• Config prefers ~/.xkg/, then ~/.xmu/, then ~/.mnemos/
• MCP serverInfo.name is xkg

Notes

• npx still uses: npx -y mnemos-capture@latest
• Do not run npx xmu — that npm name is taken
• Hosted app: https://mnemos-capture.vercel.app

Upgrading

npx -y mnemos-capture@latest serve-mcp --key YOUR_API_KEY

v1.3.0 — Xmu

v1.3.0 — Xmu

The product is Xmu. The npm package, GitHub repo, and hosted URL still say mnemos-capture until a dedicated domain ships.

New

• CLI binary xmu (also mnemos-capture)
• New MCP keys mint as xmu_…; existing mnemos_… keys still authenticate
• Config prefers ~/.xmu/, falls back to ~/.mnemos/
• MCP serverInfo.name is xmu; a local config still named mnemos keeps working
• Connector icons for MCP clients (Claude, ChatGPT, and anything that reads serverInfo.icons)

Notes

• npx still uses the package name: npx -y mnemos-capture@latest
• Do not run npx xmu — that npm name is an unrelated empty package
• Hosted app: https://mnemos-capture.vercel.app

Upgrading

npx -y mnemos-capture@latest serve-mcp --key YOUR_API_KEY

After a global install (npm i -g mnemos-capture), xmu is on your PATH.

v1.2.0 — Capture anything. Your agents apply it.

v1.2.0 — Capture anything. Your agents apply it.

Mnemos becomes an active knowledge-application pipeline: capture → brief → plan → implement with any AI assistant.

New

• Active briefing — briefing returns ranked suggestions + generate_plan prompt when high-score captures exist; plans saved to plans/ with Codebase Mapping + Verification Checklist
• kos orchestrator — mnemos kos creates an isolated git worktree and hands the plan to whatever assistant you run (claude -p, codex exec, aider, …); configure once with mnemos config set agent "<cmd>"
• Model-agnostic BYOK — central callLlm() adapter for Anthropic (SDK), OpenAI, and Google (REST); onboarding UI + API now accept a provider field
• Vault hook (opt-in) — setup-hooks --vault installs a PreToolCall hook that surfaces relevant captures before file edits, deduped per session
• Curator — curate HEAD-checks URLs (404/410 → stale, timeout → ok), flags lowConfidence captures, optional auto_archive; batch cap 20
• source_type — url / note / paste auto-detected and written to frontmatter + INDEX.md
• list_plans — new MCP tool to list or read saved plans

Fixed

• lowConfidence was never written to frontmatter — curate's regex was matching a field that didn't exist

Upgrading

npx mnemos-capture@latest serve-mcp --key <your-key>
mnemos config set agent "claude -p"
mnemos kos

v1.1.0 — Automatic hook setup, briefing mode, always-latest

v1.1.0 — Automatic hook setup, briefing mode, always-latest enforcement

Highlights

This release closes the gap between capturing knowledge and surfacing it inside Claude Code sessions, and ensures users always run the latest version of mnemos-capture.

New features

Automatic SessionStart hook

Installs silently on the first serve-mcp run. Every Claude Code session now opens with a one-line nudge:

Mnemos: 4 captures in inbox — run list_inbox to review

Your agent sees this before the conversation begins and can proactively surface pending captures instead of waiting for you to ask. Zero configuration required — the hook lands in ~/.claude/settings.json automatically.

--briefing mode (opt-in)

Replaces the inbox count with an LLM-composed briefing grounded in your current git branch, last 5 commits, and CLAUDE.md excerpt. Tells your agent exactly which captures matter for what you're working on right now.

npx -y mnemos-capture@latest setup-hooks --key YOUR_KEY --briefing

Adds ~5 seconds to session start (calls the briefing MCP tool, uses your Anthropic key).

Always-latest enforcement

Three layers of defense so nobody runs a stale version:

1. @latest everywhere — install command and all hook commands now use npx -y mnemos-capture@latest, forcing npx to check the registry on every invocation
2. Self-upgrade safety net — serve-mcp queries the npm registry on startup; if a newer version exists, it respawns via npx -y mnemos-capture@<new> with stdio: inherit. A MNEMOS_UPGRADED=1 env var prevents recursion
3. Legacy hook migration — pre-1.1.0 hooks without @latest are silently rewritten on next serve-mcp run, preserving any --briefing flag the user already set

New CLI commands

Command	What it does
npx mnemos-capture setup-hooks --key KEY [--briefing]	Manually install or upgrade the hook in ~/.claude/settings.json
npx mnemos-capture inbox-check --key KEY [--briefing]	What the hook actually runs (callable directly for debugging)

Where the hook works

Surface	Hook fires automatically
Claude Code CLI (terminal)	Yes
VS Code extension	Yes
JetBrains extension	Yes
Claude Code desktop app	Yes
Claude Code on the web	No (different settings location)
Cursor / other MCP clients	No (different config system)

The MCP tools themselves (list_inbox, briefing, recall, search_captures, …) work in all of these surfaces — only the proactive nudge is specific to Claude Code reading your local settings file. For unsupported surfaces, add a line to your project's CLAUDE.md like "At session start, call list_inbox to surface pending captures" for a portable alternative.

Upgrading

New users: follow the updated README install command. @latest is now the default.

claude mcp add mnemos -- npx -y mnemos-capture@latest serve-mcp --key YOUR_KEY

Existing users: nothing to do. Your next Claude Code session will pull 1.1.0 automatically through serve-mcp's self-upgrade path. The hook will be installed silently. Legacy hook commands (without @latest) will be migrated on the same run.

No breaking changes

All features are additive. Existing MCP registrations, API keys, knowledge repos, and ~/.claude/settings.json configurations continue to work unchanged.

Files changed

cli/hooks.ts          (new)    setupHooks + inboxCheck + project-context detection
cli/version-check.ts  (new)    getCurrentVersion + maybeSelfUpgrade
cli/index.ts          (edited) setup-hooks + inbox-check commands, updated help
cli/mcp-server.ts     (edited) self-upgrade + auto-install on startup
cli/tsconfig.json     (edited) types: ["node"] so CLI compiles
README.md             (edited) documented all new flows
package.json          (edited) version 1.0.6 → 1.1.0

Pull request

#13 — v1.1.0: automatic hook setup, briefing mode, always-latest enforcement