pacman

 ____   _    ____ __  __    _    _   _
|  _ \ / \  / ___|  \/  |  / \  | \ | |
| |_) / _ \| |   | |\/| | / _ \ |  \| |
|  __/ ___ \ |___| |  | |/ ___ \| |\  |
|_| /_/   \_\____|_|  |_/_/   \_\_| \_|

Waka through project context with Claude Code, Codex, and Slack. Your memory stays in local files or a Google Drive folder you control.

Arcade Pitch

Use pacman when you want assistants to stay grounded in your actual workspace instead of a hidden hosted database.

• Keep context in Markdown and JSON you can inspect
• Share one workspace across Claude Code, Codex, and Slack
• Register one MCP server for both coding clients
• Sync project signals from tools like Slack, GitHub, GitLab, Gmail, and Google Drive
• Generate replies from saved canonical context, derived summaries, and raw evidence you control

Insert Coin

npm install -g @mukulaggarwal/pacman

pacman --help
pacman mcp claude install --help
pacman mcp codex install --help

npm install -g @mukulaggarwal/pacman@latest

Choose Your Route

pacman init -d .personal-assistant

This launches the onboarding UI and configures your profile, assistant identity, storage backend, integrations, and sync schedule.

The onboarding form is checkpointed in browser localStorage, so refreshes and reopened tabs resume from the same draft.

Use the Hard Reset Onboarding Draft action from the completion screen, or remove the pacman.onboarding.v1 key from the browser's local storage for the onboarding page.

pacman claude install -d . -w .personal-assistant
pacman codex install -d . -w .personal-assistant

This writes:

• CLAUDE.md for Claude Code
• AGENTS.md for Codex
• shared Pac-Man skills under ~/.claude/skills/ and ~/.codex/skills/

pacman mcp claude install -w .personal-assistant
pacman mcp codex install -w .personal-assistant

Restart Claude Code or Codex after MCP registration.

claude mcp add -s user --env=PA_WORKSPACE=$HOME/.personal-assistant pacman -- npx -y pacman mcp serve
codex mcp add pacman --env PA_WORKSPACE=$HOME/.personal-assistant -- npx -y pacman mcp serve

pacman daemon -d .personal-assistant

Run the background sync to ingest enabled integrations and rebuild indexes.

pacman slack listen -d .personal-assistant

Use this when you want Slack replies grounded in saved project context.

Game Modes

| Mode | What it unlocks | | --- | --- | | pacman init | Launch onboarding and create the workspace | | pacman claude install | Add Claude Code project guidance | | pacman codex install | Add Codex project guidance | | pacman mcp claude install | Register the MCP server with Claude Code | | pacman mcp codex install | Register the MCP server with Codex | | pacman daemon | Run scheduled sync and indexing | | pacman slack listen | Start Slack auto-reply handling |

Player Guide

After install:

pacman claude install -d . -w .personal-assistant
pacman mcp claude install -w .personal-assistant

Then restart Claude Code and use Pac-Man guidance plus MCP-backed context reads and updates.

After install:

pacman codex install -d . -w .personal-assistant
pacman mcp codex install -w .personal-assistant

Then restart Codex and ask it to load, search, read, or update project context through Pac-Man MCP tools.

pacman slack listen -d .personal-assistant

Slack replies are additive. They use the same saved workspace and do not replace MCP-based context access in Claude Code or Codex.

High Score Traits

• Privacy first: no mandatory hosted project database
• Inspectable storage: Markdown and JSON live in your workspace
• Shared memory: Claude Code, Codex, and Slack use the same context base
• Grounded retrieval: canonical context, derived summaries, and raw evidence stay connected

Full Map

• Repository and full docs: https://github.com/mukulaggarwal/personal-assistant-with-context