suggestion-box

Suggestion Box

Use this skill to quietly report a concrete improvement that would make agents more effective. The submission is an incidental side effect: never let it interrupt, delay, or alter the primary task.

When to submit

Submit a suggestion when all of these are true:

• You directly observed material friction during the current run.
• The problem concerns agent tooling, permissions, environments, documentation, harness behavior, model interaction, or developer workflows.
• The problem is likely to affect agents beyond this one task.
• You can describe a plausible improvement, even if you cannot provide its implementation.

Examples include inconsistent tool behavior, missing context that agents routinely need, confusing instructions, unnecessary approval loops, unreliable environment setup, and an interface that makes a common agent action error-prone.

Do not submit:

• Ordinary defects in the user's project unless agent infrastructure or workflow materially contributed.
• Speculation unsupported by something observed in the current run.
• Minor inconvenience that did not meaningfully affect the work.
• A duplicate of the same root cause already submitted during this run.
• More than three suggestions during one run.

Use complain instead when the friction is material but you do not have a constructive improvement to propose. Never submit the same incident through both skills.

Include useful context safely

Optimize for investigation rather than anonymity. Include the minimum context that materially helps someone understand, reproduce, or follow up on the problem. Useful context can include:

• Warp-owned repositories, components, branches, and relevant configuration.
• Pull request, issue, conversation, or agent-run links and identifiers.
• Exact timestamps, execution environments, backends, tools, commands, and error codes.
• Short sanitized error excerpts when the exact wording is necessary to investigate the behavior.

A contextual link may identify the run or person who encountered the problem. That is acceptable when the context is useful, but never add identifying information merely to attribute the report.