Interface CoTPartialPrompt


public interface CoTPartialPrompt
Facilities for generating partial prompts with selected fragments omitted.

Purpose

When debugging CoT workflows, full prompts can be overwhelming?hundreds of kilobytes of UI summaries, DataSource schemas, action lists, and boilerplate obscure the specific logic being investigated. Partial prompts solve this by omitting irrelevant sections while preserving troubleshooting-relevant content.

Fragment Types

Prompts are composed of fragments that can be independently omitted:
  • Built-in fragments: goal, goalPrimer, history, historyPrimer, transitions, transitionsPrimer, errors, errorsPrimer, taskPrompt, introPrompt
  • Process fragments: entries from CoTProcess.optionalPrompts
  • State variables: Any state.* variable referenced in templates

Built-in Modes

Pre-configured modes target common troubleshooting scenarios. Pass a mode name to CoTProcess.getPartialPrompt():
  • taskPromptOnly - Debug task-specific prompt content
  • transitionDebug - Debug workflow transition logic
  • stateTracking - Track state variable changes
  • historyOnly - Focus on action history continuity
  • errorsOnly - Focus on validation/execution errors
  • minimal - Smallest useful prompt
  • noData - Omit large data, keep logic

Subclasses may define additional modes. Modes are resolved by looking for this.promptMode[ModeName] on the process instance.

Customizing Modes

Any mode can be customized via PartialPromptConfig.add and PartialPromptConfig.remove: