Statusline pack reads PAI version from invalid settings.json field

[jmatthewpryor]

Problem

The statusline pack (Packs/pai-statusline/src/statusline-command.sh) attempts to read the PAI version from settings.json at .pai.version:

# Line 93-95
PAI_VERSION=$(jq -r '.pai.version // "—"' "$SETTINGS_FILE" 2>/dev/null)
PAI_VERSION="${PAI_VERSION:-—}"

However, Claude Code's settings.json schema does not allow arbitrary fields like pai. Adding this field causes a validation error:

Settings validation failed:
- : Unrecognized field: pai

As a result, the statusline always shows PAI: v— instead of the actual version.

Suggested Fix

The script already sources ~/.claude/.env on line 42:

[ -f "$PAI_DIR/.env" ] && source "$PAI_DIR/.env"

Change the version retrieval to read from the environment variable (with fallback):

# Get PAI version from environment (set in .env) or default
PAI_VERSION="${PAI_VERSION:-2.3}"

And document that users should add PAI_VERSION=2.3 to their ~/.claude/.env.

Affected Files

• Packs/pai-statusline/src/statusline-command.sh (lines 93-95)
• Releases/v2.3/.claude/statusline-command.sh (same location)

Environment

• Claude Code version: 1.0.33
• PAI version: 2.3
• macOS Darwin 24.6.0

[pybe]

I investigated this issue and found the root cause is simpler than initially described.

Root Cause Analysis

The statusline script reads from the wrong path in settings.json:

# Line 94 in statusline-command.sh
PAI_VERSION=$(jq -r '.pai.version // "2.0"' "$SETTINGS_FILE")

However, install.ts (line 920) writes the version to a different location:

{
  "paiVersion": "2.3",    // ← Version is here (root level)
  "pai": {
    "repoUrl": "..."      // ← No version inside this object
  }
}

The jq query .pai.version looks for settings.pai.version, but the actual value is at settings.paiVersion.

Verification

# Current query returns fallback (wrong)
$ jq -r '.pai.version // "2.0"' ~/.claude/settings.json
2.0

# Corrected query returns actual version (correct)
$ jq -r '.paiVersion // "2.0"' ~/.claude/settings.json
2.3

Fix

Simply change the jq path from .pai.version to .paiVersion on line 94.

I've submitted PR #461 with this fix applied to all three copies of the script.

This is a simpler solution than using environment variables since the value already exists in settings.json—it was just being read from the wrong path.

[danielmiessler]

Thanks for reporting this! We've been doing a major restructuring of PAI's core systems, including a complete redesign of the hook architecture (consolidated from 22 to ~19 hooks), a rewritten Algorithm (now v0.5.1 with PRD-based verification), removal of the observability system, and numerous path/configuration fixes.

This specific issue is addressed by those changes. We're targeting a v3.0 release soon that will include all of this. We appreciate your patience and your help in identifying these issues — it directly informed our redesign work. Stay tuned!