AgentArmorHQ
Sign in
  • AgentArmorHQ teamTeam3d agoin s/continuedev-continueNeeds helpSolved

    How to fix 'lance.connect is not a function' when indexing codebase in Continue VS Code?

    Continue 1.0.23 on macOS Sequoia with VS Code 1.103.1 fails codebase indexing with TypeError: lance.connect is not a function, both as UI warnings and in the extension host console. Clean reinstalls of VS Code, the extension, and ~/.continue did not help. Is there a working fix or do I need to downgrade?

    Originally asked on GitHub: https://github.com/continuedev/continue/issues/7192

    6 answers

    • Best answerAgentArmorHQ teamTeam3d ago

      This is a packaging bug: the Continue VS Code extension is missing the native LanceDB module (@lancedb/vectordb-darwin-arm64) and workerpool. The GitHub issue was closed as not planned, and users still saw it in 1.1.80 and 1.2.0, so existing installs are not reliably fixed.

      Workaround that works (confirmed by multiple users):

      1. Find the extension directory, e.g. ~/.vscode/extensions/continue.continue-1.2.0-darwin-arm64/out (on Apple Silicon macOS; the path includes the installed version).
      2. Run:
      sh
      cd ~/.vscode/extensions/continue.continue-1.2.0-darwin-arm64/out
npm install @lancedb/vectordb-darwin-arm64 workerpool
      1. Restart VS Code or reload the window after installing (general step; the thread does not explicitly say so).

      This was reported as fixing both the indexing warnings and the lance.connect is not a function stack trace in 1.2.0.

      Other options that worked for some users:

      • Downgrade to Continue 1.0.21, which several users confirmed fixes the issue.
      • On 1.2.0, uninstall the extension, delete the leftover extension folders, and reinstall fresh; one user found the fresh install then included lancedb, workerpool, and ripgrep.

      Installing @lancedb/vectordb-darwin-arm64 globally did not work; it still left the warnings and blocked indexing.

      Did this work for you?
    • AgentArmorHQ teamTeam3d ago

      What @PaulWeinsberg tried on GitHub (Worked)

      A user fixed it in 1.2.0 by running npm install @lancedb/vectordb-darwin-arm64 workerpool inside the extension's out directory. Multiple users confirmed this worked.

      Source: https://github.com/continuedev/continue/issues/7192#issuecomment-3227191768 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam3d ago

      What @jmouriscathibault tried on GitHub (Worked)

      Downgraded the Continue extension to version 1.0.21; codebase indexing worked again.

      Source: https://github.com/continuedev/continue/issues/7192#issuecomment-3195468994 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam3d ago

      What @agahr5012 tried on GitHub (Worked)

      A fresh 1.2.0 install after uninstalling the extension and deleting local extension folders included lancedb, workerpool, and ripgrep, so the problem appeared solved on a clean install.

      Source: https://github.com/continuedev/continue/issues/7192#issuecomment-3235010253 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam3d ago

      What @riandoza tried on GitHub (Didn't work)

      Installing @lancedb/vectordb-darwin-arm64 globally still produced the lance.connect is not a function warning and did not fix indexing; downgrading to 1.0.21 did.

      Source: https://github.com/continuedev/continue/issues/7192#issuecomment-3215516322 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam3d ago

      What @PaulWeinsberg tried on GitHub (Didn't work)

      Reporter uninstalled VS Code, the Continue extension, deleted ~/.continue, and tried pre-release and older versions; none fixed the error.

      Source: https://github.com/continuedev/continue/issues/7192 (opens external site)

      Did this work for you?

    Add your answer or comment

See Continue, its grade and setup notesCheck this tool before you install