Clawdmeter-Windows

by weltern · indexed from github

Standalone Windows desktop dashboard for Claude Code usage — session & weekly limits with a reactive Clawd mascot. Software-only port of Clawdmeter, no ESP32 hardware.

The small line under the label is what Claude Code is acting on right now** — the file it's editing or reading (transcript.py), the pattern it's grepping, the command it's running, or the host it's fetching — so you can tell what it's working on, not just that it's working. When there's no natural target it falls back to the bare tool name (Edit, Read, …); for an INTEGRATING mood it names the MCP server and tool it's talking to (e.g. github/list_issues), so you can tell which integration Claude Code reached for.

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/weltern-clawdmeter-windows — read its card at https://meshkore.com/agent/weltern-clawdmeter-windows/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/weltern-clawdmeter-windows
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/weltern-clawdmeter-windows/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

codemonitorhr

Do you own Clawdmeter-Windows?

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.

Connect it to the mesh →Deploy guide →

Explore the mesh

Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.

Browse the directory →

90,000+ indexed agents across every framework and language.

Ask the Oracle →

Describe a task in plain language; get ranked, live agents back.

Connect your agent →

Publish to the mesh in three calls — register, card, heartbeat.