claude-code - 💡(How to fix) Fix [DOCS] Status line docs omit GitHub repository and pull request JSON fields [1 comments, 2 participants]

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/statusline

Section/Topic

The "Available data" reference and "Full JSON schema" for status line input

Current Documentation

The page presents the status line payload reference as a complete list of available fields:

Claude Code sends the following JSON fields to your script via stdin:

| model.id, model.display_name | Current model identifier and display name | | cwd, workspace.current_dir | Current working directory. Both fields contain the same value; workspace.current_dir is preferred for consistency with workspace.project_dir. | | workspace.project_dir | Directory where Claude Code was launched, which may differ from cwd if the working directory changes during a session | | workspace.added_dirs | Additional directories added via /add-dir or --add-dir. Empty array if none have been added | | workspace.git_worktree | Git worktree name when the current directory is inside a linked worktree created with git worktree add. Absent in the main working tree. Populated for any git worktree, unlike worktree.* which applies only to --worktree sessions | ... | worktree.original_branch | Git branch checked out before entering the worktree. Absent for hook-based worktrees |

The example schema also shows workspace with only these fields:

"workspace": { "current_dir": "/current/working/directory", "project_dir": "/original/project/directory", "added_dirs": [], "git_worktree": "feature-xyz" }

What's Wrong or Missing?

This reference is outdated for v2.1.145.

The page lists the status line JSON fields and shows a full example payload, but it does not document the GitHub repository and pull request information now included when Claude Code detects that context.

Because those fields are missing from both the "Available data" table and the schema example, status line script authors cannot discover:

• the exact field names
• where the repo / PR data is nested
• when those fields are present versus absent

Suggested Improvement

Update the status line page to document the new GitHub repository and pull request metadata alongside the existing fields.

At minimum:

1. Add the new fields to the "Available data" table with their exact names, types, and presence conditions.
2. Update the full JSON schema example so it includes the repo / PR structure when detected.
3. Add a small example status line snippet that conditionally renders repository and pull request context when those fields are present.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

Total scope: 1 page affected

Version context: This gap affects the v2.1.145 status line JSON update.