SeaShell Gmail copy messaging produces clean, email-ready text from an assistant response, stripping terminal noise and markdown that does not belong in email so technical summaries, status updates, and code explanations paste clearly into a Gmail compose window. You trigger it with the /copy-as-gmail command or the Copy for Gmail action on an assistant message in 2026.
Email-ready by default
Pasting raw AI output into an email leaves markdown artifacts that make an update look unpolished. The Gmail target shares a plain-text core that removes those artifacts before the text reaches your clipboard.
Headings, emphasis markers, and terminal-only formatting are stripped where they would hurt readability, while the substance of the message stays intact. What lands in the compose window reads like an email you wrote, not a transcript you dumped.
Designed for async updates
Use it to turn implementation plans, bug explanations, and release notes from a terminal session into readable stakeholder email.
Code remains readable as text so technical detail survives, while the formatting is calm enough for a non-terminal audience. It closes the gap between where the work happens and where it gets reported.
Same interaction model as Slack copy
The Gmail action is available through /copy-as-gmail and the assistant message menu, matching the Slack copy flow exactly.
Both targets read from the same copy-format action list, so the interaction is identical and only the output format differs. The current Gmail target produces clean text for clipboard paste; rich Gmail draft API support is a later phase.
Frequently asked questions
- What does Copy for Gmail do?
- It formats an assistant response as clean plain text for email, keeping the content readable when pasted into a Gmail compose window.
- Does Gmail copy preserve code?
- Yes. Code stays readable as text, while markdown syntax and terminal-only formatting are removed where they would hurt email readability.
- Is rich Gmail formatting supported?
- The current Gmail target produces clean text for clipboard paste. Rich Gmail draft API support is a later phase.
- How is it different from Slack copy messaging?
- It shares the same interaction model and action list, but outputs clean email text instead of Slack mrkdwn.
Try SeaShell in your terminal
The terminal-native AI coding agent. Free core, single binary.
Install SeaShellRelated guides
Atlas with Llama 3.3 70B Instruct (Meta Llama API) in 2026
Drive Atlas with Llama 3.3 70B Instruct (Meta Llama API) in 2026. Leverage its 128,000 token context and near-405B instruction quality for coding tasks.
Atlas with Claude Sonnet 5: Your 2026 Workhorse for AI-Powered Coding
Drive Atlas with Claude Sonnet 5, Anthropic's 2026 workhorse. Get 1M token context for $2/$10 per Mtok, ideal for long, agentic coding sessions in your terminal.
Atlas vs Tabby: Terminal AI Coding Agents in 2026
Comparing Atlas and Tabby in 2026: Atlas offers terminal-native AI with explicit planning and diffing, while Tabby provides self-hosted GPU-based completion and a cloud agent.
Atlas for Groovy: A Terminal-Native AI Coding Agent for Gradle, Spock, and Jenkins in 2026
Atlas is a terminal-native AI coding agent for Groovy in 2026. It reads build.gradle closures and Jenkinsfiles, writes Spock specs, runs ./gradlew test, and applies Spotless.
Atlas with Gemini 3.1 Pro in 2026
Explore Atlas with Gemini 3.1 Pro, Google's frontier model. Leverage its 1M token context window and $2/Mtok input pricing for powerful, cost-effective AI coding in 2026.
Atlas with Qwen3 Coder Flash in 2026
Drive Atlas with Qwen3 Coder Flash in 2026 for rapid, cost-effective coding. Leverage its 1M token context and $0.30/Mtok input for fast edit-run-fix loops.
Atlas with GPT-5.6 Terra (2026)
Drive Atlas with GPT-5.6 Terra in 2026. This OpenAI model offers a 1.05M token context window and balanced pricing ($2.50/$15 per Mtok) for deep reasoning tasks.
Atlas for Gin in 2026
Atlas is a terminal-native AI coding agent for Gin in 2026. It reads router groups and binding tags, then runs go test ./... -race behind a permission prompt.