---
title: "REA + Claude Code reads what your last app update really changed, send it this s"
url: "https://reamcp.dev/en/cases/rea-claude-code-reads-what-your-last-app-update-really-chang-3a1c06"
source: "https://x.com/i/status/2110859977355145565"
source_type: "x"
author: "Myttle"
author_handle: "xmyttle"
stars: 0
category: "File formats & protocols"
categories: ["formats-protocols"]
tags: ["android-apk", "claude-code", "diff", "electron", "static-analysis"]
added: "2026-10-16T02:06:36.304Z"
updated: "2026-10-15T22:26:51.000Z"
locale: "en"
content_locale: "en"
---

# REA + Claude Code reads what your last app update really changed, send it this s

A post showing how to combine REA with Claude Code to diff two versions of an Electron app or Android APK and produce a labelled change report using REA's compare tool, static analysis only.

## Description

REA + Claude Code reads what your last app update really changed, send it this single prompt and the changelog is dead

The files inside the app know the truth. REA, the free open source Reverse Engineer Anything tool, lets a coding agent read those files, and the prompt on the image points it at one question: what did this update change?

After you paste it into Claude Code, the agent
→ asks you 4 questions: which app, which versions, where, what matters
→ sets REA up with a dry run, plan first, nothing written yet
→ analyzes the old version once and the new one once
→ calls REA's compare tool and keeps only what it returns
→ hands you a table: change, file and function, label, why it matters

The label is the part I would never skip. Every row is OBSERVED
INFERRED or UNKNOWN A missing finding is not proof that nothing changed, and the prompt makes the agent say so

Why I trust labels more than a confident summary: in REA's own blog a rebuilt function matched the original instruction for instruction and still had 0.0 where the original said 128.0.

The check passed because it never looked at the number

For Electron apps and Android APKs you own or may examine.

Static analysis only, nothing gets run, and for an unknown file use a VM because REA is not a sandbox

## Original README

REA + Claude Code reads what your last app update really changed, send it this single prompt and the changelog is dead

The files inside the app know the truth. REA, the free open source Reverse Engineer Anything tool, lets a coding agent read those files, and the prompt on the image points it at one question: what did this update change?

After you paste it into Claude Code, the agent
→ asks you 4 questions: which app, which versions, where, what matters
→ sets REA up with a dry run, plan first, nothing written yet
→ analyzes the old version once and the new one once
→ calls REA's compare tool and keeps only what it returns
→ hands you a table: change, file and function, label, why it matters

The label is the part I would never skip. Every row is OBSERVED
INFERRED or UNKNOWN A missing finding is not proof that nothing changed, and the prompt makes the agent say so

Why I trust labels more than a confident summary: in REA's own blog a rebuilt function matched the original instruction for instruction and still had 0.0 where the original said 128.0.

The check passed because it never looked at the number

For Electron apps and Android APKs you own or may examine.

Static analysis only, nothing gets run, and for an unknown file use a VM because REA is not a sandbox