Skip to main content
toolsSource-backed
Asciinema logo

Asciinema

Open-source CLI and web ecosystem for recording, replaying, live streaming, sharing, and embedding terminal sessions as lightweight asciicast files.

by asciinema · submitted by oktofeesh1·added 2026-06-03·
HarnessCLI
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://docs.asciinema.org/manual/cli/, https://github.com/asciinema/asciinema, https://asciinema.org/
Brand
Asciinema
Brand domain
asciinema.org
Brand asset source
brandfetch
Safety notes
Terminal recordings can capture secrets, prompts, commands, file paths, hostnames, account names, API output, and generated code, so review and redact casts before publishing or embedding them., Live streaming exposes terminal output as it happens; use it only in approved environments and avoid production shells, private repositories, credentials, customer data, and destructive commands., Optional input and environment capture should be configured deliberately because it can record keystrokes, command context, and metadata that are more sensitive than the visible terminal output.
Privacy notes
Local `.cast` files can contain terminal output, timing data, window size, command metadata, titles, captured environment fields, and optionally keyboard input., Uploading or streaming through asciinema.org sends recordings or live terminal output to the public asciinema service unless visibility and sharing settings are reviewed first., Self-hosted asciinema servers still need access control, retention, backup, log, database, and upload-storage policies for recorded terminal sessions.
Author
asciinema
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-03

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

78

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Copy & paste

Copy-ready — paste the snippet to get started.

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup. Includes a review or approval gate.

0/3 ready
Network & hosting1Review & approval2

Safety & privacy surface

Safety & privacy surface

3 safety and 3 privacy notes across 4 risk areas. Review closely: credentials & tokens, network access.

4 areas
  • SafetyCredentials & tokensTerminal recordings can capture secrets, prompts, commands, file paths, hostnames, account names, API output, and generated code, so review and redact casts before publishing or embedding them.
  • SafetyCredentials & tokensLive streaming exposes terminal output as it happens; use it only in approved environments and avoid production shells, private repositories, credentials, customer data, and destructive commands.
  • SafetyExecution & processesOptional input and environment capture should be configured deliberately because it can record keystrokes, command context, and metadata that are more sensitive than the visible terminal output.
  • PrivacyLocal filesLocal `.cast` files can contain terminal output, timing data, window size, command metadata, titles, captured environment fields, and optionally keyboard input.
  • PrivacyNetwork accessUploading or streaming through asciinema.org sends recordings or live terminal output to the public asciinema service unless visibility and sharing settings are reviewed first.
  • PrivacyCredentials & tokensSelf-hosted asciinema servers still need access control, retention, backup, log, database, and upload-storage policies for recorded terminal sessions.

Disclosure: editorial

Safety notes

  • Terminal recordings can capture secrets, prompts, commands, file paths, hostnames, account names, API output, and generated code, so review and redact casts before publishing or embedding them.
  • Live streaming exposes terminal output as it happens; use it only in approved environments and avoid production shells, private repositories, credentials, customer data, and destructive commands.
  • Optional input and environment capture should be configured deliberately because it can record keystrokes, command context, and metadata that are more sensitive than the visible terminal output.

Privacy notes

  • Local `.cast` files can contain terminal output, timing data, window size, command metadata, titles, captured environment fields, and optionally keyboard input.
  • Uploading or streaming through asciinema.org sends recordings or live terminal output to the public asciinema service unless visibility and sharing settings are reviewed first.
  • Self-hosted asciinema servers still need access control, retention, backup, log, database, and upload-storage policies for recorded terminal sessions.

Prerequisites

  • asciinema CLI installed from an official package manager, release binary, or reviewed source build.
  • Terminal workflow, CLI demo, pair-programming session, support reproduction, or AI-agent run that is safe to record.
  • Decision on whether recordings stay local, are shared through asciinema.org, are streamed live, or are hosted on a reviewed self-hosted asciinema server.

Schema details

