Why is the Resend API key treated as a global config rather than a per-repo requirement?

[alexanderbnelson]

I’m working across multiple projects that each use different Resend accounts, and I’m running into friction with the current approach of relying on a globally set RESEND_API_KEY through the CLI.

In practice, this makes it easy to accidentally point the wrong project at the wrong Resend account, and it doesn’t scale well once you’re managing more than one integration.

Would it make sense to require RESEND_API_KEY at the repository level instead, or allow the integration to explicitly accept a key via configuration? I’m curious if there’s a design reason behind the current approach, or if this is something that could be revisited to better support multi-account workflows.

Happy to provide more context if helpful.