Review FPGA reverse-engineering steps with a second model before board checks
At a glance
An FPGA researcher alternated Claude Code and Gemini while mapping a Cyclone IV bitstream, keeping physical verification in human hands. This workflow is listed under reverse-engineering, fpga, model-review.
Agents / tools
Claude Code, Gemini, Quartus Prime, Python, openFPGALoader
Posting as 14sea, the author describes asking Claude for its next step after each small advance, sending the progress summary and proposed step to Gemini, then asking Claude to evaluate Gemini's suggestions. The linked project documents compiling paired designs and comparing their bitstreams to locate configuration bits.
How it went
The project documentation records AND and XOR bitstreams flashed to an AX301 board, with LED behavior matching the intended logic.
Worth knowing
The author says Claude could get stuck on a local approach and Gemini needed steering. Hardware verification still required the author's manual intervention.
Save ideas in this browser. Upvotes count across the board.
Open-source CLI+MCP (morluto/rea) lets Claude Code/Cursor inspect binaries, Electron/.NET/apps via Hopper/Ghidra/IDA, returning evidence-backed observations so agents can rebuild features from behavior without copying source.
MIT Claude Code plugin hands tasks to DeepSeek, Gemini (Antigravity), Codex, OpenCode or Copilot as worker CLIs—each in an isolated git worktree with your verify command—then returns a compact verdict/patch for Claude to review; API keys stay in a local browser form.
An indie hacker packaged an agency's eight repeated workflows (briefs, client approval with revision counters, quotes with margin checks, content calendars, post-mortems) as free MIT Claude skills.
A builder asked Grok Bot to bridge to Claude Code—Grok does live research/browser work while Claude Code builds, and they ping each other for Playwright and research help.