basic-memory-pi-setup

Configure Basic Memory continuity for a Pi workspace via a project-local JSON file.

4.0k|282|Updated Dec 2, 2024
One-click install
npx skills add https://github.com/basicmachines-co/basic-memory --skill basic-memory-pi-setup-basicmachines-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: basic-memory-pi-setup
Source: https://github.com/basicmachines-co/basic-memory/tree/main/integrations/pi/skills/basic-memory-pi-setup
Command: npx skills add https://github.com/basicmachines-co/basic-memory --skill basic-memory-pi-setup-basicmachines-co

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pi-mcp-adapter.

What problem does it solve? Pi workspaces lack durable memory across sessions unless Basic Memory is explicitly configured, and users risk mutating their global default project or enabling automation in untrusted workspaces without guidance. ## Core Features & Use Cases - Project-local configuration: Creates a .pi/basic-memory.json file that binds the workspace to a chosen Basic Memory project without touching global defaults. - CLI or MCP transport selection: Defaults to CLI transport requiring only bm on PATH, with guided switching to MCP mode via the pi-mcp-adapter npm package. - Trust-gated automation: Enables automatic recall and capture only after the user confirms workspace trust via BASIC_MEMORY_PI_TRUST_WORKSPACE=1, keeping manual /bm-recall and /bm-capture available otherwise. - Use Case: A developer starting a new Pi workspace runs /bm-status, sees no project configured, and uses this Skill to bind the workspace to their Basic Memory project with auto recall and capture enabled. ## Quick Start Set up Basic Memory for this Pi workspace and connect it to my project with automatic recall and capture enabled.

Frequently Asked Questions about basic-memory-pi-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up Basic Memory in a Pi workspace?▼

Create a .pi/basic-memory.json file in the workspace specifying the transport, project name, capture folder, and auto recall/capture flags. Run /bm-status first to check current state, then verify with /bm-recall or /bm-capture after configuration.

Should I use CLI or MCP transport for Basic Memory in Pi?▼

CLI transport is the default and only requires the bm command on PATH. Choose MCP transport if you want MCP tool integration, which requires installing the pi-mcp-adapter npm package and setting transport to mcp in the config.

Why is automatic recall and capture not working after configuring the project?▼

A project mapping alone does not enable automation. You must confirm trust in the workspace and set BASIC_MEMORY_PI_TRUST_WORKSPACE=1 in the environment used to launch Pi; manual /bm-recall and /bm-capture still work without it.

Does Pi setup change my global Basic Memory default project?▼

No. The setup writes only a project-local .pi/basic-memory.json file and explicitly avoids mutating the global default project, keeping routing predictable per workspace.

How do I use a local Basic Memory development build with Pi?▼

In a trusted workspace, set BASIC_MEMORY_PI_TRUST_BM_COMMAND=1 and define bmCommand as an argv array such as ["uv", "run", "--project", "/path/to/basic-memory", "basic-memory"]. This overrides bmPath without invoking a shell.