Dipstick

DOCS

Docs · dipstick.tools

Documentation

Everything here describes the app as it stands, including the parts that are not finished. If a guide tells you something works, it works today.

10 pages 5 setup guides 7 known issues 0 published releases

  1. 01 How to read a meter Which quantity is the fill and which is the marker, what each colour means, the fifteen percent rule, and what happens on a tie — with three worked readings you can check against the drawing. concepts

02 / 04 · Setup guides

One guide per provider.

Each lists the real prerequisites and the failure modes you will actually hit, with the fix for each. The right-hand column is what that provider needs present on this Mac before a meter can read anything.

  1. 01 Set up Claude Claude Code installed and signed in. Run claude once in a terminal and confirm it answers before enabling the provider. claude
  2. 02 Set up Codex The ChatGPT desktop app, or an authenticated Codex CLI you can run as codex from a terminal. codex app-server
  3. 03 Set up Cursor Cursor installed, opened at least once, and signed in — the local state database only exists after a real sign-in. Cursor state database
  4. 04 Set up Copilot GitHub CLI installed and signed in to an account with Copilot access. Confirm with gh auth status before enabling the provider. gh
  5. 05 Set up Antigravity Google Antigravity CLI installed and signed in, for the experimental local quota projection. local projection file

03 / 04 · Operations

Known issues, changes, recovery, status.

Each readout below is the real state of the thing it points at, resolved from the same data and flags the page itself renders from — so this index cannot promise something the page then denies.

  1. 01 Known issues Each one traceable to a documented behaviour or an upstream constraint. None of them is a placeholder. 7 entries
  2. 02 Changelog What changed in each published release, generated from one array. zero published
  3. 03 Purchase recovery Getting your licence back on a new Mac or after a reinstall, without emailing anyone. at first release
  4. 04 Service status What the status page will report — checkout, activation, recovery, update feed — and where incidents get posted. no feed yet

04 / 04 · Where a report goes

Six things that go wrong, and where each one goes.

Sending a report to the wrong place is the main reason it goes nowhere. This table is keyed on what happened. The security page is keyed the other way — five channels, and what each one is for.

  1. A meter reads wrong, or does not appear at all Known issues first — most of these are documented Known issues
  2. Setup will not complete for one provider That provider’s setup guide has the failure modes and the fix for each Setup guides
  3. Anything else about the app, from a person The support email. A web form replaces it at launch. support@dipstick.tools
  4. A suspected vulnerability Privately, always — never the public issue tracker security@dipstick.tools
  5. A reproducible bug carrying no account data The public issue tracker on the releases repository GitHub issues
  6. Checkout, activation or recovery is failing right now The status page carries active incidents Status