anthropics / anthropics/claude-code

[BUG] background-mode permission dialog shows only a Deny button, no way to Accept

Open
#92,974 3 comments 1 reaction 0 assignees View on GitHub
area:agents area:permissions bug platform:macos
Dominant language
Python
Stars
145k
Forks
23.1k
PR merge metrics
PR metrics pending

Description

### 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?

I was testing out a scheduled task where Claude sends a message to a group chat. During the test claude request access to use messages and there is no way to accept it, there is only a deny button.

I have ran the test before and it successfully sent messages. I have approved all the permissions and have claude on auto allow as well.

### What Should Happen?

There should be an approve button so permissions can be granted

### Error Messages/Logs

```shell

```

### Steps to Reproduce

Image

Context:
wait whats taking so long, what are you working on

Sorry about that — I was doing a pre-Tuesday readiness check and went a bit deep without checking in. Quick status:

Good news: your Mac's still connected, the draft finished on Sep 4, and I confirmed I can pull real roster/matchup data for Week 1 (rosters are already populated with actual players).

One thing I caught: ESPN's raw data API returns an error on score/matchup views now (works fine for team/draft info, but not live scores) — even though the league is public. I found a reliable workaround using browser navigation instead of the direct API, so this isn't a blocker, just means the data-pull method needs to change from what I originally built.

Also noticed some team names have changed since August — at least one team is now "My Ball Zach Ertz" instead of what I had cached, so I'll need to pull fresh names rather than reuse the old list.

I still need to check whether the "Degenerate Football" group chat is set up and whether I've been added to it — that's next. Want me to keep going now, or pause here?

I think you got stuck in the group chat part, it was checking for 3 hours

Used a tool
Used a tool
there is no accept button only a deny button

Got it — sorry, that explains the long hang earlier too, it was just sitting there waiting on a dialog you had no way to approve.

That's worth knowing about since it'd block the actual Tuesday automation too (the iMessage send needs that same permission). For now, let's not fight it — can you just tell me directly: did you create the "Degenerate Football" group chat yet, and if so, have you added me to it?

Separately, when you get a chance, it might be worth closing and reopening the Claude desktop app (or checking for an update) to see if that fixes the permission dialog — a "Deny only, no Accept" button is definitely a bug on that dialog, not something on my end I can work around.

### Claude Model

Sonnet (default)

### Is this a regression?

Yes, this worked in a previous version

### Last Working Version

_No response_

### Claude Code Version

2.1.247

### Platform

Anthropic API

### Operating System

macOS

### Terminal/Shell

Other

### Additional Information

_No response_

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the background-mode permission dialog on macOS with Claude Code 2.1.247, using the scheduled group-chat message scenario described in the issue. Done means the dialog provides a way to approve Messages access and the scheduled task can proceed instead of waiting on a deny-only prompt.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos
Domain
authorization, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.