From ada9eebe3fabbe002106d71b702b3465683d99ea Mon Sep 17 00:00:00 2001
From: Alessandro <155005371+3clyp50@users.noreply.github.com>
Date: Sun, 10 May 2026 03:02:10 +0200
Subject: [PATCH] Document computer-use rearm guidance and evidence

Update the computer-use skill so agents tell users to run /computer-use rearm when the desktop-control backend reports COMPUTER_USE_REARM_REQUIRED, instead of asking them to manually switch modes.
---
 skills/computer-use-remote/SKILL.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/skills/computer-use-remote/SKILL.md b/skills/computer-use-remote/SKILL.md
index de330e4f8..69e02c4f4 100644
--- a/skills/computer-use-remote/SKILL.md
+++ b/skills/computer-use-remote/SKILL.md
@@ -53,7 +53,7 @@ Arguments:
 
 Availability, backend support, and trust mode are checked when the tool runs. If no CLI is connected or local computer use is disabled, tell the user what to enable instead of using the server environment.
 
-If any tool result contains `COMPUTER_USE_REARM_REQUIRED` or `status=rearm required`, stop the computer-use sequence immediately. Do not retry `start_session`, do not call `capture`, and do not use shell, vision, or screenshot fallbacks to bypass it. Tell the user that the A0 CLI has Computer Use configured but the installed desktop-control backend is not armed; they must re-arm it in the CLI with Confirm with User, approve the platform permission prompt if shown, and then switch back to Free Run if desired.
+If any tool result contains `COMPUTER_USE_REARM_REQUIRED` or `status=rearm required`, stop the computer-use sequence immediately. Do not retry `start_session`, do not call `capture`, and do not use shell, vision, or screenshot fallbacks to bypass it. Tell the user that the A0 CLI has Computer Use configured but the installed desktop-control backend is not armed; they should run `/computer-use rearm` in the A0 CLI and approve the platform permission prompt if shown.
 
 ## Core Loop