open-webui / open-webui/computer

feat: configurable system prompt for messaging-gateway chats

Open
#257 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
569
Forks
79
PR merge metrics
No merged PRs in 30d

Description

feat: configurable system prompt for messaging-gateway chats

Feature description

Conversations routed through messaging gateways (Discord, WhatsApp, Telegram)
use the same base system prompt as local chats. It would be useful for admins
to customize the persona/instructions for gateway conversations separately —
for example, shorter or more notification-style answers suited to chat apps.

Proposed solution
  • A gateway.system_prompt config (editable in the Gateway settings tab) that replaces the base system prompt for conversations with a gateway bridge id in their meta.
  • When the override is set, skip the base-template resolution but keep all augmentation (memory, AGENTS.md instructions, skills, context) so gateway chats still behave like full agent chats.
  • Empty config = zero behavior change (default).
Additional context

Implemented on a fork; can share implementation notes.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how gateway bridge IDs are identified in conversation metadata, how the base system prompt is resolved, and where the Gateway settings tab reads configuration. Done means an optional gateway.system_prompt replaces only the base prompt for gateway chats, preserves memory, AGENTS.md, skills, and context augmentation, and leaves behavior unchanged when empty.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.