[Feature Request] Expose advisor enabled/disabled state in statusline JSON
There is no way to tell at the beginning of a session if advisor is enabled or not.
---
⏺ Let me check the advisor skill/settings to understand what's available.
⏺ Bash(cat /Users/brock/.claude/plugins/installed_plugins.json 2>/dev/null | python3 -m json.tool
2>/dev/null | grep -A5 -i 'advisor')
⎿ No matches found
⏺ Bash(find /Users/brock/.claude -name '.json' -o -name '.md' | xargs grep -l 'advisor'
⏺ Bash(find /Users/brock/.claude /Users/Shared/nonpunctual/.claude -name 'settings*.json'
⏺ The /advisor toggle state isn't surfaced anywhere in config files or the session context - it's
entirely runtime state managed by Claude Code's process. There's no persistent file that records
enabled/disabled status between sessions.
The only way to know the state at session start is to run /advisor (which toggles it) and read the
output - but that changes the state. It's a known UX gap: the command is a toggle with no
read-only status query.
If this is something you want consistently on or off, you could hook it into session start via a
SessionStart hook in settings.json, but that still requires knowing the initial state to toggle
correctly.
❯ All I want is for it to show on the status line
⏺ Let me check the statusline setup to understand what's configurable there.
⏺ Skill(statusline-setup)
⏺ The statusline script receives JSON input from Claude Code. I need to check what fields are
available in that JSON - specifically whether advisor state is included.
⏺ Advisor state is not in the statusline JSON schema - it's not one of the available data fields.
The statusline script only receives the fields documented in that table, and advisor
enabled/disabled is not among them.
There's no supported way to surface it in the status line currently. You'd need to file a feature
request for Anthropic to expose it in the statusline JSON payload.
Environment Info
- Platform: darwin
- Terminal: Apple_Terminal
- Version: 2.1.141
- Feedback ID: 73e314ec-e8a3-4030-b182-b53f55e014cf
---
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