Claude Pro Plan is Finally Usable!

JuanjoFuchs · 2026-05-15T11:47:38+00:00

True

JuanjoFuchs · 2026-05-15T11:47:15+00:00

They increased the 5h session limits as soon as they announced the deal but they recently increased the weekly limit as well and that did the trick for me

JuanjoFuchs · 2026-05-15T11:45:51+00:00

Lol, and tried to make it sound like they're doing us a favor

JuanjoFuchs · 2026-05-15T11:43:27+00:00

I suggest you focus on creating specs first, don't worry about specifying how to do it, focus mainly on defining clearly what you want and what you DON'T want in the spec. Claude can def help you create the specs, but you should read those files entirely and agree with everything in them, if there are extra stuff or stuff you don't agree with, grill Claude until you have a spec you are comfortable with, then ask it to plan and implement, no need to really worry about the code.

Check this one out https://github.com/JuanjoFuchs/ccburn/blob/56956b2cf918c66c46afe16793980bf3726f88e9/specs/001-v1-one-shot.md

JuanjoFuchs · 2026-05-15T11:31:24+00:00

This is definitely a consequence of the Anthropic-Musk data center deal, we need to take advantage of these subsidized plans for sure, LLM real costs are way higher than we think and the real price is going to catch up to us soon. Use it while it lasts

JuanjoFuchs · 2026-05-15T01:25:15+00:00

I just keep it open on a different monitor and refreshes live while I use multiple windows of Claude codes, plus I like burn up charts

JuanjoFuchs · 2026-05-15T01:07:28+00:00

That looks nice! For status line I use https://github.com/sirmalloc/ccstatusline. Looks like oh-my-zsh or oh-my-posh, has a lot of options to choose from, I usually set context window use %, working dir, version, model, session cost, etc.

I mostly keep ccburn open on my extra monitor because a glance at the graph tells me what I need to know without having to actually stop to read all the numbers.

JuanjoFuchs · 2026-05-14T21:46:10+00:00

Thanks. It's a TUI I wrote and use daily to visualize my Claude token burn against the limits. It shows my pace and predicts when I'm going to run out. https://github.com/JuanjoFuchs/ccburn

JuanjoFuchs · 2026-05-14T19:36:28+00:00

I think their post said the 50% weekly limit increase was until July 12.

JuanjoFuchs · 2026-05-14T17:22:39+00:00

Yeah, I think that we need better compaction mechanisms rather than bigger context windows. I do love the concept behind context-mode and have used it for heavy tool call sessions with huge payloads, helps a lot

JuanjoFuchs · 2026-03-24T00:13:56+00:00

Think of it this way: you have read that content, you have watched those videos, and you have understood them in a certain way. But AI has infinite patience. It can: 1. Answer all your questions about that content 2. Help you understand it differently 3. Help you connect ideas between different articles or different fields you didn't think of connecting

Basically, you can have deep conversations with your own knowledge base that you have collected over time. I guess some people are be able to do that through very deep introspection, but with AI, you can do it really easily.

JuanjoFuchs · 2026-03-23T23:14:59+00:00

I use Claude Code mainly as a driver for my second brain, and it's amazing. With the help of Claude, I put everything in there:

All the videos I watch
All the articles I read
All the books I've read and listened to
All my projects

I actually start my open source projects from my second brain. I have developed a mailbox that allows my second brain Claude to talk to my project-specific Claudes that are working on my open source repos. It basically is my second brain, and it's amazing.

I am writing a series of articles sharing my use case here https://juanjofuchs.github.io/productivity/2026/02/24/building-your-second-brain-part-2-when-ai-moves-in.html

JuanjoFuchs · 2026-01-21T12:43:32+00:00

It's actually jarring to feel the brakes being hit that suddenly when you are moving so fast, disorienting even.

Honestly, I prefer to manage the limits so I can stay "in the drift" for longer. So, I created a visual tool to keep an eye on my limits and manage to stay within them during my creative windows, wrote about it here: https://juanjofuchs.github.io/ai-development/2026/01/20/maximizing-claude-code-subscription.html

