Affected area
Model routing / providers
Problem or use case
Users need a clearer way to configure system prompts for different models and a unified user-level system prompt. The original report notes that the current visible input can only approximate this behavior and has a limited character count.
Original context:
Proposed behavior
Add support for configuring system prompts at both the model level and the user level. The configuration should allow longer prompt content, make precedence clear when both model-level and user-level prompts exist, and apply the selected prompt consistently when a conversation is created or sent to a model provider.
Alternatives considered
Using the current limited input field as a workaround, but it does not provide enough capacity or clear per-model/user-level behavior.
Compatibility, deployment, or migration impact
Configuration changes: May require new user preference or model configuration fields.
API changes: Conversation creation or model invocation APIs may need to include resolved system prompt behavior.
Database migrations: May be needed if prompts are persisted per user or per model.
Deployment changes: None identified in the original report.
Backward compatibility: Existing conversations should keep their current behavior unless a system prompt is explicitly configured.
Documentation or API contract impact
Document system prompt configuration, precedence rules, and any API or admin-console behavior changes.
Pre-submit checklist
Affected area
Model routing / providers
Problem or use case
Users need a clearer way to configure system prompts for different models and a unified user-level system prompt. The original report notes that the current visible input can only approximate this behavior and has a limited character count.
Original context:
Proposed behavior
Add support for configuring system prompts at both the model level and the user level. The configuration should allow longer prompt content, make precedence clear when both model-level and user-level prompts exist, and apply the selected prompt consistently when a conversation is created or sent to a model provider.
Alternatives considered
Using the current limited input field as a workaround, but it does not provide enough capacity or clear per-model/user-level behavior.
Compatibility, deployment, or migration impact
Configuration changes: May require new user preference or model configuration fields.
API changes: Conversation creation or model invocation APIs may need to include resolved system prompt behavior.
Database migrations: May be needed if prompts are persisted per user or per model.
Deployment changes: None identified in the original report.
Backward compatibility: Existing conversations should keep their current behavior unless a system prompt is explicitly configured.
Documentation or API contract impact
Document system prompt configuration, precedence rules, and any API or admin-console behavior changes.
Pre-submit checklist