FIRST PUBLIC PREVIEW · v0.27SCARDINA CYBER CONSULTING

THE VISUAL BINARY WORKBENCH

Every byte.
A bigger picture.

Bring a visual hex workbench into your ChatGPT or Codex conversation. Open a file with a prompt, explore it visually, and ask for explanations or reviewed changes.

Download for Mac See how it works inside ChatGPT Free personal & commercial binary use · Proprietary source
HEX EDIT / LINKED WORKSPACEv0.27.0
01 / 03
Start with an exact selection.

Select an instruction to highlight its verified file bytes. Virtual addresses and file offsets keep their distinct identities.

HEX + ASCIIASSEMBLY + PSEUDOCODECONTROL-FLOW GRAPHSREVIEWED PATCHESPDF OBJECTS + PREVIEWS
NEW / Explore PDF objects, image previews & resource extraction

FIRST PUBLIC RELEASE / v0.27.0 PREVIEW

Your workbench.
Ready to install.

For macOS 13.5+ on Apple Silicon. The core editor and a private Node runtime are included. REA, Ghidra, a JDK and qpdf are separate optional tools.

46 MB ZIP · No paid certificate or notarization · Public preview

Verify the download’s SHA-256c92c93364fdf62b849d65973c3c8b591cf65b6b69601fce7b34c72d6743af31fDownload checksum file

Official unmodified binaries are free for personal and commercial use. Hex Edit remains proprietary; modification and redistribution require permission. Read the usage terms.

  1. 01

    Download, extract, open

    Install Codex first. Extract the ZIP and open Hex Edit Setup.app. macOS may block this unnotarized app; review Apple’s guidance and approve only a source you trust. Setup never disables Gatekeeper.

  2. 02

    Choose your working folder

    Select the files folder Hex Edit may access. Codex is detected where available. Optional analysis connects your existing trusted REA/Ghidra/JDK installations; it does not download them.

  3. 03

    Install, then ask

    Click Install Hex Edit, start a new Codex chat, and say “Open Hex Edit with the sample.” Expand the visual result into the side panel. Restart Codex normally if it retains old tools.

Codex setup and ChatGPT connection are separate.

The Mac setup installs the local Codex plugin. ChatGPT requires a separately connected backend and your account consent; this package does not create a public endpoint or a directory listing. Read the complete setup guide.

Selected bytes and tool results shared with Codex/ChatGPT may be processed by the host/model provider. Keep confidential files within your organization’s approved workflows. Data handling · Usage terms · Support

INSIDE CHATGPT & CODEX

Open Hex Edit
with a prompt.

Your conversation and your visual investigation can work together. ChatGPT can open the connected Hex Edit panel, read the selected bytes through tools, explain what you are looking at, and prepare precise patch proposals for your review.

01 / OPENFrom the prompt
“Show firmware.bin in Hex Edit.”

ChatGPT invokes Hex Edit and opens an interactive workbench in the conversation. Use the panel to inspect hex and text, navigate the file, and keep working with the same investigation.

PROMPT → VISUAL WORKSPACE
02 / INVESTIGATEWith shared context
“What do the selected bytes represent?”

ChatGPT can inspect the current selection and exact revision through Hex Edit’s tools. Ask follow-up questions, inspect a header, or request an explanation while navigating visually.

SELECTED BYTES → EXPLANATION
03 / PROPOSEWith you in control
“Propose changing this value to 42. Don’t apply it.”

ChatGPT can stage a patch with the expected and replacement bytes. You review and apply the proposal in Hex Edit; the original stays intact, and applied edits support undo and redo.

PROPOSAL → YOUR REVIEW

Ask. Explore. Review. Keep going.

The panel is interactive, not a screenshot. Hex Edit supplies file and revision context; ChatGPT works through the connected tools. The separately installed REA backend adds native-code analysis and linked evidence.

See how REA fits in
DEVELOPER PREVIEW / SETUP & SCOPE

Examples illustrate the workflow; this page is not a live chat. Hex Edit must be installed and connected in a supported host, and the file must be accessible in its configured workspace. Panel expansion and downloads depend on host capabilities.

Earlier ChatGPT checks cover core editing, undo/redo, direct REA flows and PDF resources. The new v0.27 analysis UI still needs fresh Codex/ChatGPT qualification; each tour capture states its own tested host and version. See current preview scope ↗

LESS CONTEXT SWITCHING. MORE CONTEXT.

Stay close to the bytes.
See how the pieces connect.

Hex Edit brings a persistent visual workspace to binary investigation. Move between bytes and code, retain your findings, and examine proposed changes before applying them.

REA supplies the analysis. Hex Edit connects those observations to the exact file and revision you are viewing, with current, historical and incomplete evidence made visible.

17 REAL VIEWS / A GUIDED LOOK INSIDE

The workbench,
up close.

Open any screenshot for a closer look.
Every view was captured from the actual tool using generated test files.

17 views

ANALYZE

Four perspectives. One investigation.

