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

How to check whether an agent's 'done' claim is verified with Agentacct

Open a task receipt and separate the agent's own Reported result from checks that passed after the last change.

Who it is forA developer who has been told an agent finished a change and wants to confirm it before merging or reviewing the diff.

The problemAn agent's own statement that work is done can sound final even when no passing check ran after its last edit.

The outcomeA clear view of whether the result is only Reported or Verified, with the timeline of attempts, checks, and any earlier failures still visible.

What you need first

  • Python 3.11 or newer on macOS or Linux, or Windows through WSL, with pipx available (or the signed macOS app from the latest release on macOS 14+)
  • At least one supported coding agent with local session logs on this machine, such as Claude Code or Codex
  • Permission to open a new agent session after setup, because hooks and MCP servers bind at session start

Steps

  1. Run agentacct tui
  2. Open Sessions and select the task whose result you want to check
  3. Read the recorded outcome: Reported means the agent's own claim, Verified means current passing checks after the last recorded change
  4. Open the check details and the activity timeline to see which tests ran and when

Prompt for your agent

Use the agentacct repo at https://github.com/mikehasa/agentacct to open the receipt for the task <task name> and report whether its result is Reported or Verified. Confirm that any passing checks ran after the last recorded change, and list any earlier failed checks that remain in the history.

Caveat. A Verified result only covers the checks Agentacct recorded, so it does not replace your own review of the code.

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