# Debugger: Interpreters

This window only supports the older "Recorder-based" targets. For newer "TraceRmi-based" targets, the actual debugger runs in an integrated VT-100 terminal emulator.

For debuggers which have built-in interpreters (many do), and whose connectors expose that interpreter in the model, the interpreters plugin can provide user access to it via a graphical console. The plugin leverages the existing interpreter console framework in Ghidra, so the interface should be relatively familiar. Typically, the console is accessed via the Objects window's Console action. Output is displayed in a large text field, and user input is taken via a small text field at the bottom. The prompt, commands, and outputs are all defined by the connector.

## Actions

Each interpreter console has the following actions:

### Clear Interpreter

This action is always available. It clears the console's output buffer.

### Remove Interpreter

This action appears when the target's interpreter is no longer valid, i.e., the connection was closed. It permanently closes the console. Note this action can only appear if this console was pinned.

### Pin Interpreter

This action is always available. Normally interpreter consoles are permanently closed immediately upon the associated target interpreter becoming invalid, i.e., the connection was closed. Pinning an interpreter keeps it open, but in a disabled state, so that the buffer can be examined after invalidation.

### Interrupt

This action is always available. It interrupts the current target's execution.