Skip to content

feat: add --cc flag and make --subject optional on thread replies#18

Open
armandokun wants to merge 1 commit into
mainfrom
feat/cc-support
Open

feat: add --cc flag and make --subject optional on thread replies#18
armandokun wants to merge 1 commit into
mainfrom
feat/cc-support

Conversation

@armandokun

Copy link
Copy Markdown
Collaborator

Summary

  • Add a repeatable --cc <email> flag to openmail send, threaded through the HTTP client for both JSON and multipart (attachment) sends.
  • Make --subject optional when --thread-id is set — the thread's subject is reused (matching the API), and still required for new threads.
  • Update the OpenClaw skill output to document CC-reply handling: check deliveryRole/headerTo on inbound messages and reply to headerTo when you were CC'd.

Notes

  • The API already supports cc; this brings the CLI in line.
  • Pure addition — no change to existing send behavior when --cc/--thread-id are not used.

Test plan

  • openmail send --to a@b.com --subject Hi --body Hello (new thread, unchanged)
  • openmail send --to a@b.com --body "reply" --thread-id <id> (no subject required)
  • openmail send --to a@b.com --subject Hi --body Hello --cc c@d.com --cc e@f.com (multiple CC)
  • openmail send ... --cc c@d.com --attach file.pdf (CC + multipart)
  • npm run build passes

Made with Cursor

Support copying additional recipients with a repeatable --cc flag, wired
through the HTTP client for both JSON and multipart sends. Subject is now
optional when --thread-id is set, since the thread subject is reused.
Document CC-reply handling (deliveryRole/headerTo) in the skill output.

Co-authored-by: Cursor <cursoragent@cursor.com>
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