# Development

**URL:** https://discourse.asciinema.org/c/development/10.md

[Latest](https://discourse.asciinema.org/latest.md) · [Categories](https://discourse.asciinema.org/categories.md) · [Tags](https://discourse.asciinema.org/tags.md)

---

## [About the Development category](https://discourse.asciinema.org/t/about-the-development-category/776)

<div class="topic-metadata">

**Author:** [@ku1ik](https://discourse.asciinema.org/u/ku1ik)\
**Replies:** 0

</div>

This category is for topics related to hacking on asciinema: submitting pull requests, configuring development environments, coding conventions, and so forth.

---

## [PR for adding inline image rendering to asciinema player](https://discourse.asciinema.org/t/pr-for-adding-inline-image-rendering-to-asciinema-player/1064)

<div class="topic-metadata">

**Author:** [@deeplook](https://discourse.asciinema.org/u/deeplook)\
**Replies:** 0\
**Last updated:** [February 17, 2026, 12:49pm UTC](https://discourse.asciinema.org/t/pr-for-adding-inline-image-rendering-to-asciinema-player/1064 "2026-02-17T12:49:47Z")

</div>

I have created this PR about supporting images in asciinema-player. Mentioned before here: Playback support for terminal graphics (iTerm inline images protocol)? - #5 by deeplook . Comments welcome.

---

## [Testing the new Rust version of the asciinema CLI](https://discourse.asciinema.org/t/testing-the-new-rust-version-of-the-asciinema-cli/778)

<div class="topic-metadata">

**Author:** [@ku1ik](https://discourse.asciinema.org/u/ku1ik)\
**Replies:** 12\
**Last updated:** [August 27, 2025, 2:59pm UTC](https://discourse.asciinema.org/t/testing-the-new-rust-version-of-the-asciinema-cli/778 "2025-08-27T14:59:16Z")

</div>

Next major version of the asciinema CLI is a rewrite in Rust, and since this is a new codebase, we need to test it thoroughly on many systems and environments. It’s still in a work-in-progress shape, but reports of succe…

---

## [CORS issue using s3 with self hosted instance](https://discourse.asciinema.org/t/cors-issue-using-s3-with-self-hosted-instance/800)

<div class="topic-metadata">

**Author:** [@botch](https://discourse.asciinema.org/u/botch)\
**Replies:** 1\
**Last updated:** [March 7, 2024, 9:38am UTC](https://discourse.asciinema.org/t/cors-issue-using-s3-with-self-hosted-instance/800 "2024-03-07T09:38:08Z")

</div>

I self-hosted asciinema on fly.io, set the s3 env variables, recording and uploading works. Playing the cast gives me this emoji :boom:. The issue? Well, in the console, it says it’s a CORS problem. Access to fetch at '…

---

## [Preview of the new upload behavior in asciinema CLI 3.0](https://discourse.asciinema.org/t/preview-of-the-new-upload-behavior-in-asciinema-cli-3-0/780)

<div class="topic-metadata">

**Author:** [@ku1ik](https://discourse.asciinema.org/u/ku1ik)\
**Replies:** 1\
**Last updated:** [December 26, 2023, 7:52pm UTC](https://discourse.asciinema.org/t/preview-of-the-new-upload-behavior-in-asciinema-cli-3-0/780 "2023-12-26T19:52:11Z")

</div>

The change from 2.x is that it now requires opt-in / confirmation to use asciinema.org as the default asciinema server. The server URL configuration step lets you enter your own self-hosted asciinema server URL. Also…