Skip to content
mcp/harbor

Kindex changelog

io.github.wandercom/kindex

10 changes recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.

  • server.json 1 field changed
    version
    0.54.1 0.54.2

  • server.json 1 field changed
    version
    0.53.0 0.54.1

  • server.json 1 field changed
    version
    0.52.0 0.53.0

  • AGENTS.md +2 −2

    https://raw.githubusercontent.com/wandercom/kindex/HEAD/AGENTS.md 

    − Install Python test dependencies (`pip install -e ".[dev,mcp]"`) and Node.js 24 or newer.− The `CI` workflow runs full `pytest` with Python 3.12, Node.js 24, and `.[dev,mcp]` on pull+ Install Python test dependencies (`pip install -e ".[dev,mcp,vectors]"`) and Node.js 24 or newer.+ The `CI` workflow runs full `pytest` with Python 3.12, Node.js 24, and `.[dev,mcp,vectors]` on pull
  • llms.txt +3 −3

    https://kindex.tools/llms.txt 

    −   --wake codex --session last --cwd "$PWD" \−   --wake opencode --session last --cwd "$PWD" --wake-agent build \− Boundary: `remind_create` records a reminder. Due reminders fire only when `kin remind check`, `kin remind exec`, `kin cron`, or an installed `kin setup-cron` schedule runs. Codex/OpenCode wakeups start headless turns from that checker context; Kindex does not interrupt an idle interactive TUI by itself.+   --wake codex --session YOUR_SESSION_ID --cwd "$PWD" \+   --wake opencode --session YOUR_SESSION_ID --cwd "$PWD" --wake-agent build \+ Boundary: `remind_create` records a reminder. Due reminders fire only when `kin remind check`, `kin remind exec`, `kin cron`, or an installed `kin setup-cron` schedule runs. Codex, Claude, Antigravity, Cursor, OpenCode and Muse wakeups start or resume headless turns from that checker context; Kindex does not interrupt an idle interactive TUI by itself. Notification output is separate from wakes and defaults to `/dev/null`; set `reminders.output_destination` or `--destination` to route it.

  • server.json 1 field changed
    version
    0.49.0 0.52.0

  • server.json 1 field changed
    version
    0.48.1 0.49.0

  • AGENTS.md +19 −2

    https://raw.githubusercontent.com/wandercom/kindex/HEAD/AGENTS.md 

    −    The registry is how MCP clients discover the server, and it stalled at 0.38.0 through six PyPI releases because nothing automated it.− - Generated `.kin` artifacts (`.kin/index.json`, `.kin/code-map.json`): never hand-resolve a git conflict in them. `kin index` auto-registers the `kin merge-kin` structured union merge driver (via `.gitattributes` + local `.git/config`); `kin setup-merge` (re)installs it per clone. Regenerate with `kin index` / `kin export code-map` rather than hand-editing the JSON.+ ## Project knowledge preservation+ Kindex databases hold durable state and may be its only complete copy. Capture+ and update knowledge through the supported Kindex tools in the selected graph.+ Do not delete a Kindex database, including an ignored worktree database, as a+ cache or assume tracked JSON/JSONL files can reconstruct it.+ - Stage and commit matching `.kin/config` and `.kin/index.json` changes with code.+ - Use `kin repo-memory publish` for explicitly selected active public/team+   concepts, decisions, and questions. It is an evidence transport, not a full+   database backup. Keep private knowledge, credentials, and local state out of Git.+ - Preserve both knowledge artifacts if JSON and JSONL coexist. Publish/import+   refuse that layout until their records are explicitly reconciled into one file.+ - Preserve databases and relevant source records during migration or worktree+   cleanup. Report unsupported fields, missing evidence, and unresolved references;+   neither a summary index nor selected exports prove complete recovery.+ The planned canonical JSONL architecture and its unimplemented recovery+ requirements are documented in+ [canonical-knowledge-migration.md](docs/canonical-knowledge-migration.md).+    The registry is how MCP clients discover the server.+ - Generated `.kin` snapshots are not complete canonical knowledge or lossless conflict archives. `kin merge-kin` selects same-ID index conflicts by timestamp (ties keep ours); code-map collisions can keep ours. Preserve both input snapshots and relevant knowledge before regenerating with `kin index` / `kin export code-map` from the selected graph and merged code; an incomplete local graph must not overwrite another branch's knowledge. Do not hand-edit generated snapshots. `kin index` auto-regist

  • server.json 1 field changed
    version
    0.46.0 0.48.1

  • server.json 1 field changed
    version
    0.45.0 0.46.0
Kindex MCP server