Install type
copy
Troubleshooting
No
Source repository stats
Scope
Source repo
Tool listing metadata
Pricing
open-source
Disclosure
editorial
Application category
DeveloperApplication
Operating system
Linux, macOS, FreeBSD, Web, Self-hosted
Full copyable content
## Editorial notes

Asciinema is useful when Claude-adjacent teams need a durable, text-based record of what happened in a terminal without shipping a large screen recording. It can capture a CLI demo, failed reproduction, pair-programming session, or agent run as an asciicast, then replay it locally, publish it to asciinema.org, embed it in docs, or stream the terminal live for reviewers.

## Source notes

- The official docs describe asciinema as a suite of tools for recording, streaming, and sharing terminal sessions.
- The CLI manual describes asciinema CLI as a recorder/client for terminal sessions that stores lightweight `.cast` files, replays them locally, publishes them to an asciinema server, embeds them with the player, or streams sessions live.
- The quick-start docs cover installation from common Linux, macOS, FreeBSD, Cargo, and release-binary paths, plus `rec`, `play`, `upload`, and `stream` workflows.
- The GitHub repository is `asciinema/asciinema`, describes the project as a terminal session recorder, streamer, and player, and is GPL-3.0 licensed.

## Duplicate check

Checked current `content/tools/`, `content/mcp/`, guides, skills, agents, open pull requests, live HeyClaude `llms-full.txt`, and repository-wide content for `Asciinema`, `asciicast`, `asciinema.org`, `docs.asciinema.org`, `github.com/asciinema/asciinema`, `terminal session recorder`, `terminal recording`, `live terminal streaming`, `VHS`, `terminalizer`, `ttyrec`, and `scriptreplay`. Existing AgentOps, Browserless, and Jam entries mention adjacent session replay concepts for agents, browsers, or feedback capture, but no dedicated terminal session recording tools entry, source URL duplicate, or open duplicate PR was found.

## Disclosure

Editorial listing. No paid placement or affiliate link is used.

About this resource

Editorial notes

Asciinema is useful when Claude-adjacent teams need a durable, text-based record of what happened in a terminal without shipping a large screen recording. It can capture a CLI demo, failed reproduction, pair-programming session, or agent run as an asciicast, then replay it locally, publish it to asciinema.org, embed it in docs, or stream the terminal live for reviewers.

Source notes

  • The official docs describe asciinema as a suite of tools for recording, streaming, and sharing terminal sessions.
  • The CLI manual describes asciinema CLI as a recorder/client for terminal sessions that stores lightweight .cast files, replays them locally, publishes them to an asciinema server, embeds them with the player, or streams sessions live.
  • The quick-start docs cover installation from common Linux, macOS, FreeBSD, Cargo, and release-binary paths, plus rec, play, upload, and stream workflows.
  • The GitHub repository is asciinema/asciinema, describes the project as a terminal session recorder, streamer, and player, and is GPL-3.0 licensed.

Duplicate check

Checked current content/tools/, content/mcp/, guides, skills, agents, open pull requests, live HeyClaude llms-full.txt, and repository-wide content for Asciinema, asciicast, asciinema.org, docs.asciinema.org, github.com/asciinema/asciinema, terminal session recorder, terminal recording, live terminal streaming, VHS, terminalizer, ttyrec, and scriptreplay. Existing AgentOps, Browserless, and Jam entries mention adjacent session replay concepts for agents, browsers, or feedback capture, but no dedicated terminal session recording tools entry, source URL duplicate, or open duplicate PR was found.

Disclosure

Editorial listing. No paid placement or affiliate link is used.

Source citations

Add this badge to your README

