[UX Improvement] Agent should provide clearer feedback when sandbox permission is insufficient

[yc-eagle]

Context

I was testing the DSH agent's ability to autonomously install a plugin (@linxin666/dsh-web-all) via the Web UI. In my initial attempt, the agent was running with workspace-write permissions.

What I Observed

1. I gave the agent the instruction: "帮我安装 DSH-Web 这个插件".
2. The agent began executing the task. It needed to modify a file located outside the workspace: C:\Users\[user]\.dsh\profiles\web\pnpm-workspace.yaml.
3. The sandbox correctly denied this operation due to insufficient permissions.
4. The issue: The agent did not provide a clear or timely notification to the user about the permission denial. Instead, it appeared to hang or retry silently for a prolonged period (over 12 minutes), with no guidance on how to resolve the situation (e.g., "Please upgrade your session permissions to Full Access").

It was only after analyzing the logs that I realized the root cause was a permission issue.

The Improvement Idea

The agent's feedback loop for permission-related failures needs to be more user-friendly and actionable.

When a sandbox denies an operation (specifically for EPERM or similar errors on paths outside the workspace), the agent should:

1. Immediately notify the user with a clear message.
2. Explain the cause, e.g., "The installation is trying to modify user configuration files outside the workspace."
3. Offer a clear solution, e.g., "Please change the session's sandbox permission to Full Access and ask me to retry."

This would greatly improve the user experience, especially for those learning the platform, and prevent the "agent is stuck" perception.

Additional Info

• OS: Windows 11
• DSH Version: 0.1.2-alpha.5
• Initial Session Permission: workspace-write
• Full Session Log is available on request for more context.

Related Discussions

I found Discussion #468, which touches on a similar permission escalation mechanism. However, my proposal focuses on the user-facing communication aspect, which I believe is a distinct and important UX problem to solve.

Thanks for considering this!