Skip to content

[Feature]: Add copy/export actions for ZeroCode session transcripts #10299

Description

@Audacity88

Summary

Add explicit ZeroCode actions to copy the last assistant message and export or copy the current session transcript.

Problem statement

#10141 reports that ZeroCode makes code snippets easy to copy, but does not give an equally direct way to copy the last message or export a whole session. That makes session recovery and handoff awkward when a user needs to preserve the useful part of a conversation instead of individual code blocks.

Existing related issues cover text selection and transcript interaction details, including #10051 and #10086. This issue is the session-level copy/export slice from #10141.

Proposed solution

Add discoverable actions in ZeroCode for:

  • copying the last assistant message;
  • copying the current session transcript;
  • exporting the current session transcript to a file or other supported destination.

The first implementation should preserve existing code-block copy behavior and avoid changing stored session ownership or retention policy.

Non-goals / out of scope

This does not cover session archiving/deletion controls from #8894, session rewind/fork behavior from #9020, or web-dashboard session browsing from #7543.

Alternatives considered

Users can currently copy individual snippets or select visible text, but that does not cover full-session export or quick last-message handoff.

Acceptance criteria

  • ZeroCode exposes a clear copy-last-message action.
  • ZeroCode exposes a clear copy or export action for the current session transcript.
  • Exported content preserves message ordering and role attribution.
  • Existing code-block copy controls continue to work.
  • Manual or automated coverage verifies at least one non-trivial transcript.

Architecture impact

Likely affects ZeroCode transcript rendering/actions and the runtime/session transcript read path.

Risk and rollback

Risk is medium because transcript export can expose more session content than single-message copy. Rollback is to remove the new actions and keep existing snippet-level copy behavior.

Expected routing

Could become contributor-ready after maintainer scoping

Next decision surface

Use #10141 as the parent umbrella and #9010 for ZeroCode hardening coordination.

Breaking change?

No

Data hygiene checks

  • I removed personal/sensitive data from examples, payloads, and logs.
  • I used neutral, project-focused wording and placeholders.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestfollow-upCarved-out follow-up scope from a parent PR or issue.priority:p2Medium priorityrisk:mediumOrdinary behavioral change without a high-impact boundary.zerocodeAuto scope: apps/zerocode/** changed.

    Type

    No type

    Projects

    Status
    Backlog

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions