Files
deepseek-harness/snapshots/web/subagent-interrupt/offline-composer.expected.md
T
_KermanandTianyi Cui fb79a944f5 refactor(llm): separate durable producer sources from request inputs
Give durable user context its producer-owned source kind instead of a generic plugin wrapper. The V3-to-V4 conversion preserves the frozen rename and collision rules, all own JSON metadata, event coordinates, and historical request-only kinds. Native catalog and JSONL admission retain source validation so unknown attribution can survive without its producer while malformed owned sources are refused.

Use an explicit user-only RequestUserInput for auxiliary LLM prompts that do not own durable message identity. Auto Review and compaction remove their request-only source registrations while retaining prompt content and freezing; provider serializers and projections keep the same wire data, assistant replay isolation, image ordering, and tool correlation. Session writes, Agent delivery, and recorded title requests continue to require identified durable messages.

Bind the saved compatibility policy only to user sources and qualify tmux location attribution without weakening fixed system, model, or tool semantics. Rebuild the current inventory and unpublished V4 acknowledgement on the actual tool-role parent, preserving its rationale and all accepted historical records. The catalog format version records tooling metadata; Session remains V4. Developer-role policy and activation belong to their own feature.

The latest-master Messages adapter, serialization, request-input typing, EpochHeader reservation, and attribution checks pass 103 tests across five files. The retained V3 Messages input-history snapshot passes through the source profile; Host/Client typechecks and all 41 documentation gates pass. The generated comparison records four changed roots and 447 unchanged type fingerprints. Latest-master ARIA changes are retained, with producer source labels applied independently; new Messages fixtures retain their producer names as declared source kinds and use the fixed system-message helper; recorded Session generations are unchanged by this regrouping.

Co-authored-by: Tianyi Cui <[email protected]>
2026-09-18 19:07:12 +08:00

1.4 KiB

  • banner:
    • navigation "Session hierarchy":
      • button "Ask a research subagent to"
      • text: /
      • 'button "Switch subagent: event-sourcing researcher"': event-sourcing researcher
    • text: Standard mode
    • button "More actions"
    • button "Open right sidebar"
    • tablist:
      • tab "Chat" [selected]
      • tab "Trajectory"
  • button "System prompt"
  • text: "Explain event sourcing in one sentence.Your parent agent id is "session-{{uuid}}". Before you finish, send your result to that agent with send_message({ agent_id: "session-{{uuid}}", message: "" }). The parent shares your workspace but does not automatically receive your transcript, tool output, or reasoning. Send earlier messages as well when a finding changes what the parent should do next; sending a message does not end your turn. {{clock}}"
  • button "Copy"
  • button "Context injection runtime-context"
  • paragraph: partial
  • status: Deep diving...
  • list:
    • listitem:
      • text: Keep working until I stop you again.
      • button "Edit queued message"
      • button "Remove queued message"
      • button "Steer queued message"
  • textbox "Parent session offline; sending is unavailable but you can still stop the run" [disabled]
  • button "Add files or run commands" [disabled]
  • 'button "Access mode, current: Custom" [disabled]': Custom
  • button "Stop generating"
  • button "Send message" [disabled]