DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to track Harness token use and estimated cost on macOS with DeepSeek Harness Desktop

Read today and seven-day token totals and estimated cost from the title bar while you work.

Who it is forA macOS user running several Harness sessions who wants to know how many tokens and roughly how much money the work is using.

The problemModel usage and spend are easy to lose track of across many sessions and models.

The outcomeA compact title-bar summary and a detail view showing input, output, cache, estimated cost, and live throughput for your sessions.

What you need first

  • A macOS (Apple Silicon or Intel) or Windows 10/11 x64 computer
  • A model provider account and API key for the provider you want to use in Harness
  • For iPhone: an iPhone on iOS 17 or later and the TestFlight app
  • For Android: a device on Android 8.0 or later
  • For building from source: Node.js 22.19 or newer, and Git

Steps

  1. Install the macOS DMG for your chip, such as DSH-Desktop-0.5.0-mac-arm64.dmg for Apple Silicon.
  2. Configure a provider and API key under Settings, then Models.
  3. Start or continue a Harness session.
  4. Read the compact usage summary in the title bar.
  5. Open the summary for input, output, cache, cost, and live-throughput details.

Prompt for your agent

Using the chokwinlee/deepseek-harness-desktop repo, help me set up DSH Desktop on macOS and find the token and estimated cost figures for my current Harness session. Expected output: today and seven-day token totals and an estimated cost. Verify that any model without a public price is shown as unpriced rather than treated as free.

Caveat. Costs are estimates built from local token logs and available public model prices, so they may not match your provider invoice.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page