Repository navigation
Replies: 2 comments
|
Thanks for the proposal. Here's where I land. Static extra headers: yes, in core. Several gateways need a second header besides the provider key (Cloudflare AI Gateway's
Scoped session/flow identifiers: not for now. Without a concrete gateway that needs them, I'd rather not define what identifies a MailFlow user or task to a third-party gateway. If you have a specific gateway and header that requires per-flow grouping, name it and show the request shape, and I'll look at it as a separate change. Plugin extension point: no. MailFlow's plugins are frontend-only today, so a backend hook would be a much larger change than the feature itself. I'll implement the static headers in main and post the commit here when it lands. |
|
Landed in a4a7783. Settings > AI Assistant now has Extra request headers for the API-key connection, up to 10:
It ships in the next release. |
Uh oh!
There was an error while loading. Please reload this page.
Would configurable request headers for an AI provider be appropriate upstream, including optional scoped session/flow placeholders for self-hosted AI gateways?
Some OpenAI-compatible gateways need an additional routing/auth header, and need requests from one MailFlow task to share an identifier without accidentally sharing another user's session. Proposed behavior: per-provider header configuration, encrypted stored values, redacted readback, validation against unsafe/reserved headers, and server-derived scoped identifiers. No browser session cookie or secret should be forwarded as an identifier.
This is a feature proposal, not a clean-upstream bug. A fork prototype exists with configuration, isolation and redaction tests: https://github.com/shady2k/mailflow/tree/integration/upstream-20261014 . It should be discussed and split into a focused change before any PR. Would a plugin extension point be preferable to core configuration?
All reactions