Skip to content

fix: native codedb stays callable when codedb-pro is licensed - #652

Closed
justrach wants to merge 2 commits into
mainfrom
cursor/codedb-always-4ffc
Closed

fix: native codedb stays callable when codedb-pro is licensed#652
justrach wants to merge 2 commits into
mainfrom
cursor/codedb-always-4ffc

Conversation

@justrach

@justrach justrach commented Aug 27, 2026

Copy link
Copy Markdown
Owner

A licensed codedb-pro seat hid and refused native codedb / read_file (including rlm codedb(...)). Walking a repo then died with “codedb is blocked while the LICENSED code-intelligence suite is in charge” and fell through to metered inspect/search.

ADR 0040: ordinary reads use native codedb or read_file, licensed or not. codedb-pro is extra search/batch, not the default reader.

  • codedb and read_file stay in the catalog and run
  • no redirect/refuse to mcp__codedbpro__read
  • cat/head are not licensed-gated; Licensed codedb-pro: one read surface, one edit surface #626 still steers a concrete source-file scan toward codedb
  • prompts say READ with codedb/read_file; faster_search only when codedb cannot answer
  • companion write tools stay hidden (they bypass /rewind)
  • leading grep/rg may still point at zigrep
Open in Web Open in Cursor 

A licensed suite hid and refused codedb (including rlm codedb), so a
repo walk died on "codedb is blocked" and fell through to metered
inspect/search. codedb is free and indexed — it always runs. read_file
and leading shell cat/grep still redirect. ADR 0040.
read_file stays in the catalog and is no longer redirected or refused
to mcp__codedbpro__read. cat/head are not licensed-gated. codedbGuard
steers source-file scans to codedb whether or not pro is licensed.
Prompts say READ with codedb/read_file; pro is extra search only.
@justrach

Copy link
Copy Markdown
Owner Author

Already on main (ADR 0040). Closing as superseded.

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.

2 participants