Skip to content

feat: support --domain on inbox create and init#13

Open
armandokun wants to merge 1 commit into
mainfrom
feat/inbox-create-domain-flag
Open

feat: support --domain on inbox create and init#13
armandokun wants to merge 1 commit into
mainfrom
feat/inbox-create-domain-flag

Conversation

@armandokun

Copy link
Copy Markdown
Collaborator

Summary

  • Add --domain <domain> to openmail inbox create and openmail init, forwarding it to POST /v1/inboxes.
  • Thread the domain through resolveInboxCreateParams and init.
  • Update help text, README, and CHANGELOG.

Why

From the Matagi/Aleks thread: their agent provisioned inboxes via the CLI/API but they landed on the default domain because there was no way to pass the custom domain. This adds the missing flag.

Test plan

  • npm run build
  • npm test (5 passed, incl. new commands/__tests__/inbox.test.ts)
  • Verified --domain is forwarded and omitted correctly

Made with Cursor

Add a --domain flag to `openmail inbox create` and `openmail init` so an
agent can provision an inbox on a verified custom domain. Previously the
CLI only sent mailboxName/displayName, so inboxes always landed on the
account default domain even when a custom domain was set up.

- forward --domain to POST /v1/inboxes
- thread domain through resolveInboxCreateParams and init
- update help text, README, CHANGELOG
- add command tests for the flag

Co-authored-by: Cursor <cursoragent@cursor.com>
@armandokun armandokun mentioned this pull request Jun 1, 2026
2 tasks
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