[FEATURE]

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

I'll search for Anthropic's feedback portal or submission form.Perfect! I found the Claude Code GitHub issues page. Here's the updated information:

Best place to submit your feature request:

https://github.com/anthropics/claude-code/issues

This is the official Claude Code repository where the team actively tracks feature requests and bugs. I can see they're actively managing issues (there were new ones posted just today).

---

Updated draft for GitHub:

When you go to create a new issue, select "Feature Request" and you can use this:

Title: Improve OAuth token expiration UX in Claude Code CLI

Problem Statement

The current OAuth token expiration experience in Claude Code creates unnecessary friction for developers:

Current behavior:

• Tokens expire relatively quickly (appears to be days/weeks)
• When expired, user receives cryptic API 401 error: {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired..."}}
• User must manually run claude login in their system terminal (not in Claude Code's CLI interface)
• Full OAuth flow required each time

Requested improvements:

1. One-click re-authentication: When token expires, show a clickable button/link in the Claude Code interface that automatically launches the OAuth flow instead of requiring manual command entry in a separate terminal

1. Automatic token refresh: Implement refresh token mechanism to silently extend sessions without user intervention

1. Longer token lifetime for CLI usage: For a local development tool on a trusted machine, the current expiration window feels unnecessarily short

1. Better error messaging: Instead of raw API errors, show user-friendly messages like "Your session has expired. [Click here to log in again]"

Rationale:

Developers use Claude Code as a daily tool on their own machines. The current re-auth friction interrupts workflow and feels overly cautious for local CLI usage.

Proposed Solution

I'll search for Anthropic's feedback portal or submission form.Perfect! I found the Claude Code GitHub issues page. Here's the updated information:

Best place to submit your feature request:

https://github.com/anthropics/claude-code/issues

This is the official Claude Code repository where the team actively tracks feature requests and bugs. I can see they're actively managing issues (there were new ones posted just today).

---

Updated draft for GitHub:

When you go to create a new issue, select "Feature Request" and you can use this:

Title: Improve OAuth token expiration UX in Claude Code CLI

Problem Statement

The current OAuth token expiration experience in Claude Code creates unnecessary friction for developers:

Current behavior:

• Tokens expire relatively quickly (appears to be days/weeks)
• When expired, user receives cryptic API 401 error: {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired..."}}
• User must manually run claude login in their system terminal (not in Claude Code's CLI interface)
• Full OAuth flow required each time

Requested improvements:

1. One-click re-authentication: When token expires, show a clickable button/link in the Claude Code interface that automatically launches the OAuth flow instead of requiring manual command entry in a separate terminal

1. Automatic token refresh: Implement refresh token mechanism to silently extend sessions without user intervention

1. Longer token lifetime for CLI usage: For a local development tool on a trusted machine, the current expiration window feels unnecessarily short

1. Better error messaging: Instead of raw API errors, show user-friendly messages like "Your session has expired. [Click here to log in again]"

Rationale:

Developers use Claude Code as a daily tool on their own machines. The current re-auth friction interrupts workflow and feels overly cautious for local CLI usage.

Alternative Solutions

I'll search for Anthropic's feedback portal or submission form.Perfect! I found the Claude Code GitHub issues page. Here's the updated information:

Best place to submit your feature request:

https://github.com/anthropics/claude-code/issues

This is the official Claude Code repository where the team actively tracks feature requests and bugs. I can see they're actively managing issues (there were new ones posted just today).

---

Updated draft for GitHub:

When you go to create a new issue, select "Feature Request" and you can use this:

Title: Improve OAuth token expiration UX in Claude Code CLI

Problem Statement

The current OAuth token expiration experience in Claude Code creates unnecessary friction for developers:

Current behavior:

• Tokens expire relatively quickly (appears to be days/weeks)
• When expired, user receives cryptic API 401 error: {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired..."}}
• User must manually run claude login in their system terminal (not in Claude Code's CLI interface)
• Full OAuth flow required each time

Requested improvements:

1. One-click re-authentication: When token expires, show a clickable button/link in the Claude Code interface that automatically launches the OAuth flow instead of requiring manual command entry in a separate terminal

1. Automatic token refresh: Implement refresh token mechanism to silently extend sessions without user intervention

1. Longer token lifetime for CLI usage: For a local development tool on a trusted machine, the current expiration window feels unnecessarily short

1. Better error messaging: Instead of raw API errors, show user-friendly messages like "Your session has expired. [Click here to log in again]"

Rationale:

Developers use Claude Code as a daily tool on their own machines. The current re-auth friction interrupts workflow and feels overly cautious for local CLI usage.

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

I'll search for Anthropic's feedback portal or submission form.Perfect! I found the Claude Code GitHub issues page. Here's the updated information:

Best place to submit your feature request:

https://github.com/anthropics/claude-code/issues

This is the official Claude Code repository where the team actively tracks feature requests and bugs. I can see they're actively managing issues (there were new ones posted just today).

---

Updated draft for GitHub:

When you go to create a new issue, select "Feature Request" and you can use this:

Title: Improve OAuth token expiration UX in Claude Code CLI

Problem Statement

The current OAuth token expiration experience in Claude Code creates unnecessary friction for developers:

Current behavior:

• Tokens expire relatively quickly (appears to be days/weeks)
• When expired, user receives cryptic API 401 error: {"type":"error","error":{"type":"authentication_error","message":"OAuth token has expired..."}}
• User must manually run claude login in their system terminal (not in Claude Code's CLI interface)
• Full OAuth flow required each time

Requested improvements:

1. One-click re-authentication: When token expires, show a clickable button/link in the Claude Code interface that automatically launches the OAuth flow instead of requiring manual command entry in a separate terminal

1. Automatic token refresh: Implement refresh token mechanism to silently extend sessions without user intervention

1. Longer token lifetime for CLI usage: For a local development tool on a trusted machine, the current expiration window feels unnecessarily short

1. Better error messaging: Instead of raw API errors, show user-friendly messages like "Your session has expired. [Click here to log in again]"

Rationale:

Developers use Claude Code as a daily tool on their own machines. The current re-auth friction interrupts workflow and feels overly cautious for local CLI usage.

Additional Context

in the above, i've posted identical copies of what claude's wrote for me. i am too tired at the moment to carefully edit, sorry ;-S

oh, and thank you for the time you may invest in pursuit of this. unfixed, it's really quite an impressive amount of friction. okay, it's for security. hmm, what's that all about? probably written somewhere. sigh. very bewildering compared to "wow, this is a great tool. it helps and helps and helps" until the expiration.