Claude Code sessions in Warp are a single block, making partial copy difficult

[shungo11260]

Summary

When using Claude Code in Warp, the entire interactive session is treated as a single block, which makes partial copy and paste difficult.

Problem

I often need to copy only a specific answer or snippet from a long Claude Code session. Because the whole session is one block, selecting only the needed range is cumbersome and error prone.

Expected behavior

• Interactive CLI agent sessions such as Claude Code can be segmented into smaller units, for example per turn or per response.
• Or Warp provides a dedicated copy workflow that makes partial extraction from very long single blocks reliable and fast.

Actual behavior

• A full Claude Code run is grouped into one block.
• Extracting only the relevant part requires manual selection in a long output area and often causes mis selection.

Reproduction steps or desired workflow

1. Run claude in Warp.
2. Continue the conversation for many turns.
3. Try to copy only one specific response from the middle of the session.
4. Observe that the single large block makes this significantly harder than turn level selection.

Artifacts

None attached

Warp version

Unknown

Operating system

macOS

[oz-for-oss]

@shungo11260

Here's what I found while triaging this issue:

This appears to be an enhancement request: Warp currently groups a long-running interactive CLI command like claude into one block, so reliable per-response copying would likely need turn-aware segmentation or a dedicated copy workflow.

Maintainer details

I concluded that claude Code partial-copy pain appears to be a UX enhancement around turn-level segmentation or copy affordances for long-running interactive CLI agent blocks..

Triage

This looks like a feature request / UX gap rather than a Claude Code execution bug. The reporter wants a reliable way to copy one response or snippet from the middle of a long claude session, but Warp currently presents that long-running interactive command as one terminal block.

Reproducibility

High. The steps are plausible from the report and match the current architecture: command blocks are created around shell lifecycle boundaries, so a multi-turn interactive process remains one block until it exits.

Likely implementation area

The likely change is in terminal block/session handling and copy/selection UX. app/src/terminal/model/blocks.rs creates/restores command blocks, app/src/terminal/model/blocks/selection.rs and app/src/terminal/view.rs turn selections into copied text, and app/src/terminal/cli_agent_sessions/* plus app/src/terminal/cli_agent_sessions/plugin_manager/claude.rs track Claude Code session events. Today those structured agent events update session status/context, but do not create per-turn terminal blocks or a dedicated per-response copy affordance.

Duplicate check

A repository-wide scan of open non-PR issues found related copy/selection or block requests such as #8540, #10353, #1017, #3075, and #820, but they target different problems (formatting/whitespace, TUI selection mode, generic copy escape hatches, broad block features, or scrolling). Fewer than two issues matched this specific Claude Code single-block partial-copy request, so I am not marking this as a duplicate.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz