Skip to content

The Cursor plugin local connection and memory search are tested - #759

Merged
zlareb1 merged 1 commit into
mainfrom
docs/cursor-native-tested
Nov 17, 2026
Merged

zlareb1 merged 1 commit into
mainfrom
docs/cursor-native-tested

Conversation

@zlareb1

@zlareb1 zlareb1 commented Nov 17, 2026

Copy link
Copy Markdown
Member

Changelog category

  • Documentation

Changelog entry

The native Cursor plugin's local single-user MCP connection and read-only memory search are tested.

Why

The native clickhouse-loom package loads its two skills, lists its MCP tools, and answers a read-only memory search. Its manifest and integration pages still describe it as untested.

Scope and risk

Removes the untested notes from the native manifest and transcript-hook README. The integration page states the tested scope: local single-user MCP and read-only memory search. Marketplace availability remains described as unlisted. The diff changes no runtime code or hooks. Browser OAuth and transcript capture were outside the native smoke test.

Compatibility, rollout and rollback

  • Wire: none.
  • Operator steps: none.
  • Rollback: revert the three text edits.

Tests

  • Native Cursor 3.27.22, plugin 1.2.0: the local package loads loom and loom-code, lists 21 tools and one resource, and answers loom_search for cursor-plugin-smoke-test with an empty result from an empty test database. The Loom server uses fake providers. The temporary server and database are removed after testing.
  • make format, make lint, and make typecheck pass.
  • pytest tests/unit/test_cursor_plugin.py tests/unit/test_release_prepare.py tests/unit/test_published_links.py tests/unit/test_doc_links.py tests/unit/test_public_copy.py -q: 362 passed.
  • Plugin sync, both plugin validators, the hook, grep-shim and Cline JavaScript suites, and generic ingest checks pass.
  • Broader local checks encounter parser subprocess, ClickHouse-local and release-shell failures on macOS; the transcript-hook contract also fails its existing Markdown path comparison. Full-suite GitHub CI validation is required before merge, as authorized by the repository owner.

AI assistance in the code

  • AI-generated: Codex wrote the text edits and checked them against the native application result and focused tests.

  • I can explain every line of this diff and how it interacts with the rest of Loom.

Checklist

  • Full-suite CI passes before merge; local formatting, lint, type checks and focused tests pass.
  • Generated files are unchanged; the plugin sync check passes.
  • No migration changes.
  • No shipped plugin behaviour changes; versions are unchanged.
  • No frontend changes.
  • Docs describe the tested scope and current marketplace status; there are no operator or wire changes.
  • Repository text has no dates, people, host names, internal namespaces, ticket or decision numbers.
  • Commit is signed off.

Remove the untested notes after the native package loads both skills and answers a read-only memory search.

Signed-off-by: Lareb Zafar <lareb.zafar@clickhouse.com>
@zlareb1
zlareb1 merged commit 9953ba6 into main Nov 17, 2026
51 of 52 checks passed
@zlareb1
zlareb1 deleted the docs/cursor-native-tested branch November 17, 2026 18:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant