show some user info in the footer

[zhubert]

I think it would be useful to show some user info somewhere on the screen (footer? header?) that indicates which Claude account is being used.

People often have work and personal Claude accounts, let's help them keep them separate.

[zhubert]

Implementation Plan: Show Claude Account Info in Footer

Summary

Run claude auth status at startup to get account information (email, org name, auth method) and display it in the footer. This helps users distinguish between work and personal Claude accounts.

The user feedback confirms we can use claude auth status, which outputs JSON like:

{
  "loggedIn": true,
  "authMethod": "claude.ai",
  "email": "zack@planningcenter.com",
  "orgName": "Planning Center",
  ...
}

Approach

1. Create a new internal/claudeauth/ package to fetch and parse auth status
2. Add a AuthStatusFetchedMsg to the app message system
3. Fetch auth status in Init() as a background command
4. Store the result in the model and display it in the footer (right-aligned, alongside keybindings)

Key Files to Modify

• NEW internal/claudeauth/auth.go — AuthStatus struct + GetAuthStatus() function that runs claude auth status and parses JSON
• NEW internal/claudeauth/auth_test.go — Tests for JSON parsing and error handling
• internal/app/app.go — Add claudeAuthInfo field to Model, dispatch fetch in Init()
• internal/app/msg_handlers.go (or app.go) — Handle AuthStatusFetchedMsg, store result
• internal/ui/footer.go — Add userInfo string field + SetUserInfo() method, render it in View()
• internal/ui/footer_test.go — Tests for user info display

Step-by-Step Implementation

Step 1: internal/claudeauth/auth.go

type AuthStatus struct {
    LoggedIn   bool   `json:"loggedIn"`
    AuthMethod string `json:"authMethod"`
    Email      string `json:"email"`
    OrgName    string `json:"orgName"`
}

func GetAuthStatus() (*AuthStatus, error) {
    cmd := exec.Command("claude", "auth", "status")
    output, err := cmd.Output()
    // parse JSON...
}

Step 2: Add message type in app.go

type AuthStatusFetchedMsg struct {
    Status *claudeauth.AuthStatus
    Error  error
}

Step 3: Dispatch in Init()

func (m *Model) Init() tea.Cmd {
    return tea.Batch(
        func() tea.Msg { return StartupModalMsg{} },
        PRPollTick(),
        func() tea.Msg {
            status, err := claudeauth.GetAuthStatus()
            return AuthStatusFetchedMsg{Status: status, Error: err}
        },
    )
}

Step 4: Handle message in Update()
When AuthStatusFetchedMsg arrives, store auth info and pass display string to footer:

• If logged in with email: show email (or email @ orgName if org is present)
• If logged in without email: show auth method
• If not logged in or error: show nothing (fail silently)

Step 5: Footer display
Add userInfo string field to Footer. In View(), when userInfo is non-empty, append it right-aligned. Since the footer uses MaxHeight(1), the user info will appear at the right end of the keybindings line, styled in a muted/dimmed color to not compete with keybindings.

Example footer display:

n: new session  |  q: quit  |  ?: help           zack@planningcenter.com

The user info is rendered on the right side using padding calculations (similar to how the header right-aligns content).

Potential Risks / Edge Cases

• claude auth status may not output JSON in all versions — wrap parsing in error handling, fail silently if parsing fails
• Footer width overflow — if both keybindings and email are long, truncate email with ellipsis. Use lipgloss.Width() for accurate width calculation
• Not logged in — show nothing, don't error
• Corporate SSO / API key auth — may not have an email; fall back to authMethod or show nothing
• Performance — claude auth status is a subprocess; running it in Init() as a tea.Cmd (background goroutine) means it won't block the UI

Test Coverage

• Unit tests for JSON parsing (happy path, missing fields, malformed JSON, not logged in)
• Unit tests for footer SetUserInfo() and View() with user info
• Test that user info renders correctly in footer view
• Test that flash messages still take priority over user info display

[zhubert]

The plan above is ready for your review. Reply with your feedback to request changes, or reply with an approval (e.g. "LGTM", "looks good", "approved") to proceed.

[zhubert]

Can't you get the info by running claude auth status

erg main ❯ claude auth status
{
"loggedIn": true,
"authMethod": "claude.ai",
"apiProvider": "firstParty",
"apiKeySource": "/login managed key",
"email": "blah@blah.com",
"orgId": "29dsfjas9s",
"orgName": "Planning Center",
"subscriptionType": null
}

[zhubert]

approved

[zhubert]

A pull request is ready for your review: #327

Please review and approve it to proceed.