CLI

Pajama CLI

The pajama CLI is the fastest way to write and retrieve project memories from your terminal.

• Install once, then auto sync your memory everywhere.
• Use Organization scope for shared team memory, and Personal scope for private notes.
• Upload large files to R2 and link them to memories for evidence-first debugging.

Install (Recommended)

Install the prebuilt binary via npm:

npm i -g @pajamadot/pajama

Supported (current): win32/x64.

Login (Browser OAuth PKCE)

Interactive login:

pajama login

If your environment cannot auto-open a browser:

pajama login --no-open

The CLI opens the web consent page, you approve, then it redirects back to http://localhost:... and saves the token locally.

Show where the token is stored:

pajama config-path

Use An API Key (Non-Interactive)

For agents and services, you usually want an API key:

1. Go to Settings -> API Keys
2. Create a key in the scope you want (Org shared vs Personal private)
3. Set it in your environment

$env:PAJAMA_TOKEN = "gdm_..."
pajama projects list

You can also pass a token per-command:

pajama --token gdm_... projects list

Configure

Environment variables:

Core Commands

Projects:

pajama projects list
pajama projects create --name "UE5 Shooter Prototype" --engine unreal --description "Goals, constraints"

Memories:

pajama memories list --project-id <project-uuid> --limit 50
pajama memories create --project-id <project-uuid> --category bug --title "Crash on PIE exit" --content "Root cause..." --tags "unreal,crash"
pajama memories search-index --project-id <project-uuid> --q "shader compile crash" --provider memories_fts --memory-mode balanced --limit 20
pajama memories batch-get --ids <memory-id-1>,<memory-id-2>
pajama memories timeline --project-id <project-uuid> --limit 100
pajama memories derive <memory-id> --dry-run
pajama memories derive <memory-id>
pajama memories foresight-active --project-id <project-uuid> --within-days 30 --limit 25

Assets (large files):

# Upload a file (multipart) and get an asset id back
pajama assets upload --project-id <project-uuid> --path "C:\\tmp\\build.zip"

# Download an asset by id
pajama assets download <asset-uuid> --out "C:\\tmp\\build.zip"

Evolve (arena):

pajama evolve policy --project-id <project-uuid>
pajama evolve arena-latest --project-id <project-uuid>
pajama evolve arena-run --project-id <project-uuid>
pajama evolve arena-iterate --project-id <project-uuid> --iterations 300 --time-budget-ms 300000
pajama evolve arena-campaign --max-projects 10 --iterations-per-project 200 --time-budget-ms 600000

# Agent (retrieval-first)
pajama agent status
pajama agent ask --project-id <project-uuid> --query "what changed in rendering perf?"
pajama agent ask --project-id <project-uuid> --query "what changed in rendering perf?" --dry-run --diagnostics
pajama agent ask --project-id <project-uuid> --query "what changed in rendering perf?" --dry-run --diagnostics --no-cache --cache-ttl-ms 15000

Benchmark Retrieval Latency

Use the benchmark helper to compare retrieval profiles and cache behavior against the live API:

./scripts/benchmark-agent-retrieval.ps1 -Token "<gdm_api_key>" -ProjectId "<project-uuid>" -Iterations 12

Common tuning switches:

• -NoCache for cold-path latency.
• -MemoryMode fast|balanced|deep for recall/latency tradeoffs.
• -RetrievalMode auto|memories|hybrid|documents for routing comparisons.
• -CacheTtlMs to tune worker-side retrieval cache TTL per run.

Evidence-First: Link Files To Memories

Create a memory first:

$mem = pajama memories create --project-id <project-uuid> --category build-error --title "Packaging failed" --content "See attached log" --tags "ue,packaging"

Upload the log or artifact and link it to that memory:

pajama assets upload --project-id <project-uuid> --memory-id $mem --path "C:\\tmp\\Saved\\Logs\\MyProject.log"

Verify the link:

pajama assets list --memory-id $mem

Troubleshooting

Install worked but pajama is missing

Rebuild global install scripts:

npm rebuild -g @pajamadot/pajama

OAuth login times out

Give yourself more time to approve in the browser:

$env:PAJAMA_OAUTH_CALLBACK_TIMEOUT_SECS = "1800"
pajama login

Binary download 404

The npm installer downloads from:

https://api-game-dev-memory.pajamadot.com/downloads/pajama/v{version}/{file}

If you are running a dev environment or custom domain, override the prefix:

$env:PAJAMA_DOWNLOAD_BASE_URL = "https://api-game-dev-memory.pajamadot.com/downloads/pajama"
npm i -g @pajamadot/pajama

Agent Skills (Codex / Claude Code)

This repo ships public agent skills in skills/ (for example: skills/pajama-cli). A skill is just a folder with a SKILL.md (and optional scripts/references).

To make a skill "public":

• Keep skills/<name>/ in a public GitHub repo (and make sure it contains no secrets).
• Document a copy/install command into the agent's skill directory.

Full guide: /docs/skills.

Install pajama-cli skill (PowerShell):

$CODEX = if ($env:CODEX_HOME) { $env:CODEX_HOME } else { Join-Path $HOME ".codex" }
$tmp = Join-Path $env:TEMP "gdm-skill"
if (Test-Path $tmp) { Remove-Item -Recurse -Force $tmp }
git clone --depth 1 https://github.com/pajamadot/game-dev-memory.git $tmp
New-Item -ItemType Directory -Force (Join-Path $CODEX "skills\\pajama-cli") | Out-Null
Copy-Item -Recurse -Force (Join-Path $tmp "skills\\pajama-cli\\*") (Join-Path $CODEX "skills\\pajama-cli")

Install pajama-cli skill (macOS/Linux):

CODEX_HOME="${CODEX_HOME:-$HOME/.codex}"
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/pajamadot/game-dev-memory.git "$tmp/gdm"
mkdir -p "$CODEX_HOME/skills/pajama-cli"
cp -R "$tmp/gdm/skills/pajama-cli/"* "$CODEX_HOME/skills/pajama-cli/"

After install, you can tell your agent to use the pajama-cli skill to record memories and attach evidence files (assets) during sessions.