[BUG] Cowork Desktop (Windows): first Artifact publish fails in "Skip all approvals" mode because it still demands an approval card; "Automatically approve" works

### Preflight Checklist

- [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code

### What's Wrong?

In Cowork on Claude Desktop, with the session approval mode set to "Skip all approvals", the first publish of a new artifact fails immediately with:

> The first publish to an Artifact from this Cowork session needs the approval card, and no one can answer it in this session. Do not retry the publish in this session.

No approval card is ever rendered in the conversation. The tool does not wait for one, it refuses at once. This reproduced on the first publish in every new session, across different artifacts and different workflows, over two days.

Switching the same account, same machine and same build to "Automatically approve" makes publishing work normally. The approval mode is the only variable that changed. So "Skip all approvals", documented as the mode where nothing is checked, is strictly worse than "Automatically approve" for artifact publishing.

The failing session also reported itself internally as non-interactive (it stated that OAuth flows could not be run in it) while I was actively typing into it. That suggests no approval channel is wired up under Skip mode, which would explain why the publish gate finds nobody to answer.

Impact: while Skip mode is selected, artifacts cannot be created at all. Because the gate applies only to the first publish per session, the failure is easy to misattribute to the artifact, the workflow, or to working in a local folder, rather than to the approval mode.

### What Should Happen?

"Skip all approvals" should cover the built-in Artifact tool the way it covers everything else. Per "Get started with Claude Cowork", that mode means nothing is checked, and no carve-out for artifacts is documented.

Failing that:

1. The error should name the actual remedy ("switch the approval mode to Automatically approve") instead of describing a card that is never presented.
2. The documentation should record that the Artifact publish gate recognises only Auto mode.

### Error Messages/Logs

```shell
Tool result, verbatim:

The first publish to an Artifact from this Cowork session needs the approval card, and no one can answer it in this session. Do not retry the publish in this session.

---

No local logs are available for the failing period. Desktop file logging under %APPDATA%\Claude\logs, and its MSIX-redirected copy under %LOCALAPPDATA%\Packages\Claude_pzs8sxrjxfjjc\LocalCache\Roaming\Claude\logs, stops on 2026-08-21 and has written nothing since, across at least two app updates. That silence may be a separate bug, and it removes the log evidence this report would normally carry.

Last artifact-related lines written, from the previous mechanism:

2026-08-21 01:10:49 [info] [ScheduledTasks] Auto-approved tool permission for "mcp__cowork__update_artifact" in scheduled task ""
2026-08-21 01:10:49 [info] [CoworkArtifacts] Updated { id: '' }

The old live-artifacts tool mcp__cowork__update_artifact could be auto-approved. The built-in Artifact tool that replaced it on 19 August 2026 apparently cannot, unless the mode is Auto.
```

### Steps to Reproduce

1. Open Cowork in Claude Desktop on Windows 11.
2. Set the approval mode in the chat-box selector to "Skip all approvals".
3. Start a new session and ask Claude to build and publish any artifact. A trivial static HTML page is enough.
4. Observe: the publish fails immediately with the message quoted above, and no approval card appears anywhere in the conversation.
5. Change the approval mode to "Automatically approve".
6. Ask for the same publish. It succeeds.

Reproducibility: 100%. Observed across several sessions and several different artifacts over two days before the approval mode was isolated as the cause.

Not tested: "Manually approve" mode. I do not know whether the card renders correctly there.

### Claude Model

Opus

### Is this a regression?

Yes, this worked in a previous version

### Last Working Version

Unknown exact build; artifact publishing worked before the 19 August 2026 live-artifacts migration

### Claude Code Version

Claude Desktop 1.46388.4 (Cowork, not the CLI)

### Platform

Anthropic API

### Operating System

Windows

### Terminal/Shell

Other

### Additional Information

## Environment

- Claude Desktop 1.46388.4 (MSIX package Claude_pzs8sxrjxfjjc), first launched 2026-09-05
- Earlier builds on this machine: 1.34493.0 (staged 2026-08-21), 1.24012.9 (early August)
- Windows 11 Pro, build 26100, x64
- Cowork in Claude Desktop, local session (local_*), local folder in use
- Signed in to claude.ai via OAuth, not an API key
- No tool deny rules configured; mcp-user-tool-toggles.json is empty for this account
- No CMEK / ZDR / HIPAA configuration

## Probably related

This looks like the interactive-desktop counterpart of an already-reported family of issues, all describing the built-in Artifact tool raising an interactive permission request that nothing in the permission system can satisfy:

- #88997 (2026-08-23): cloud routines, Artifact publish raises an interactive permission prompt, so unattended runs hang in requires_action
- #89967 (2026-08-27): routines cannot run unattended when the task publishes an Artifact; neither the Connectors tab nor permissions.defaultMode: bypassPermissions reaches the native Artifact tool
- #91883 (2026-09-03): cloud routine hangs on a permission prompt for the built-in Artifact tool, triggered by the first-party /morning skill

Those three are filed against cloud routines. This one is the same gate failing in interactive Cowork Desktop, where a user is present and there is still no card to answer.

## Documentation this contradicts

- "Get started with Claude Cowork" describes "Skip all approvals" as the mode where nothing is checked, with no carve-out for artifacts.
- "Share session output as artifacts" (code.claude.com/docs/en/artifacts) documents Auto mode as the one where a classifier reviews the publish instead of prompting. Skip mode is not mentioned in that section at all, which is consistent with the publish gate recognising only Auto.
- "Use artifacts in Claude Cowork" documents approval for an artifact's use of connectors, and says nothing about an approval gate on the publish action itself.

## Suggested fix

Treat "Skip all approvals" the same as "Automatically approve" at the Artifact publish gate, or route it through the same classifier path.

Reproduce the first Artifact publish in a new Cowork Desktop session using Skip all approvals, then compare it with Automatically approve and, if possible, Manually approve. Trace the built-in Artifact publish gate and approval-mode handling, using the documented pages “Get started with Claude Cowork,” “Share session output as artifacts,” and “Use artifacts in Claude Cowork” as expected-behavior references. Done means Skip mode publishes successfully or reports the actual required remedy.

Escrito por el modelo de indexación a partir del texto del issue.