VectorCode

Created By
Davidyza year ago
A code repository indexing tool to supercharge your LLM experience.
Overview

What is VectorCode?

VectorCode is a code repository indexing tool designed to enhance the experience of using large language models (LLMs) by indexing and providing contextual information about the code repositories you are working on.

How to use VectorCode?

To use VectorCode, you can install the command-line tool or the Neovim plugin. Follow the setup instructions in the documentation to get started with indexing your code repositories and utilizing the features of the tool.

Key features of VectorCode?

  • Indexing of code repositories for better context in LLM prompts.
  • Integration with Neovim for seamless coding experience.
  • Support for multiple embedding engines through Chromadb.
  • Basic retrieval and embedding functionalities with room for improvements.

Use cases of VectorCode?

  1. Enhancing code completion suggestions in LLMs for less-known or closed-source projects.
  2. Assisting developers in writing better prompts for AI coding assistants.
  3. Providing contextual information for complex coding tasks.

FAQ from VectorCode?

  • What is the purpose of VectorCode?

VectorCode aims to improve the understanding of LLMs regarding code repositories, especially those that are not well-known or closed-source.

  • Is VectorCode free to use?

Yes! VectorCode is open-source and free to use.

  • What programming languages does VectorCode support?

VectorCode is primarily developed in Python and supports various programming languages through its indexing capabilities.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Davidyz
Star
442
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago