keyboard — Compatibility no-op for MATLAB keyboard debugging stops.

keyboard is accepted so MATLAB scripts containing manual debug stops continue to run under RunMat.

Syntax

keyboard

How keyboard works

  • keyboard accepts no inputs and returns no outputs.
  • RunMat currently treats it as a deterministic no-op. It does not enter MATLAB's interactive K>> debug prompt.
  • Interactive debugger suspension is a broader runtime/REPL feature and is not implemented by this builtin.

Does RunMat run keyboard on the GPU?

keyboard is control-flow debugger compatibility and has no GPU/provider behavior.

Example

Accept a manual debug stop without halting batch execution

keyboard

Using keyboard with coding agents

Open a RunMat example with live inputs, then ask the agent to explain how keyboard changes the result.

Run a small keyboard example, explain the result, then change one input and compare the output.

FAQ

Does RunMat enter an interactive debugger for keyboard?

No. The command is accepted as a no-op until interactive debugger infrastructure exists.

Open-source implementation

Unlike proprietary runtimes, every RunMat function is open-source. Read exactly how keyboard is executed, line by line, in Rust.

About RunMat

RunMat is an open-source runtime that executes MATLAB-syntax code blazing on any GPU. It is licensed under the Apache 2.0 license.

  • RunMat automatically optimizes your math for GPU execution on Apple, Nvidia, and AMD hardware. No code changes needed. Simulations that took hours now take minutes.
  • Start running code in seconds. RunMat runs in the browser, on the desktop, or from the CLI. No license server, no IT ticket.

Getting started · Benchmarks · Pricing

Download RunMat

Download RunMat for full performance, or use RunMat in your browser for zero setup.