RunMat
  • Pricing
RunMat
GitHub
GitHub
DownloadSign InTry in Browser
DesktopRuntimeServer
RunMat

Run math blazing fast

GitHubX (Twitter)LinkedIn

Company

  • About
  • Pricing
  • Contact

Explore

  • RunMat for academia
  • RunMat vs MATLAB Online
  • Benchmarks

Get product updates and release notes from the RunMat team.

© 2026 Dystr · Made withfor the scientific community.

RunMat™ is a registered trademark of Dystr, Inc. MATLAB® is a registered trademark of The MathWorks, Inc. RunMat is not affiliated with, endorsed by, or sponsored by The MathWorks, Inc.

LicensePrivacy
/
    • Session Engine
    • Execution Requests
    • Workspace State
    • Variable Inspection
    • Workspace Replay
    • Interaction & Streams
    • Host Integration
    • Execution
    • Async Execution
    • Errors & Diagnostics
    • Remote Execution
Docs>Runtime>Sessions and Execution

Workspace Replay

Workspace replay persists and restores live session variables. It is owned by runmat-runtime::replay::workspace and the session import/export methods.

Workspace replay exports session variables into a JSON payload containing base64 MAT bytes:

Loading diagram...

export_workspace_state gathers each value as needed before encoding. WorkspaceExportMode::Auto returns nothing for an empty workspace; Force emits a payload even for an empty workspace; Off disables export.

import_workspace_state validates and decodes the replay payload, clears the current session workspace, then installs restored variables into slots, bindings, and durable values. Import is restore/replace semantics, not merge semantics.

Replay Limits

The runtime enforces replay limits before accepting payloads:

LimitDefault
Workspace payload bytes32 MB
MAT payload bytes24 MB
Variable count2048

Rejected payloads produce replay/runtime errors instead of partial imports.

On this page
  • Replay Limits