Keep objects, data, and operation status consistent with the tool service. Make the active object and progress clear.
Keep frequent actions and main results easy to find. Adapt to the available workspace. Use readable controls, text descriptions for status, and a usable keyboard and focus order.
Define the source of truth for the active resource, selection, and operation progress. A response from an old request must not overwrite a newer selection. Display completion only after the tool confirms success. On service failure, keep the last valid state and explain the cause and available next action.
Distinguish loading, empty data, failure, cancellation, and completion. Explain the next available action after failure. Distinguish stopping the interface wait from stopping the background task, and report the result of each.
Explain service authorization. Before an operation that requires confirmation, describe its target and effects and wait for confirmation. Explain how to resolve insufficient permissions.
If a local global app has the required file capability, let the user choose which files to add to the chat draft and review the attachments before sending. When requesting a foreground or background task, explain the work and whether the task will open in the foreground or run in the background, then wait for the user’s permission. If the app requests a series of tasks, respect the user’s choice to stop the remaining requests.
Quickstart · Interaction checklist · Plugin specification
| Part | Responsibility |
|---|---|
| Interface | Present results and accept selections, input, and actions |
| Tools and services | Query data, perform operations, and return results |
| Configuration and resources | Provide client entry points and dependencies |
| Conversation and instructions | Explain how to open the interface, interpret results, and continue |