From f55c2ba4d052db52a2aa70c7779028f8228066c5 Mon Sep 17 00:00:00 2001 From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com> Date: Wed, 1 Oct 2025 15:00:36 +0000 Subject: [PATCH] backport of commit 3b9ac7b907de3f245a4b5491ffb2009fe6c05dca --- website/content/docs/session-recording/index.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/content/docs/session-recording/index.mdx b/website/content/docs/session-recording/index.mdx index 55d1eb0706..cfa33b3938 100644 --- a/website/content/docs/session-recording/index.mdx +++ b/website/content/docs/session-recording/index.mdx @@ -81,7 +81,9 @@ Be careful when you use Secure File Copy (SCP) to transfer large files during a ## asciicast When you view recorded sessions using the CLI or Admin UI, Boundary can convert the recording into other formats for playback. -Currently Boundary supports converting the recording of an individual SSH channel into an [asciicast](https://github.com/asciinema/asciinema/blob/develop/doc/asciicast-v2.md) format to play back an interactive SSH session. +Currently Boundary supports converting the recording of an individual SSH channel into an asciicast format to play back an interactive SSH session. + +Refer to the [asciinema documentation](https://docs.asciinema.org/) for more information about the [asciicast](https://docs.asciinema.org/manual/asciicast/v3/) format. ### Limitations