pi-anthropic-auth: Skill for Claude Code

Pi CLI Repro

Use When

• You need to reproduce a bug through the real pi executable.
• Extension logic must be validated in the live CLI path rather than only unit tests.
• Anthropic OAuth behavior differs between tests and the installed CLI.
• You need a short feedback loop for prompt shaping or request-shaping changes.

Core Workflow

1. Reproduce with explicit extension loading

Use the live CLI with this extension file loaded directly:

pi \
  --model anthropic/claude-haiku-4-5 \
  --no-session \
  --tools read,grep,find,ls \
  -e /Users/chris/development/pi/pi-anthropic-auth/src/index.ts \
  -p "How many lines are in @AGENTS.md ?"

Why this shape:

• --no-session avoids session carryover noise
• --tools read,grep,find,ls keeps repros narrow and read-only
• -e .../src/index.ts guarantees the local extension is actually loaded
• -p gives a fast non-interactive cycle
• anthropic/claude-haiku-4-5 is the preferred fast repro model unless you are chasing a model-specific issue

An extension slash command runs headlessly too: pi -ne -e <path>/src/index.ts -p "/anthropic-auth:status" prints whatever the handler sends to console.log (Refs #80).

2. Check version alignment first

Before trusting a repro, confirm the installed CLI version:

pi --version

If the live CLI version does not match the Pi libraries this repo targets, treat that as a possible source of mismatch.

Useful Experiments

Compare default prompt vs minimal custom prompt

If Anthropic OAuth fails, test whether the default Pi prompt is the trigger:

PI_ANTHROPIC_AUTH_DEBUG=tool-use pi ... -p "hi"

then compare with:

pi ... --system-prompt "You are a coding assistant." -p "hi"

If the minimal prompt succeeds while the default prompt fails, suspect prompt fingerprinting.

Remove project context from the experiment

To separate prompt-template issues from AGENTS.md or repo guidance:

pi ... --no-context-files -p "hi"