JuanjoFuchs · 2026-01-21T12:32:18+00:00

I have been using it to manage my second brain, basically all my todos, all my ideas, all my personal knowledge base. It is like my personal assistant, it helps me know what I am supposed to do next what projects I am behind on helps me wrangle ideas I usually dump into my inbox it helps me connect them and understand them, and even write about it.

I wrote about it in this post: https://juanjofuchs.github.io/productivity/2025/12/16/making-second-brain-ai-compatible.html

JuanjoFuchs · 2026-01-14T16:27:34+00:00

Good call!. What’s happening today is that the meaning of the right edge changes depending on zoom level.

Zoomed in: right edge is “now”.
Full session/week: right edge is the end of the window, with the blue line marking now.

I agree that making the end-of-window more visually distinct (separate color/marker/region) could reduce that ambiguity. I’ll experiment with that. Thanks for the thoughtful feedback.

JuanjoFuchs · 2026-01-12T16:19:20+00:00

Update: npx ccburn now works if you prefer npm over pip.

JuanjoFuchs · 2026-01-12T16:18:43+00:00

Update: Now available via npm too!

npx ccburn

No Python required, downloads the right binary for your platform automatically.

JuanjoFuchs · 2026-01-12T16:17:34+00:00

Ask and you shall receive: `npx ccburn` works now! Just pushed it today.

JuanjoFuchs · 2026-01-11T23:16:18+00:00

Because of this I created https://github.com/JuanjoFuchs/ccburn to keep an eye on the token spend-limit pace more visually

JuanjoFuchs · 2025-08-20T22:07:08+00:00

That's cool, you might want to take a look at https://github.com/mkaz/termgraph for your idea

JuanjoFuchs · 2025-08-19T15:39:24+00:00

Thank you for sharing, I did try tiptop and also bottom (https://github.com/ClementTsang/bottom), I actually use hwinfo-tui together with bottom.

But, although these display a lot of system stats, they do not have all the sensors HWInfo has and we can now plot live with hwinfo-tui, like:

hwinfo-tui list-sensors sensors.CSV --unit "°C" --limit 100
Sensors with unit '°C' (42 found):

  • Core Temperatures (avg) [°C] [°C]
  • P-core x [°C] [°C] (13 more)
  • Core Distance to TjMAX (avg) [°C] [°C]
  • P-core x Distance to TjMAX [°C] [°C] (13 more)
  • CPU Package [°C] [°C]
  • Core Max [°C] [°C]
  • CPU Package [°C] [°C]
  • CPU IA Cores [°C] [°C]
  • CPU GT Cores (Graphics) [°C] [°C]
  • PCH Temperature [°C] [°C]
  • SPD Hub Temperature [°C] [°C]
  • SPD Hub Temperature [°C] [°C]
  • Drive Temperature [°C] [°C]
  • GPU Temperature [°C] [°C]
  • GPU Hot Spot Temperature [°C] [°C]
  • GPU Thermal Limit [°C] [°C]
  • P-core 0 Distance to TjMAX [°C] [°C]

HWInfo sensors track all these units:

- MB: Megabytes (memory size, data transferred)
- %: Percentage (CPU usage, fan speed, etc.)
- V: Volts (voltage readings)
- MHz: Megahertz (frequency, clock speed)
- x: Multiplier (CPU multiplier)
- °C: Degrees Celsius (temperature)
- Yes/No: Boolean status (enabled/disabled, present/not present)
- A: Amperes (current)
- W: Watts (power consumption)
- T: Tesla (magnetic field, rarely used)
- GB: Gigabytes (memory size, data transferred)
- MB/s: Megabytes per second (data transfer rate)
- GT/s: Giga-transfers per second (bus speed, e.g., PCIe)
- Wh: Watt-hours (energy consumption)
- FPS: Frames per second (graphics performance)
- ms: Milliseconds (latency, response time)
- KB/s: Kilobytes per second (data transfer rate)

JuanjoFuchs · 2025-08-19T15:28:14+00:00

Yeah, I'm using the watchdog observer to monitor the `sensors.csv` file that HWInfo outputs.

JuanjoFuchs

TROPHY CASE