email

claudex:email — broadcast a brainstorm question to your panel

Send-only. Emails the current question + a short context snapshot to a panel defined in ~/.claude/claudex/panel.json, so people can read it on their own device during a screen-shared meeting and respond by email or aloud. It does NOT collect, match, or summarize replies, and does NOT change claudex:think.

Canonical invocation: /claudex:email [filter]. Replies land in the connected Gmail account and are not monitored live.

Step 1 — Parse panel (true fail-fast)

Read ~/.claude/claudex/panel.json. If it is missing or does not parse, STOP and tell the host to create/fix it. Recipients are parsed from data.panel.members; the members array is nested under the top-level panel key. Minimal required shape:

{
  "panel": {
    "members": [
      { "name": "Name", "email": "[email protected]", "role": "student", "include": true }
    ]
  }
}

If panel.members is missing or is not an array, treat it as a panel schema error and STOP before drafting. This is the only hard stop before drafting — everything else still produces a draft you can fall back to.

Step 2 — Resolve recipients

Resolve recipients only from data.panel.members plus any validated ad-hoc email tokens.

• No argument: every member with include: true.
• Argument contains a token with @: strip surrounding angle brackets, commas, semicolons, and whitespace from each such token; lowercase the domain; then validate it against a conservative email regex such as ^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,}$. If any @ token is not a valid email, STOP and list the rejected tokens. Valid ad-hoc emails are combined with any other (non-@) filter tokens.
• Other tokens (case-insensitive):
  • professor/professors → role: professor; student/students → role: student.
  • Name tokens (e.g. florescu bozdog) match against name. Multiple tokens are OR — florescu bozdog resolves to BOTH people, not one person matching both.
• NEVER select a member with include: false unless explicitly named in the argument.
• Each selected member from panel.members must have non-empty string name, email, and role fields plus a boolean include field. If any selected member fails this validation, STOP. If any selected member lacks a valid email, show which selected member is invalid.
• Deduplicate the final recipient list by normalized lowercased email before preview, send, and log. Show the unique recipient count.
• If zero recipients resolve, STOP and show what matched / was excluded.