Basic Memory

Created By
basicmachines-coa year ago
Knowledge management system that allows you to build a persistent semantic graph from conversations with AI assistants. All knowledge is stored in standard Markdown files on your computer, giving you full control and ownership of your data. Integrates directly with Obsidan.md
Overview

What is Basic Memory?

Basic Memory is a knowledge management system that allows users to build a persistent semantic graph from conversations with AI assistants, storing all knowledge in standard Markdown files on their computer.

How to use Basic Memory?

To use Basic Memory, install it via the command line, configure it with your AI assistant (like Claude), and start creating notes by conversing with the AI. You can also manage projects and sync your knowledge base using CLI commands.

Key features of Basic Memory?

  • Local storage of knowledge in Markdown format
  • Integration with AI assistants for dynamic note-taking
  • Bidirectional synchronization between AI and user notes
  • Support for multiple projects and semantic relationships
  • Easy access and editing through familiar tools like Obsidian

Use cases of Basic Memory?

  1. Building a personal knowledge base that evolves over time.
  2. Capturing and structuring information from conversations with AI.
  3. Managing separate knowledge graphs for different projects or topics.

FAQ from Basic Memory?

  • Can I use Basic Memory with any AI assistant?

Yes, Basic Memory is designed to work with any compatible AI assistant using the Model Context Protocol (MCP).

  • Is my data secure with Basic Memory?

Yes, all data is stored locally on your computer, giving you full control and ownership.

  • How do I back up my knowledge?

You can back up your Markdown files using standard file backup methods.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
basicmachines-co
Star
-
Language
-
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)

20 hours ago
Gpt Scrambler

2 days ago