Read the bytes, inspect the assembly, follow the control-flow graph and consult reconstructed pseudocode in a connected workspace.

  • Instruction selections map to verified file bytes.
  • The graph and assembly follow the selected instruction; pseudocode follows its function.
  • Resizable panes, focused views and saved layouts adapt to the way you work.
What this screenshot shows

Pseudocode is reconstructed by the provider. Exact instruction-to-pseudocode-line mapping is not available.

ANALYZE

See the paths through the code.

Explore basic blocks and distinguish branch, fallthrough, jump and loop relationships without losing the byte-level context.

  • Zoom, pan and fit the graph; use the minimap to keep your bearings.
  • Follow observed branches and highlight a static exploration path.
  • Move between instructions and blocks with the keyboard.
What this screenshot shows

A static path is an exploration aid, not a recording of execution. Unresolved destinations remain unknown.

INSPECT

Start with the bytes.

A color-coded hex and text view brings selections, recognized structures and modified bytes into focus. Keep the immutable original beside your working revision.

  • Choose row widths, byte grouping and explicit endianness.
  • Interpret signed and unsigned integers, floats and text.
  • Search masked hex or UTF-8; jump to an offset or bookmark a location.
What this screenshot shows

The screenshot shows original/working comparison on a generated PNG fixture. Recognized headers are structural hints, not validity checks.

CHANGE

Understand a change before applying it.

Stage exact byte overwrites, review the expected bytes and inspect the instruction impact before committing a compatible patch set.

  • Compare current instructions with a separately analyzed proposed snapshot.
  • Expose overlap, stale revisions and partial instruction coverage.
  • Apply as one undoable transaction; request REA reanalysis after edits.
What this screenshot shows

This screenshot deliberately shows a staged proposal awaiting REA decoding. Static previews do not prove executable correctness; signatures and checksums are not repaired automatically.

INSPECT

Turn a byte range into named fields.

Apply a declarative template to decode headers, arrays, enums and bitfields. Select a field to inspect its exact bytes.

  • Built-in templates cover common Mach-O, ELF, PNG and DOS headers.
  • Use explicit byte order and bounded JSON templates without executing code.
  • Save reusable templates and review numeric overwrites through the existing edit flow.
What this screenshot shows

A selected template is your interpretation of the bytes, not proof that the entire file conforms to that format.

ANALYZE

Explore the layout REA actually observed.

Inspect provider-defined structures, field offsets, lengths and child types, with evidence and coverage kept alongside the layout.

  • Browse retained type lookups and inspect their field tables.
  • Follow explicitly observed child type identities.
  • Navigate to field bytes when the current evidence verifies their mapping.
What this screenshot shows

These are retained real REA/Ghidra observations from a generated native fixture, not original source declarations. Full automatic ChatGPT type workflows remain under qualification.

CHANGE

Compare changes without confusing coordinates.

Inspect differences between two file revisions or binaries. Bounded aligned windows help reveal inserted, removed and changed sequences.

  • Choose each file, byte source and starting offset independently.
  • Navigate changed ranges while keeping separate coordinates on both sides.
  • Compare imported functions, instructions and provider pseudocode.
What this screenshot shows

The screenshot shows a real bounded alignment of two generated fixtures. Repeated bytes can admit alternative alignments. Comparison does not enable insertion/deletion editing.

ORGANIZE

Keep the reasoning with the evidence.

Capture comments, user labels and named locations at a byte selection. Your notes stay distinct from provider symbols.

  • Bind each entry to a byte range, digest and revision.
  • Flag notes for review when the underlying revision changes.
  • Exchange project metadata and retain investigations in the library.
What this screenshot shows

The note shown is a tour example saved only in an isolated copy of the generated fixture. Project metadata exchange is separate from full investigation archives.

ORGANIZE

A powerful tool, close at hand.

Use organized menus, a compact toolbar, right-click actions or the searchable Command-K palette to reach the same workbench commands.

  • Find commands, settings and saved layouts without hunting through panes.
  • Keep unavailable actions visible with the reason they need more context.
  • Hide menu chrome or the minimap and save a layout that suits your investigation.
What this screenshot shows

Keyboard delivery, clipboard access and downloads depend on the host. Commands preserve the originating review before consequential actions.

ANALYZE

Know the state of your analysis.

Track requested, running, completed and interrupted work. Keep retained snapshots and evidence available when a host or provider stops responding.

  • Bind requests and imports to the exact artifact, architecture and byte revision.
  • Inspect ownership and fresh provider state before preparing a separate retry.
  • Recover verified retained evidence without silently rerunning analysis.
What this screenshot shows

The screenshot shows retained tracking awaiting a provider update. A timeout or expired reservation does not establish cancellation or permit automatic takeover.

PDF

Browse the PDF object tree.

Follow the catalog, pages, dictionaries, arrays and indirect references, then view supported image objects directly in the explorer.

  • Expand page resources and inspect each selected logical value.
  • View decoded RGB/grayscale/JPEG images with fit, zoom and pixelated scaling.
  • Keep cyclic references visible without expanding forever.
What this screenshot shows

