🤖 Agent Run Monitor

Runs
Token Costs
Stuck Handoff

Agents that have been stuck for more than 5 minutes (or 300 simulated seconds) are listed below. You can hand them off to a human.

🔗 Share:

Local run fixtures, filtering and stored costs

Read the explanation

The original page initializes seven authored run records. Two are completed, two running, two stuck, and one failed. Filtering for stuck displays two rows while summary total remains seven because it counts the complete stored array. At thirty five pixels per total or filtered run the bars span two hundred forty five and seventy. These are local sample statuses, not telemetry from active workers or a backend. The original offline Chart dependency fails after list and cost summaries update, preventing later handoff and share rendering. That original limitation is preserved in the diagnostic preview. The seven sample records contain twenty eight thousand eight hundred fifty input plus output tokens. Multiplying by the authored rate of point zero zero two dollars per thousand gives point zero five seven seven dollars. But the displayed cost summary sums the separately stored cost fields, which total point one one eight dollars. At two thousand pixels per dollar the bars span two hundred thirty six and one hundred fifteen point four. The sample costs are not recomputed from that rate. Newly added runs use the formula, so the array mixes stored fixture costs and calculated additions. None of these values verifies actual billing or a current provider price. Editing one displayed stuck run to completed reduces the stored stuck count from two to one and increases completed from two to three. At eighty pixels per stuck run the bars shrink from one hundred sixty to eighty. The edit accepts one of four status strings and then rerenders local data. It does not prove a worker resumed or completed its task. The separate handoff function likewise assigns completed and shows an alert, with no human assignment service or operational handoff. Because the offline chart fails before the handoff list is built, we do not claim that handoff control or share-link workflow succeeds.

Super generates helpful tools and automates fact-checking across the internet proactively. If you enjoyed this tool, build your own with Super and share it with a friend.