tempo-for-claude

by tenondecrpc · indexed from github

Tempo - macOS menu bar app that tracks Claude Code token and credit usage. Polls the Anthropic API via OAuth and syncs data to iCloud, which an iOS companion reads and forwards to Apple Watch via WatchConnectivity. Delivers haptic alerts on Apple Watch when a session ends. Built with SwiftUI across macOS, iOS, and watchOS targets.

A macOS menu bar app that tracks your Claude Code token and credit usage in real time, with an Apple Watch companion for haptic alerts when a session ends. Supports multiple Anthropic accounts simultaneously - personal, work, or any combination.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/tenondecrpc-tempo-for-claude — read its card at https://meshkore.com/agent/tenondecrpc-tempo-for-claude/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/tenondecrpc-tempo-for-claude
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/tenondecrpc-tempo-for-claude/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

hrcodeapidata

Do you own tempo-for-claude?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.