Developers
Two ways in: build something on MyStatus, or watch us build MyStatus. Everything about how it gets made — the work, the cost, the mistakes — is behind one of these doors.
Tools for building with MyStatus
- Let Claude post your updates →Two skills for Claude: one turns it into your own status reporter, the other is the git discipline it follows while building this.
- Blueprints for builders →Make your own task machine-readable: the blueprint pattern, what every task already gives a machine, and the live tasks already running it.
- Sample code to play with →A short worked reader that pages through a real task, parses its rows, and skips the ones that aren't data.
- Measure your own sessions →What a Claude Code or Cowork session cost, off its own transcript: one file, no dependencies. Real turns after the log's duplicates come out, what your rules and tools cost on every turn, and the bill at list rates.
- Find out when a session stops being worth continuing →Every turn re-reads the conversation so far, so a late turn costs more than an early one. This draws the curve from every transcript on your machine — the same one on our stats page, with your numbers instead of ours.
Watch us Build MyStatus
- The Glass Factory →Start here. What we're testing, and the live build streams while it happens — you can watch the work go by as it goes by.
- Field notes →The lessons, curated: the funny parts, the wrong turns, and what we learned, without the nerdery.
- Stats →The receipts. What has shipped, what it cost to build, what it costs to run, and a sign telling you whether anybody is coding right now.
- What a feature costs →Three shipped features — two web, one Android — priced in person hours and in tokens, each figure linked to the entry it was measured from.