This is what we are working on, in order. It changes when you tell us something matters more: vote on ideas in Discussions or send feedback. There are no dates here on purpose; a date we miss is worse than none.
Now#
- plottypus 1.1. A first-run screen that says what plottypus reads and that it sends nothing. An optional update check you switch on yourself, and
plottypus updateto update by hand.plottypus feedbackto report a problem from the app. A session timeline, alerts in the dashboard, replay, a status line for tmux, and grouped processes. - Feedback. This site’s feedback form, GitHub issue forms, and chip reports from
plottypus doctor.
Next#
- Fixes from launch feedback. Whatever breaks on Macs other than the one M5 Pro it was measured on.
- More chips measured. CPU watts are checked against IOReport on an M5 Pro only. Reports from other chips decide what gets verified next.
- An open-source sensor reader. The code that reads CPU power correctly on macOS 27, as a small MIT-licensed Rust crate other monitors can use.
- Signed update manifests. The update check will verify an Ed25519 signature, not only the checksum.
Later#
- Pro on sale. History, reports, recording, exporters, the background agent, the theme pack, the bench and fleet already exist behind a licence; they go on sale once the free version has earned trust. Email to hear first.
- Notarized builds, so a browser download opens without a Gatekeeper prompt.
Not planned#
- Usage tracking. plottypus does not count what you do. If that ever changes, it will be off unless you turn it on, and it will be announced here first. The only request plottypus makes is the update check, and only if you turn it on.
- Intel Macs. plottypus reads Apple Silicon’s own sensors; there is nothing equivalent to read on Intel.