Coder DB - AI Memory Enhancement System

Created By
angrysky56a year ago
An intelligent code memory system that leverages vector embeddings, structured databases, and knowledge graphs to store, retrieve, and analyze code patterns with semantic search capabilities, quality metrics, and relationship modeling. Designed to enhance programming workflows through contextual recall of best practices, algorithms, and solutions.
Overview

what is Coder DB?

Coder DB is an AI memory enhancement system designed to improve programming workflows by leveraging vector embeddings, structured databases, and knowledge graphs to store, retrieve, and analyze code patterns with semantic search capabilities.

how to use Coder DB?

To use Coder DB, you can store code snippets, patterns, and solutions in the Qdrant vector database, maintain a structured catalog of algorithms in SQLite, and represent relationships between coding concepts using a knowledge graph.

key features of Coder DB?

  • Semantic search and retrieval of code patterns using Qdrant.
  • Structured algorithm storage and versioning with SQLite.
  • Knowledge graph integration for representing relationships between coding concepts.
  • Enhanced metadata storage for code patterns including quality metrics and user feedback.

use cases of Coder DB?

  1. Enhancing problem-solving workflows by querying for similar solutions.
  2. Storing and retrieving reusable code patterns and best practices.
  3. Maintaining a structured catalog of algorithms with performance metrics.
  4. Analyzing relationships between coding concepts to discover trends.

FAQ from Coder DB?

  • Can Coder DB help with all programming languages?

Yes! Coder DB supports multiple programming languages and frameworks.

  • Is Coder DB free to use?

Yes! Coder DB is open-source and free to use for everyone.

  • How does Coder DB ensure data integrity?

Coder DB implements role-based access controls, regular backups, and sanitization of sensitive information.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
angrysky56
Star
1
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