Install
Not self-service yet — ask for an invite.
An organization gets MyStatus set up by emailing support@my-status.app, and its admin signs in at /login as mystatus-admin@<your domain> once the org is set up.
The install kit
- Let Claude post your updates →The skill that turns Claude into your own status reporter, plus the git discipline it follows while building this one.
- Set it up in Claude Code →Say one sentence to Claude Code in a client's project and it walks you through the rest: one key per client, and the key in no file.
- We run on this →The reference install: every way MyStatus is used to run MyStatus. Compare a customer's setup against it.
- 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.
- Read any task as markdown or JSON →Every task serves itself three ways at one address: the page, markdown, JSON — ask with an Accept header, a ?format= parameter, or the path form /task.md and /task.json. The n00b booth is the orientation page a first-time reader gets sent to, and it explains the formats, the read-only rule, and what we promise about the shape.
- 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.
- Cost breakdown of 3 deliverables →Three shipped features — two web, one Android — priced in person hours and in tokens, each figure linked to the entry it was measured from.