Captured in the native Codex v0.23 panel using a generated 256 × 144 RGB image. Optional qpdf 11+ powers PDF inspection independently of REA. Unsupported image encodings retain explicit limits; previews do not render the complete PDF page.

PDF

Extract images, scripts and streams.

Review the output format, byte count, SHA-256 and workspace destination before saving a resource separately from the PDF.

  • Export supported images as PNG or original JPEG, and script/XFA sources as files.
  • Choose decoded or encoded stream bytes and inspect embedded-file references.
  • Recompute and verify the reviewed output before creating a unique saved file.
What this screenshot shows

This native Codex v0.23 screenshot shows a verified 29,162-byte PNG export from a generated PDF. The source remains revision 0 and unchanged. Exports are bounded to 8 MiB; downloads depend on host capabilities, and extracted content is never launched.

ANALYZE

Put reasoning beside the instructions.

Name a function locally, annotate instructions and blocks, and inspect exact bytes, operands and observed branch destinations without leaving the linked workspace.

  • The context inspector follows verified hex and instruction selections.
  • Local names and notes stay distinct from REA symbols and provider pseudocode.
  • Current/historical revision identity stays visible; uncertain mappings remain unknown.
Capture scope & limitations

v0.27 local-browser capture with authenticated retained REA/Ghidra evidence and generated bytes. Fresh native Codex/ChatGPT qualification remains pending.

ORGANIZE

Simplify the graph. Keep the evidence.

Group related basic blocks, collapse and expand the diagram, and review a standalone SVG that retains the original graph facts and annotations.

  • Groups persist across restarts and change presentation only.
  • SVG metadata retains original blocks, edges, exact instructions and snapshot identity.
  • Review the SVG before export; selectable source is available when host downloads are unavailable.
Capture scope & limitations

v0.27 local-browser capture. The SVG source and XML were verified; automatic host download receipt was not observed. Direct PDF graph export is not included.

ORGANIZE

Install the core editor from one package.

Choose a working folder, detect Codex, and install Hex Edit with its own Node runtime. Connect existing REA/Ghidra/JDK tools when you need disassembly.

  • macOS 13.5+ on Apple Silicon; per-user setup with no terminal commands for the core install.
  • REA, Ghidra, a JDK and qpdf are separate optional installations.
  • No Developer ID certificate or notarization; macOS may require explicit launch approval.
Capture scope & limitations

Setup-interface capture from v0.26.3, with the same Setup.swift UI used by the v0.27 package. Clean-Mac and quarantined-download installation remain untested.

TWO TOOLS. A CONNECTED WORKFLOW.

REA does the analysis.
Hex Edit brings it into view.

Keep REA as your separately installed native-code reverse-engineering backend. PDF object inspection uses the optional local qpdf provider. Use Hex Edit to explore its observations visually, navigate verified byte mappings, organize findings and review changes.

01

Capture the snapshot

Choose the file revision and architecture. Analysis receives an immutable snapshot with an explicit digest.

FILE → SNAPSHOT
02

Investigate with REA

With your trusted direct connection configured, Hex Edit runs tracked static REA/Ghidra jobs without waiting for another model turn. No target application execution is required.

LOCAL RUNNER → REA / GHIDRA
03

Explore linked evidence

Validated imports connect observed instructions, blocks and mappings to the matching revision.

EVIDENCE → WORKBENCH

Edits create a new working revision. Previous analysis stays readable as historical evidence; fresh analysis is needed to restore current byte links.

BUILT FOR THE WORK

Depth where it matters.

⌕

Follow the leads

Browse imported functions, symbols and strings. Inspect incoming and outgoing cross-references, follow mapped locations, and return through navigation history.

↶

Keep changes reviewable

Preserve the immutable original, stage exact overwrites, undo or redo transactions, and export verified copies or portable patch manifests.

▦

Make the workspace yours

Resize panes, save named layouts, switch themes, toggle the minimap and choose between linked views and focused analysis.

PUBLIC PREVIEWv0.27.0 / NOVEMBER 2026

Available to explore. Still earning v1.0.

The first public preview includes the core editor, linked REA views, PDF inspection, durable local annotations, a context inspector and reversible graph groups. It is not a v1 release candidate or an approved OpenAI directory listing.

Qualification and current limits

All 445 regression tests pass. The v0.27 analysis UI passed local browser checks with authenticated retained REA evidence; fresh native Codex/ChatGPT checks are pending. Changed code does not inherit older host receipts. Clean-Mac installation and downloaded-app approval remain untested; abrupt host loss and physical power loss were not tested.

Files are limited to 64 MiB and eight open tabs. Edits are fixed-length overwrites. Instruction assembly, insertion/deletion editing, a debugger, automatic checksum/signature repair, direct PDF graph export and exact instruction-to-pseudocode-line mapping are not included. A static preview does not guarantee patched application behavior.

Historical tour captures are individually scoped. New v0.27 chapters use an isolated local browser and generated fixtures. Screenshots demonstrate the interface; they are not a live embedded editor.

← → Browse · Esc Close