Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat(replay): Add session replay commands to CLI

Open
#481 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
api, cli

Research direction

Start by reading the existing sentry span and sentry trace CLI commands to understand the project’s command patterns, then inspect the Sentry Replays API. Done means the CLI provides replay list and view commands that support scripted and bulk workflows.

Written by the indexing model from the issue text.

Description

Summary

The CLI currently has no support for session replays. There is value in a dedicated CLI approach for replays — particularly for agent/automation use cases where you can pull down large sets of replays and run bash pipelines over them — that the MCP server does not yet support well.

Current Behavior

Session replay data is only accessible via the Sentry web UI or through the MCP server. There is no way to list, download, or inspect replays programmatically from the CLI.

Gap

  • MCP is limited in bulk/batch replay workflows; a CLI approach enables scripting and piping (e.g., download lots of replays, run bash commands over them)
  • No prior art in getsentry/cli for replay commands

Options

  1. CLI-native replay commands — Add sentry replay list and sentry replay view commands backed by the Sentry Replays API, following the existing patterns for sentry span, sentry trace, etc.
  2. MCP only — Extend the MCP server instead; but bulk operations and bash pipelines are harder to express there
  3. Both in parallel — CLI for automation/scripting, MCP for interactive agent flows

Recommendation

Build CLI-native replay commands in parallel with any MCP experimentation. The CLI unlocks bulk pull-down and composable scripting that MCP cannot easily provide today.

Action taken on behalf of Miguel Betegón.

Dominant language
TypeScript
Stars
121
Forks
14
Avg merge
22h 3m
Merged PRs (30d)
94

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/cli

All issues in getsentry/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.