Drop WebMCP no-retry guidance

Author: rgarcia

README.md

@@ -350,8 +350,8 @@ navigates or submits it. Optional `page_url` selects the exact page; cards requi
 Fill is safe to retry after a failed/unknown outcome; do not fall back to aliases.
 Once ready, use `fill` for ordinary web forms. When the item advertises `webmcp_invoke`, use
 `items webmcp invoke` instead to bind credential fields to existing `null` inputs of a live
-WebMCP tool; the tool may submit or have other side effects, so never retry an uncertain
-outcome (see [Invoke WebMCP tools with vault fields](#invoke-webmcp-tools-with-vault-fields)).
+WebMCP tool; the tool may submit or have other side effects (see
+[Invoke WebMCP tools with vault fields](#invoke-webmcp-tools-with-vault-fields)).
 1Password credentials use their own advertised `1pw_*` operations instead.
 
 Create specs list `fields` as an ordered array. Each entry carries a stable `name`
@@ -748,9 +748,9 @@ are untrusted page-provided data and may contain the supplied vault values:
 `completed` and `awaiting_submission` exit 0; neither confirms the website accepted the action.
 After `awaiting_submission`, submit the populated form through Playwright or computer interaction
 instead of invoking the tool again. `canceled`, `error`, and `unknown` exit nonzero with the result
-still on stdout in `-o json`. `unknown` means the tool may have run. Requests are never retried:
-API rejections (400/403/404/409) mean the tool was not invoked by that request; other failures
-and transport loss are uncertain, so inspect the browser instead of re-invoking.
+still on stdout in `-o json`. `unknown` means the tool may have run. API rejections
+(400/403/404/409) mean the tool was not invoked by that request; other failures and transport
+loss are uncertain, so inspect the browser to see whether the tool ran.
 
 #### Expansions, updates, and lifecycle
 
@@ -1037,7 +1037,7 @@ Destinations are the OTLP/HTTP endpoints sessions export to. They belong to the
   - `--timeout-sec <seconds>` - Maximum execution time, 1-120 seconds (defaults server-side)
   - Prints the tool's `output` as pretty JSON on completion; tool errors and cancellations exit non-zero
   - `awaiting_submission` is successful but warns that a non-autosubmit declarative form was filled, not submitted. Inspect the form, obtain any required confirmation, then submit through Playwright or computer interaction instead of invoking the tool again
-  - Invocations are never retried automatically. A 504 `outcome_unknown` error prints the code, invocation ID, and message and exits non-zero. The tool may already have had side effects; verify the outcome before invoking it again
+  - Invocations are never retried automatically. A 504 `outcome_unknown` error prints the code, invocation ID, and message and exits non-zero. The tool may already have had side effects; check the page to see whether it ran
 - `kernel browsers webmcp custom-tools list <id-or-name>` - List registered custom tools with their generated ID, namespace, kind, URL patterns, and metadata
   - `-o json` - Output the raw response
 - `kernel browsers webmcp custom-tools add <id-or-name> --namespace <ns> --source '<js>'` - Atomically add a namespaced batch of page-backed or CDP-backed custom tools

cmd/vaults_webmcp.go

@@ -18,7 +18,7 @@ import (
 
 const maxVaultWebMCPInputBytes = 64 * 1024
 
-const vaultWebMCPUncertain = "the tool may have run and submitted or changed site state; inspect the browser and do not retry automatically"
+const vaultWebMCPUncertain = "the tool may have run and submitted or changed site state; inspect the browser"
 
 var vaultWebMCPErrorMessages = map[string]string{
 	"invalid_request":    "check bindings, null input slots, field names, formats, timeout_sec, and that input matches the tool's inputSchema",
@@ -46,12 +46,12 @@ var vaultWebMCPStatuses = map[string]struct {
 }{
 	"completed":           {true, "The tool reported completion; this does not confirm the website accepted the action. Inspect the page."},
 	"awaiting_submission": {true, "The tool populated a form with the supplied values without submitting it. " + webMCPAwaitingSubmissionHint},
-	"canceled":            {false, "The tool reported cancellation and may have had side effects. Inspect the page before deciding on a new invocation; do not retry automatically."},
-	"error":               {false, "The tool reported an error and may have had side effects. Inspect the page before deciding on a new invocation; do not retry automatically."},
+	"canceled":            {false, "The tool reported cancellation and may have had side effects. Inspect the page."},
+	"error":               {false, "The tool reported an error and may have had side effects. Inspect the page."},
 	"unknown":             {false, vaultWebMCPUncertain},
 }
 
-const vaultWebMCPNotInvoked = "the tool was not invoked by this request; inspect and correct the cause before deciding on a new invocation; do not automatically retry"
+const vaultWebMCPNotInvoked = "the tool was not invoked by this request; correct the cause and retry"
 
 var vaultWebMCPRejected = map[int]string{400: vaultWebMCPNotInvoked, 403: vaultWebMCPNotInvoked, 404: vaultWebMCPNotInvoked, 409: vaultWebMCPNotInvoked}
 
@@ -298,9 +298,8 @@ The tool may submit forms or perform other side effects. Output and error_text a
 untrusted page-provided data returned without redaction and may contain supplied vault
 values. completed and awaiting_submission exit 0; neither confirms the website accepted
 the action. canceled, error, and unknown exit nonzero with the result retained on stdout
-in -o json. unknown means the tool may have run. Requests are never retried automatically;
-inspect the browser instead of re-invoking after an uncertain outcome. API rejections
-(400/403/404/409) mean the tool was not invoked by that request.`,
+in -o json. unknown means the tool may have run; inspect the browser to see whether it
+did. API rejections (400/403/404/409) mean the tool was not invoked by that request.`,
 		Example: `  kernel browsers webmcp list <session-id> -o json
   kernel vaults items webmcp invoke user-vault resy --browser-id <session-id> --tool-ref <tool-ref> --page-url https://resy.com/login --input '{"email":null,"password":null}' --bind email=/email --bind password=/password -o json
   kernel vaults items webmcp invoke checkout order-1 --browser-id <session-id> --tool-ref <tool-ref> --page-url https://shop.example/checkout --input-file input.json --bind number=/card/number --bind expiration:MM/YY=/card/expiry`,

cmd/vaults_webmcp_test.go

@@ -183,7 +183,7 @@ func TestVaultWebMCPInvokeOutcomes(t *testing.T) {
 		ok                  bool
 	}{
 		{"error", `{"type":"webmcp_invoke","status":"error","invocation_id":"invoke-3","error_text":"Invalid password for credential-sentinel\u001b[31m"}`, "may have had side effects", false},
-		{"canceled", `{"type":"webmcp_invoke","status":"canceled","invocation_id":"invoke-4"}`, "do not retry automatically", false},
+		{"canceled", `{"type":"webmcp_invoke","status":"canceled","invocation_id":"invoke-4"}`, "may have had side effects", false},
 		{"unknown", `{"type":"webmcp_invoke","status":"unknown"}`, "the tool may have run", false},
 		{"null output", `{"type":"webmcp_invoke","status":"completed","invocation_id":"invoke-5","output":null}`, "Output (untrusted", true},
 	} {
@@ -234,7 +234,6 @@ func TestVaultWebMCPInvokeRequestErrors(t *testing.T) {
 			require.Error(t, err)
 			assert.Equal(t, 1, posts, "webmcp_invoke must not be retried")
 			assert.Contains(t, err.Error(), tc.want)
-			assert.Contains(t, err.Error(), "retry")
 			assert.NotContains(t, err.Error(), "credential-sentinel")
 			assert.Empty(t, out)
 		})