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

How to stop a long AI coding session from losing grounded facts with Reverify

Hand off a long task to a file-backed state so a fresh context keeps verified facts.

Authorization notice. Reverify is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forA developer running a long analysis task in Claude Code, Codex, or Gemini CLI whose context keeps degrading after auto-compaction or repeated clears.

The problemAuto-summaries drop details and let unverified guesses carry forward, so long tasks drift and need restarts.

The outcomeVerified and refuted results are saved to a ledger on disk, and a new session resumes from the same grounded position without re-proposing known false claims.

What you need first

  • Python installed
  • Install with pip install reverify
  • A binary or source file you are authorized to analyze

Steps

  1. Run pip install reverify to install the tool.
  2. Run reverify rollover to hand the session off to a file and start a fresh one.
  3. Run reverify ledger target.exe to see what is established and what is known false.
  4. Run reverify ledger --hook to register the Claude Code SessionStart hook for compact, clear, and resume events.

Prompt for your agent

Using the reverify repo at 2akouwu/reverify, run reverify rollover to hand off the current session, then run reverify ledger <target> and confirm the established and known-false facts appear in the new session before continuing.

Caveat. The README says the rollover works in Claude Code, Codex, Gemini CLI and OpenCode, but the hook command is documented only for Claude Code, so other agents need their own setup.

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