01Choose
Match the tool to the amount of ceremony you need.
| Situation | Best first move |
|---|---|
| The latest Claude response is already correct. | Run /copy. |
| You need the full session as a record. | Use Claude Code’s conversation export workflow. |
| You need one reply, summary, command set, or update from a noisy session. | Ask Claude to extract and save one artifact. |
| You need revisions, provenance, secret review, projects, tags, or destination formatting. | Use DraftRelay. |
Avoid adding a storage system to a one-second copy task. Also avoid copying an entire terminal buffer merely because the useful answer is hard to select.
02Native copy
Start with /copy.
In Claude Code, run /copy to copy the most recent assistant response. Paste it into a scratch area and inspect it before sending. This keeps the workflow inside Claude Code and avoids creating another saved item.
Native copy is less useful when the response contains commentary you do not want, when the desired text appeared earlier, or when the result needs a different shape for Slack, email, or a pull request. In those cases, ask Claude to produce a final version first instead of manually trimming a large selection.
03Extract
State what the clean artifact must include and exclude.
Extract the final client response from this session. Keep it under 150 words, use complete sentences, include the decision and next step, and remove internal implementation details. Save only that reply to DraftRelay under Acme, tagged renewal.
Claude composes the artifact and calls save_output. DraftRelay does not read the terminal or decide which lines matter on its own. That constraint is useful: the handoff remains an explicit part of your request.
04Review
Check meaning before formatting.
- Read the artifact as the recipient.Make sure it is self-contained and does not refer to unseen terminal context.
- Verify names, numbers, links, and claims.Provenance is useful context, not automatic proof.
- Resolve safety findings.Remove secrets rather than relying on a warning to protect them.
- Choose a destination version.Preview the Slack, email, GitHub, Markdown, or plain-text representation.
- Copy and paste manually.Review the final target once more, especially mentions and links, before sending.
05Prompt patterns
Make the finish condition concrete.
- Reply: “Save only the final reply; exclude analysis and internal notes.”
- Summary: “Save five bullets: outcome, evidence, risk, blocker, next action.”
- Commands: “Save copy-safe commands with working directories and a warning before destructive steps.”
- Status update: “Write for Slack, lead with the result, and separate verified facts from next steps.”