Explore the Console toolkit
Choose a capability by the job you want to do. Each guide explains its interface, an example, how it fits into ClautoHotkey, and the limits of the result.
Structured diagnostics
Give AI the error type, source location, failing statement, and exit code it needs to diagnose a script.
Console Read the guideLine Out & trace
Follow the statements that actually ran, with source files and line numbers to explain the path to a failure.
Console Read the guidePrint & JSON
Turn a script into a composable command-line tool, with UTF-8 output and native JSON.
Console Read the guidePersistent REPL
Keep state between expressions. Explore functions and recover from invalid input.
Console Read the guideInspect & Check
Describe values as JSON and ask the interpreter to check source before running it.
Console Read the guideProcessPipe
Exchange UTF-8 lines with a child process and manage its lifetime.
Console Read the guideAutomatic edit checks
A real Claude Code hook checks AHK syntax after Write or Edit, with an optional runtime probe.
ClautoHotkey Read the guideSkills & knowledge
Load task-specific AHK guidance for GUIs, COM, classes, debugging, and more.
ClautoHotkey Read the guideGrading gates
Keep static and dry-run findings, parser confidence, and intercepted effects in a shared format.
ClautoHotkey Read the guideNative MCP tools
Let a local tool client check, run, test, and explore source through the same engine.
Together Read the guideTest → inspect → repair
Combine assertions, structured failures, and source context into a repeatable repair loop.
Together Read the guideCrash forensics
Preserve startup, error, and exit events when stderr alone is not enough.
Console Read the guideStart with the process contract
Results belong on stdout. Diagnostics belong on stderr. The exit code tells the caller whether the process succeeded. These three channels make a script usable by a shell, a test runner, or an MCP client.
Newer features build on that foundation: inspection turns live values into structured data, ProcessPipe connects another process, and trace/coverage explain execution. Check your build before using the development APIs.