Show that Asciinema is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/tools/asciinema.svg)](https://heyclau.de/entry/tools/asciinema)

How it compares

Asciinema side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Field

Open-source CLI and web ecosystem for recording, replaying, live streaming, sharing, and embedding terminal sessions as lightweight asciicast files.

Open dossier

Lightweight, open-source coding agent from OpenAI that runs in your terminal, edits and runs code locally with configurable sandbox and approval modes, and authenticates with a ChatGPT plan or API key.

Open dossier

Open-source terminal coding assistant that edits files in Git repositories using chat-driven development loops.

Open dossier

Terminal-based agentic AI coding assistant from Charm that works with many LLM providers, uses LSP and MCP for context, manages per-project sessions, and asks permission before running tools by default.

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersoktofeesh1JPette1783JPette1783
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety · Privacy ✓ Safety ✓ Privacy ✓
BrandAsciinema logoAsciinemaOpenAI logoOpenAIAider logoAiderCrush logoCrush
Categorytoolstoolstoolstools
SourceSource-backedSource-backedSource-backedSource-backed
AuthorasciinemaOpenAIAiderCharm
Added2026-06-032026-06-052026-04-272026-06-05
Platforms
Harness
Source repo
Safety notesTerminal recordings can capture secrets, prompts, commands, file paths, hostnames, account names, API output, and generated code, so review and redact casts before publishing or embedding them. Live streaming exposes terminal output as it happens; use it only in approved environments and avoid production shells, private repositories, credentials, customer data, and destructive commands. Optional input and environment capture should be configured deliberately because it can record keystrokes, command context, and metadata that are more sensitive than the visible terminal output.Codex CLI runs as a local agent that can edit files and execute commands on your machine. It supports configurable sandbox and approval modes; keep approvals enabled and review proposed actions before allowing them. Lowering approval or sandbox restrictions lets the agent act more autonomously, increasing the risk of unintended changes. Review generated code and commands before running them against important repositories or systems.— missingCrush executes tools and commands; by default it asks for permission before each tool call. The --yolo flag skips all permission prompts; the project warns to be very careful with it, so avoid it on untrusted work. The crush.json config is trusted code — any $(...) in it runs at load time with your shell's privileges, so review config files before use. LSP and MCP servers can read your codebase and influence agent behavior; only connect servers you trust.
Privacy notesLocal `.cast` files can contain terminal output, timing data, window size, command metadata, titles, captured environment fields, and optionally keyboard input. Uploading or streaming through asciinema.org sends recordings or live terminal output to the public asciinema service unless visibility and sharing settings are reviewed first. Self-hosted asciinema servers still need access control, retention, backup, log, database, and upload-storage policies for recorded terminal sessions.Code and prompts are sent to OpenAI to power the agent under your ChatGPT plan or API key. Data handling follows OpenAI's policies for the plan or API you authenticate with; review them before processing sensitive code. API keys and account credentials should be stored securely and never committed to source control.Aider sends your prompts and the contents of selected repository files to your configured model provider (Anthropic for Claude); a provider API key is required.Your code context and prompts are transmitted to the LLM provider you configure. API keys are read from environment variables or config files and sent to the configured provider; store them as secrets. Crush records pseudonymous usage metrics tied to a device-specific hash; prompts and responses are never collected. Opt out with CRUSH_DISABLE_METRICS=1 or DO_NOT_TRACK=1.
Prerequisites
  • asciinema CLI installed from an official package manager, release binary, or reviewed source build.
  • Terminal workflow, CLI demo, pair-programming session, support reproduction, or AI-agent run that is safe to record.
  • Decision on whether recordings stay local, are shared through asciinema.org, are streamed live, or are hosted on a reviewed self-hosted asciinema server.
  • A ChatGPT plan (Plus, Pro, Business, Edu, or Enterprise) for plan-based sign-in, or an OpenAI API key.
  • Node.js and npm for the npm install, or Homebrew for the cask install.
  • A terminal on macOS, Linux, or Windows.
— none listed
  • An API key from a supported LLM provider such as Anthropic, OpenAI, or a compatible API.
  • A supported terminal on macOS, Linux, Windows (PowerShell or WSL), or BSD.
  • On Linux/BSD, clipboard helpers (wl-copy/wl-paste for Wayland or xclip/xsel for X11) for clipboard features.
Install
Config
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.