Skip to content

docs: document CC replies and the --cc / cc option#11

Open
armandokun wants to merge 1 commit into
mainfrom
docs/cc-replies
Open

docs: document CC replies and the --cc / cc option#11
armandokun wants to merge 1 commit into
mainfrom
docs/cc-replies

Conversation

@armandokun

Copy link
Copy Markdown
Collaborator

Summary

  • Document how agents should handle being CC'd on a thread: check deliveryRole and headerTo on inbound messages, reply to headerTo (not fromAddr) when copied, and note that OpenMail auto-CCs the original sender on thread replies.
  • Document the cc send option (API) and repeatable --cc flag (CLI).
  • Note that subject is optional when replying with threadId.
  • Updated across the threading concept, the OpenClaw integration, and the skill files (skill.md, skill-files/api.mdx).

Notes

Test plan

  • mint broken-links passes (verified locally)
  • Review the new "Replying when you're CC'd" section in concepts/threading.mdx

Made with Cursor

Explain how to handle being CC'd on a thread: check deliveryRole and
headerTo on inbound messages, reply to headerTo (not fromAddr), and how
OpenMail auto-CCs the original sender. Document the cc send option (API)
and --cc flag (CLI), plus that subject is optional on thread replies.
Covers threading concept, OpenClaw integration, and the skill files.

Co-authored-by: Cursor <cursoragent@cursor.com>
@mintlify

mintlify Bot commented Jun 19, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
openmail 🟢 Ready View Preview Jun 19, 2026, 12:50 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant