Skip to content

Consolidate plugins & skills into main repo + build Codex plugin #699

Open

Description

@bm-clawd

Context

Codex CLI now supports plugins (docs) — installable bundles that can package skills, MCP servers, and app integrations.

Our advantage:

  • Codex users are already our biggest traffic source (79 clicks/week on docs:/integrations/codex)
  • "codex memory" is a top search query (pos 4.0, 30 clicks/week)
  • We already have a working MCP server — plugin is just better packaging

Current State (repo sprawl)

We have 3 separate repos that are really just different ways to distribute the same thing:

  1. basic-memory-skills — 10 skills teaching agents how to use BM effectively
  2. basic-memory-plugins — Claude Code plugin (skills + commands + hooks)
  3. Need: Codex plugin — same skills, different packaging format

All three are core BM functionality, not separate products. They should live in the main repo.

Proposed Unified Structure

basic-memory/
├── src/                        # Python MCP server + CLI (existing)
├── docs/                       # Docs (existing)
├── skills/                     # ← Merge basic-memory-skills here
│   ├── memory-tasks/
│   ├── memory-schema/
│   ├── memory-reflect/
│   ├── memory-notes/
│   ├── memory-defrag/
│   └── ... (10 total)
└── plugins/                    # ← Merge basic-memory-plugins here
    ├── claude-code/            # Claude Code plugin
    │   ├── .claude-plugin/
    │   ├── skills/             # Can reference ../skills/
    │   └── commands/
    └── codex/                  # New Codex plugin
        ├── .codex-plugin/
        ├── skills/             # Can reference ../skills/
        └── .mcp.json

Why Consolidate

Single source of truth:

  • Skills are core functionality, not a separate product
  • Plugins are distribution mechanisms for those skills
  • Easier to keep in sync with BM version bumps

Avoid duplication:

  • Many skills are identical across Claude Code/Codex plugins
  • Can reference or copy from central /skills/ directory
  • Single README, single release process

Discoverability:

  • New users find everything in one place
  • Clear hierarchy: BM server → skills → plugins

Codex Plugin Specifics

What it includes:

  1. MCP server config (.mcp.json) — auto-configures uvx basic-memory
  2. Skills (reuse from /skills/):
    • memory-search — "Search my knowledge graph for X"
    • memory-write — "Save this to my knowledge graph"
    • memory-context — "Load context about X from my graph"
    • memory-tasks — "Create/update tasks that survive compaction"
    • memory-projects — "Switch to project Y"
  3. Assets — icon, logo, screenshots
  4. Manifest (.codex-plugin/plugin.json) — metadata, install surface copy

Distribution:

  1. Initial: Local marketplace (users install via GitHub URL)
  2. Later: Submit to official OpenAI Plugin Directory (when available)

Competitive position:

Mem0, Letta, Zep — all API-based, no Codex plugins yet
We'd be first with a real knowledge graph plugin for Codex

Migration Plan

  • Move /skills/ from basic-memory-skills → basic-memory/skills/
  • Move contents from basic-memory-plugins → basic-memory/plugins/claude-code/
  • Create basic-memory/plugins/codex/ for Codex plugin
  • Build Codex plugin (manifest + .mcp.json + skills + assets)
  • Test both plugins (Claude Code + Codex) from consolidated repo
  • Update marketplace URLs to point to subdirectories
  • Archive basic-memory-skills and basic-memory-plugins repos (README redirects)
  • Document plugin installation in docs.basicmemory.com
  • Announce in Discord + social
  • Submit Codex plugin to OpenAI directory (when available)

Example Plugins to Study

Open Questions

  • Should plugins reference ../skills/ via symlinks or copy files during build?
  • Do we need cloud API integration in plugins or just local MCP?
  • What starter prompts should we suggest in defaultPrompt for Codex?
  • Can we auto-configure project routing (multi-project support)?

Related Repos

Activity

  1. claude commented on Mar 27, 2026

    @claude
    Contributor

    Claude finished @bm-clawd's task in 1m 7s —— View job


    Issue Triage

    • Analyze issue
    • Check for duplicate issues — no duplicates found
    • Apply labels — applied enhancement (other labels not available in repo)
    • Provide triage summary

    Triage Summary

    Type: Feature Request — New distribution/packaging mechanism for the existing Basic Memory MCP server

    Classification:

    Field Value
    Type Feature / Enhancement
    Priority Medium
    Component MCP tools, Documentation
    Complexity Complex

    No duplicates found.

    Analysis:

    This is a well-researched feature request to package the existing Basic Memory MCP server as a Codex CLI plugin. The author has done thorough research and provided:

    • Complete plugin structure
    • Example plugin.json and .mcp.json content
    • Skills to include
    • Distribution plan

    Key open questions from the issue that need decisions before implementation:

    1. Repo location — New basic-memory-codex-plugin repo vs. subdirectory in this repo
    2. Cloud vs local only — Plugin initially could be local-only (just wraps uvx basic-memory)
    3. Starter prompts — What goes in defaultPrompt for each skill
    4. Multi-project support — Whether to support project routing in the plugin config

    Recommended next steps:

    1. Decide on repo location (separate repo seems cleaner for a plugin distribution)
    2. Build minimal plugin: plugin.json + .mcp.json + 3 skills (search, write, context)
    3. Test local install via Codex marketplace
    4. Add docs to basicmemory.com
    5. Announce when ready, submit to OpenAI directory when available

    This is a strategic opportunity (Codex users = biggest traffic source) with low implementation risk since the MCP server already exists — the plugin is primarily packaging and skill prompts.

  2. changed the title [-]Build Codex Plugin for Basic Memory[/-] [+]Consolidate plugins & skills into main repo + build Codex plugin[/+] on Mar 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions