What is Real Problem AI?

Real Problem AI is a curated directory of 100 real problems worth building an AI startup around. Each problem is scored honestly on severity, AI feasibility, market signal, and competition gap. We're for builders looking for what to build, not for ethics debates about AI.

What is the difference between Real Problem AI and AI ethics or AI risks indexes?

Real Problem AI catalogues problems AI can solve — productive, commercial opportunities for builders. AI ethics indexes catalogue problems with AI itself (bias, environmental cost, copyright, consciousness). Different intent, different audience: founders and indie hackers vs researchers and policy folks.

What should I build with AI in 2026?

Look for problems with high severity (it costs people hours, sleep, or revenue every week), high AI feasibility (LLMs, vision or voice are great at this today), strong market signal (Reddit threads + willingness to pay), and a clear competition gap (incumbents miss the same obvious thing). Real Problem AI scores 100 such problems for you on those four axes.

Where do Real Problem AI's startup ideas come from?

From three sources, scanned each cycle: 1) Reddit threads where people describe a real friction in their own words, 2) podcasts and talks of founders young builders trust (Nikhil Kamath, Aman Gupta, Ankur Warikoo, Raj Shamani, Andrej Karpathy, Greg Isenberg), and 3) a continuous 1,000+ source scan covering forums, app store reviews, regulator filings, and field interviews.

Is Real Problem AI free?

Yes. Browsing every problem, opening every score breakdown, raising your hand on a co-founder match, and the founder vault are all free. There is no paywall.

How is each problem scored?

Four axes, each 1-10, weighted: Problem Severity (30%), AI Feasibility (25%), Market Signal (25%), Competition Gap (20%). Weighted average is the Opportunity Score on each card. Only problems clearing 7.0+ make the live list.

Why does Claude Code hide your own plan quota from the terminal you live in?

The statusLine JSON that powers custom terminal HUDs includes context window, cost, and model, but nothing about the 5-hour or weekly plan quota, so users get rate-limited mid-session with zero warning.

Category: AI / Agents · Trend: LLM · Opportunity score: 8.0 / 10

What is the “Why does Claude Code hide your own plan quota from the terminal you live in?” problem in 2026?

Who has this problem?

Claude Code power users running long agentic sessions on Pro/Max plans.

Recorded source context

Dataset source note: The result: users get rate-limited mid-session with no warning. The only way to check quota is to break flow and open a browser or run /usage manually (which can't be called programmatically or from hooks/scripts).

This note may summarize the referenced material rather than quote it verbatim. Source label: anthropics/claude-code GitHub issue #27915, 23 Feb 2026, filed as the most-duplicated feature request on the repo. (reference).

Existing players in this space

/usage command: Manual, breaks flow, cannot be called from hooks or scripts.
claude.ai Settings > Usage: Accurate but requires leaving the terminal and a browser session.
Community statusline scripts: Reverse-engineer an undocumented OAuth endpoint to fake the missing data.

What existing players are missing

A first-party or drop-in statusline widget that surfaces live 5-hour and weekly quota percentage directly in the terminal, sourced from the same data Anthropic already shows on the web dashboard.

How Real Problem AI scores this opportunity

Aggregate score: 8.0 / 10. Four-axis rubric:

Problem severity: 7 / 10
AI feasibility today: 9 / 10
Market signal: 9 / 10
Competition gap: 7 / 10

How to build a solution: stack hints

Claude Code statusLine hook
Anthropic usage API polling
Terminal HUD renderer
Local caching to avoid rate-limiting the check itself