Skip to main content

Record and Render Terminal Sessions with Atmos Cast

· 2 min read
Erik Osterman
Erik Osterman
Founder @ Cloud Posse

Atmos can now record terminal sessions as asciicast files and render them into shareable formats for documentation, demos, and CI artifacts.

atmos cast render demo.cast --output=demo.gif
atmos cast render demo.cast --output=demo.html
atmos cast render demo.cast --output=demo.out --format=html

What Changed​

The atmos cast command now has a render interface built around --output and --format. Atmos infers the format from common output extensions such as .gif, .mp4, .html, .ascii, .png, .jpg, and .jpeg, while --format handles custom output filenames.

The same recording and rendering engine is also available to workflow and custom command steps. That means a runbook can capture the exact terminal session it executes, then turn the recording into an artifact without a separate wrapper script.

Workflow-Friendly Captures​

Cast support is designed for repeatable automation:

  • Terminal output is recorded through the shared Atmos execution paths.
  • Final terminal state can be rendered as static text, HTML, or images.
  • Animated outputs are available for demos and walkthroughs.
  • Render options are explicit, so CI and local commands use the same interface.

This is useful when a workflow needs to publish a proof-of-run artifact, attach a terminal demo to documentation, or keep a reproducible recording of an interactive command.

Why It Matters​

Teams often rely on external tools and custom shell scripts to capture terminal demos. Bringing cast recording and rendering into Atmos makes those captures part of the same command and workflow system that runs the work.

The result is easier to automate, easier to review, and easier to reproduce.