Reads text exports
read_file and grep open listings, strings output and decompiler text that you saved in your working folder.
The reverse engineering skills needed first are reading assembly, following the stack and keeping disciplined notes. CJK Workbench reads the text your own tools export, explains it line by line, keeps notes in files and runs small Python helpers through Shell. It does not disassemble or run programs itself.
read_file and grep open listings, strings output and decompiler text that you saved in your working folder.
write_file and edit_file maintain a notes file of functions and open questions, and every change appears as a diff.
Python scripts that read a file header or list strings run through Shell, on copies of your files.
A typical session hashes a copy of the file, reads the listing, searches for calls and saves notes in your working folder. Each card expands. It shows the real command result or the file diff.
certutil -hashfile add.exe SHA256exit 0exports/add.lsttext readcall exports/add.lst3 matchesnotes/add.mdsavednotes/add.md+6 linesnotes2 filesReverse engineering an unknown checksum algorithm in your own old program starts with its exported listing. Begin in Plan only, where the agent writes the steps and runs nothing. Then switch mode, let grep find the loop in the listing, and let read_file open the lines around it. The agent explains what each instruction does to the running total, and write_file saves the explanation to notes/checksum.md. Plans survive restarts. A routine that sums bytes looks different in assembly from one that rotates bits, and the notes record which one you found. Compare the notes with your original source, run your own test, and accept the diff only when both agree.
Reverse engineering coding in practice means small scripts around the analysis, and anyone aiming for career growth in malware analysis or reverse engineering soon writes some. Describe the file you want to read, for example the PE header of a program you built, and the agent writes header.py with write_file. Shell runs your Python command on a copy and reports the real exit code. Check the script first. Read it in the diff and confirm that it only reads bytes from the copy and does not execute it. If the command fails, the agent reads the error and edit_file shows the fix as a diff. Run the script on a second copy and keep the output in your notes.
CJK Workbench is a Windows app. It is not a hosted service or a plugin for another program, and it is meant only for files you own, files you have permission to analyse and practice material, on your own PC. It does not disassemble, decompile or run programs itself, and no answer comes with a promise of correctness, so review and test.