HN user

fotoflo

57 karma

Hi, I'm Alex — builder & investor, 25+ yrs across Asia. PM at Renren.com (NYSE IPO) → EIR at 500 Startups & Accelerating Asia → skin in ~50 startups.

Now: AI workshops/advisory (https://aimhuge.com) and Zeph.vc (https://zeph.vc), a new energy seed fund focused on Bangladesh with optionality across Southeast Asia. On the side: Plain Dharma (https://plaindharma.com) — the Buddha's core teachings in plain modern English, as a book, audiobook, and app.

Obsessed with climate startups that actually make money — hundreds of ideas at https://zeph.vc/idea-bank. Email me anything: fotoflo@gmail.com, or pitch our partners at pitch@zeph.vc

Posts9
Comments17
View on HN

I kept getting burned by rate limits in Claude Code. I'd be deep in something and just hit auto compaction or start to get near the end of my context window without noticing. Then I read about Claude's status line tooling... so I made this. Hope others find it useful.

The first line shows my context, token usage, lines of code change, and importantly how much of my 5hr and weekly budget is left and when it resets, and goes green to red as I burn it down.

The lines added/removed counter is the one I didn't expect to like. it's a quick "did I actually do anything this session" check, and honestly the days where I delete more than I add are usually the good ones.

Script and install are in the post if you want to steal it, or just paste the url into Claude Code and tell it to set it up. would be curious what other people put on theirs, theres way more in that json than I'm using.

Thank you

I couldn't find "continuosly" in the dom - where is it?

"Continuous Monitoring & Alerts for Downtime and Page Speed. Share Notes, Discuss Changes, and More."

best → easiest? simplest? most straightforward?

I always found that when i was working in any type of data analysis, and there was an anomaly, i would figure out what was up, and then... a few days later forget. So having notes on charts and whatnot and being able to share with colleagues is the collaborative part. Especially around outages and slow downs, (or speed ups) we want to know why.

It would probably need a good way to get input: a usb keyboard or something? But if it's an iPad teddy bear, maybe you're biting off more then you can chew -- teach them to read before they can code?