TL;DR

Follow-up to #60665 (closed by #69198): the merged PR added per-group systemPrompt for BlueBubbles, but the original ask explicitly requested "channel root, per-group, or per-DM" support. The DM case was silently dropped. This leaves BB asymmetric with Telegram and WhatsApp — both of which support direct.<id>.systemPrompt — and means BB DM users (the most common iMessage shape) cannot inject channel-aware behavioral instructions through config.

Current state (v2026.5.2)

Schema parity across plugins, verified from bundled-channel-config-metadata.generated.ts:

BB has no direct, dms, conversations, or chats config bucket at all — there's no place in the BB schema to attach per-DM behavioral config of any kind.

Why "use agent-level prompt customization instead" doesn't work

The merged PR's docs recommend agent-level customization for DMs:

"DMs ignore this field; use agent-level or account-level prompt customization instead."

Two problems:

1. Account-level doesn't exist either. channels.bluebubbles.accounts.<acct> has no systemPrompt field. The recommendation references config that isn't there.
2. Agent-level isn't channel-scoped. agents.defaults.systemPromptOverride and agents.list[].systemPromptOverride are global to the agent. Setting iMessage-style brevity rules at the agent level forces them on Slack, Discord, and every other channel the same agent serves.

So in practice, the only ways to inject per-DM BB behavior today are:

• Workspace-side soft prompts (rely on the model to remember to load a DNA file based on channel context — fragile)
• Hook-side message rewriting (requires custom code, defeats the purpose of having systemPrompt config)
• Spawning a dedicated agent per channel via bindings[] (heavy)

None of these are what the original feature request was meant to enable.

Proposed solution

Add one (or both) of:

A. channels.bluebubbles.direct.<chatGuid>.systemPrompt with "*" wildcard fallback, mirroring the existing Telegram and WhatsApp direct.<id>.systemPrompt pattern. This is the most direct symmetry fix and reuses the existing chatGuid/chatIdentifier/numeric-chatId matching strategy that's already implemented for groups in #69198.

B. channels.bluebubbles.accounts.<acct>.systemPrompt for an account-wide prompt that applies to every conversation (DM or group) on that account, matching the qqbot pattern. This would also make the merged PR's docs recommendation accurate.

Option A alone closes the gap symmetrically with Telegram/WhatsApp. Option B is a nice complement for users who want a single account-wide prompt without per-conversation tuning. Implementing both gives the same flexibility users already have on the most-similar channels.

References

• Original feature request: #60665 (closed by partial fix in #69198)
• Merged PR: #69198 — added groups-only systemPrompt
• Telegram/WhatsApp precedent: direct.<id>.systemPrompt already implemented and documented
• QQBot precedent: accounts.<acct>.systemPrompt already implemented
• Docs claiming a workaround that doesn't exist: docs/channels/bluebubbles.md "DMs ignore this field..." paragraph (added in #69198)