Skip to main content

QuickCard Input Presets

Overview​

QuickCard system functions are input prefill entries. A system function targets an agent and owns one or more input presets. When a user clicks a system function, the UI selects the target agent and shows the preset list on the current page or the target page.

Input presets do not send messages directly. They only update the input draft and input controls. ChatInput remains the single place that sends the final message.

Data Model​

System functions are still stored under the quick_launch_functions system config key. Each function uses input_presets to describe presets that can be applied to the input:

{
  "id": "code_review",
  "title": "Code Review",
  "team_id": 7,
  "enabled": true,
  "order": 10,
  "input_presets": [
    {
      "id": "review_change",
      "title": "Review Change",
      "prompt": "Please review the current code change",
      "source_attachment_ids": [101],
      "options": {
        "enable_deep_thinking": false,
        "enable_clarification": true,
        "force_override": true,
        "selected_skill_names": ["code-review"]
      }
    }
  ]
}

Legacy quick_phrases config is migrated to input presets when read. Saves emit input_presets.

Launch Flow​

Cross-page launches use a one-time launch intent in the URL:

  • teamId: target agent ID
  • quickLauncher: system function or favorite agent key
  • quickPreset: optional preset ID to apply directly
  • showPresets=1: show the current function's preset list after entering the target page

The target page clears these query parameters after reading the intent. After cleanup, the URL no longer continuously controls agent selection, so the user can clear or switch the selected agent.

Supported Input Options​

Input presets currently support these stable, serializable input options:

  • prompt: input text
  • enable_deep_thinking: deep thinking toggle
  • enable_clarification: clarification toggle
  • force_override: force model override toggle
  • selected_skill_names: skill names preselected for this input
  • source_attachment_ids: source attachment IDs configured for the preset

Repositories, branches, and user contexts are intentionally excluded from system function configuration. They depend on the user's environment, permissions, or current task state, so they are not suitable as global system presets.

Preset Attachments​

System function presets can include attachments. When an administrator uploads a file in the system recommendation configuration, the frontend stores the attachment ID returned by the upload API in source_attachment_ids. This ID is the source attachment in the administrator configuration and is not sent directly as a user message attachment.

When a user applies the preset, the frontend calls /api/users/quick-launch/prepare-preset. The backend verifies that the target system function and preset are enabled, copies every attachment in source_attachment_ids into a temporary attachment owned by the current user, and returns the new attachment IDs. This keeps message attachments user-owned even when the configured source attachment belongs to an administrator or system account.

Preset attachments must be visible in the input so users know which files will be sent. If the user uploads their own attachment, the frontend removes attachments brought in by the preset first. The backend also has a fallback during attachment ownership validation: when one message contains both normal attachments and QuickCard preset attachment copies, only the normal attachments are kept.