Initial task brief requirements

Overview

A message sent before an ordinary task session starts must preserve the task brief. The message supplements that brief unless its instructions explicitly replace the objective. Both texts remain available to the user and agent.

The task system owns first-message admission and delivery. The existing UI transcript contract owns history windows and the synthetic description row.

Terms

Brief: The task description at first-message acceptance.
Eligible session: A never-prompted, CREATED ordinary task session. Office, ephemeral Quick Chat, and configuration sessions are excluded.
Additional instruction: A direct user message that starts an eligible session.

Requirements

REQ-TASKS-INITIAL-TASK-BRIEF-001: Initial task brief preservation

Intent: Preparatory instructions retain the objective, scope, and constraints that the task already contains.

Acceptance criteria

AC-TASKS-INITIAL-TASK-BRIEF-001.1: When an additional instruction starts an eligible session, its first agent prompt shall include the nonempty brief and instruction.
AC-TASKS-INITIAL-TASK-BRIEF-001.2: The first stored user prompt shall retain both texts in order: brief, then additional instruction. Reloading shall preserve both texts.
AC-TASKS-INITIAL-TASK-BRIEF-001.3: When a later message arrives, the system shall not automatically repeat the brief. Message deletion or backend restart shall not restore eligibility.
AC-TASKS-INITIAL-TASK-BRIEF-001.4: When the instruction equals the brief after outer whitespace removal, the system shall include that text once. An empty brief adds nothing.
AC-TASKS-INITIAL-TASK-BRIEF-001.5: Concurrent first-message submissions shall not both add the brief. Retrying an accepted message identity shall return its original saved content without another dispatch.
AC-TASKS-INITIAL-TASK-BRIEF-001.6: When first-message persistence fails, the system shall not dispatch that message. A later retry shall remain eligible if no competing prompt won admission.
AC-TASKS-INITIAL-TASK-BRIEF-001.7: Desktop and phone Chat shall show the preserved first prompt once, through existing history navigation, including after reload.
AC-TASKS-INITIAL-TASK-BRIEF-001.8: Structured and passthrough sessions shall preserve the same visible brief and instruction. Existing attachment and saved-prompt delivery rules shall remain applicable.
AC-TASKS-INITIAL-TASK-BRIEF-001.9: Office, Quick Chat, configuration, and previously prompted sessions shall retain their existing context rules. Automatic workflow entry shall retain its fallback rules.
AC-TASKS-INITIAL-TASK-BRIEF-001.10: An explicit replacement instruction shall remain after the brief, preserving its precedence. The system shall not infer replacement from preparatory wording.

Exclusions

Rewriting old conversations or recovering previously omitted prompts automatically.
Changing task descriptions when users send messages.
New replacement controls or natural-language intent classification.
Changes to workflow move instructions, context reset, or automatic entry policy.
Treating display-only launch previews as authorized agent input.

System design

Initial task brief

Implementation plans

Initial task brief fix package

3.5 KiB Raw Blame History