[FEATURE] Token limits make sustained project work impractical on Pro plan

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'm a Pro subscriber using Claude Code to build a complete website (PHP/MySQL, ~20 files, admin panel, full frontend) for a volunteer project, a kennel website for a friend, done on my own time while on long-term sick leave.

The work is going extremely well, the quality of what Claude Code produces is genuinely extraordinary. But the token/context limits are a consistent and frustrating blocker. On a project like this, where continuity matters (the AI needs to remember
architecture decisions, file structure, naming conventions, what was built last session), hitting the limit mid-session means losing context, re-explaining, and sometimes losing momentum on complex tasks entirely.

I'm in Sweden, building something for free for someone who can't afford a web agency. Claude Code is the reason this project is possible at all, but the token ceiling is the one thing that keeps getting in the way.

Proposed Solution

Specific asks:

1. Higher context limits for sustained project work on the Pro plan
2. Consideration for reduced-cost or expanded-access tiers for people on fixed incomes, unemployed, on sick leave, students, or doing volunteer/non-commercial work. This tooling is transformative but the pricing assumes a commercial/professional

context that not everyone is in.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_