App Connector · Developer & cloud

REA

Ask what a program does and get the answer from its code, not a guess.

Reverse engineer software you own: .NET assemblies, JavaScript and Electron apps, Go and Rust binaries, firmware images and traffic captures. Plexon reads the method bodies, strings and call edges instead of guessing.

Download Plexon How connectors work

What you can do

A connector lets the assistant use an app or tool for you. Once connected, ask it to work with REA.

Open .NET assemblies

Metadata, decoded CIL, call edges, field accesses and string literals, with nothing extra installed.

Read apps and binaries

JavaScript and Electron apps, Go and Rust binaries, PE resources, WASM, archives and firmware images.

Read captured traffic

HAR and SAZ captures and live browser capture, to see what a page or an app really sends. Nothing recorded is fetched again.

Bring your own engines

Point it at Ghidra for native decompilation, JADX for Android APKs (needed for any APK read), WABT for WASM, adb for a connected device, a Chrome-family browser or Frida for runtime evidence.

Things you can ask

Type these in chat once the connector is on.

What does the "lights off" button in this LED control tool send over the serial port?Open this Electron app and list the endpoints its renderer talks toWhat does this Go binary do on startup, and which config files does it read?Decompile this APK with JADX and show me where it stores the login token

What you need

Nothing to sign in to. Optional: point it at Ghidra, a JDK, JADX or adb in the connector settings.

Setup details

Install REA from Apps. It runs on the Node that Plexon manages and downloads the REA package from npm the first time it starts, so there is nothing else to install.

Optional engines, each set in the connector settings: Ghidra 12.1 with JDK 21 for native decompilation, JADX for Android APKs (every APK read goes through it), WABT 1.0.42 for WASM modules, adb for devices, a Chrome-family browser for capture, and Frida for runtime hooks.

Use it on software you own or are authorized to examine.

Some tools run the program, attach to it, or install, start, stop and remove apps on a connected Android device. In Plan and Ask mode Plexon asks before any of those; in Code mode the assistant names them before calling.

A dozen entry-point tools stay on; the rest load on demand through tool search.

When a task uses an online app, that app receives the request. Its results may also be sent to the AI service handling your chat. You can turn the connector on for one workspace and leave it off for another.

Once REA is on

A connected app is a source. These are the parts of Plexon that draw on it.

AI Chat & Modes
Turn one on with your own account and the assistant works inside that app.
Dynamic Workflows
An inbound message or a poll on a connected app starts a run.
A Tool step calls a connector directly, spending zero AI tokens.
Dashboards
A widget's data can come from a connector tool call, refreshed on a timer.
Action Record & Tool Rules
A call to a connected app is written down before it runs and again when it ends, with the app named on the row.