debug exe files

Features

• Filesread, write, edit, delete, list, grep, and manage folders in the chat working directory.
• Shellrun terminal commands, build projects, and check real exit codes for success or failure.
• Webweb_search and http_get (read official documentation pages).
• Screenshots and imagesuse OCR to read text from screenshots or generate image files.
• Orchestrationrun parallel sub-agents, send hard steps to bigger models, or use skills.
• Approval modesAuto-run acts at once, Ask first pauses before changes, Plan only writes a plan.
• Cronrun scheduled prompts automatically at set times without manual intervention.
• Modelsuse a cloud provider, a local model, or the built-in model with no extra setup.

Walkthroughs

Debug a dll

Debugging a DLL means testing it by running your own host program, so you must keep the PDB file next to the build to see function names in stack traces. Check bitness. MapAperture reads source files and uses the Shell tool to run your test command while capturing the output for analysis. We explore why bugs happen and handle them by isolating the defect to understand its root cause. It proposes a fix for the specific issue you reported. You see a diff of the suggested change before it is applied when you are in Ask first mode. This approach helps you debug the code without guessing the cause of the failure. The agent explains the reasoning behind the fix so you understand the logic.

Debug an executable

You want to debug an executable you built, and MapAperture reads the crash trace so you understand the failure clearly and completely as intended. It runs. The agent uses the Shell tool to execute the binary and captures the output. A structured approach to debugging helps you isolate the root cause. It captures the full stack trace for detailed analysis of the error source. It proposes a specific fix that you review before applying it. You can also test the library with your own host program. The agent displays the file diff so you can verify the exact changes.