flutter-macos-tcc-responsible-process-camera-denial

flutter-macos-tcc-responsible-process-camera-denial is a skill for Claude Code, Codex from divinevideo/divine-mobile. It costs 231 tokens per session (2,719 once invoked), scanned A, original, MPL-2.0.

A troubleshooting guide for camera and microphone access in Flutter macOS apps launched from a terminal or development tool. It covers cases where the app reports that the camera is ready but shows a black preview or no frames.

In plain words
What is it for?
Use it to investigate black camera previews, zero camera frames, missing permission dialogs, and initialization timeouts when running Flutter apps on macOS.
Why use it?
It helps find permission problems caused by macOS assigning access to the launching terminal process instead of the app. This can happen even when the app’s usage descriptions and entitlements look correct.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code; installed under .agents/ (shared by several agents).

Good fit Use it to investigate black camera previews, zero camera frames, missing permission dialogs, and initialization timeouts when running Flutter apps on macOS.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/divinevideo/divine-mobile/flutter-macos-tcc-responsible-process-camera-denial
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add divinevideo/divine-mobile --skill flutter-macos-tcc-responsible-process-camera-denial
Clone the repo
git clone --depth 1 https://github.com/divinevideo/divine-mobile

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for flutter-macos-tcc-responsible-process-camera-denial

README.md
[![agentmods](https://agentmods.dev/badge/skills/divinevideo/divine-mobile/flutter-macos-tcc-responsible-process-camera-denial/github.svg)](https://agentmods.dev/skills/divinevideo/divine-mobile/flutter-macos-tcc-responsible-process-camera-denial)
Your own site
<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/flutter-macos-tcc-responsible-process-camera-denial"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/flutter-macos-tcc-responsible-process-camera-denial/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for flutter-macos-tcc-responsible-process-camera-denial

Your own site · 80×15
<a href="https://agentmods.dev/skills/divinevideo/divine-mobile/flutter-macos-tcc-responsible-process-camera-denial"><img src="https://agentmods.dev/badge/skills/divinevideo/divine-mobile/flutter-macos-tcc-responsible-process-camera-denial.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 231 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,719 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Rogue Agent · line 9
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
  • medium Rogue Agent · line 29
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
  • medium Rogue Agent · line 61
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00231 $0.02719
Opus 5 $0.00115 $0.01359
Sonnet 5 $0.00046 $0.00544
Haiku 4.5 $0.00023 $0.00272

Measured 11d ago against content hash 3796cbb9eacf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

flutter-macos-tcc-responsible-process-camera-denial scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/flutter-macos-tcc-responsible-process-camera-denial/SKILL.md · 266 lines

How it starts

The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Flutter macOS TCC Responsible-Process Camera Denial

Problem

A Flutter macOS app that should have camera/microphone access shows a black preview (or returns zero frames) even though:

  • NSCameraUsageDescription and NSMicrophoneUsageDescription are present in macos/Runner/Info.plist.
  • com.apple.security.device.camera and com.apple.security.device.audio-input are true in both DebugProfile.entitlements and Release.entitlements.
  • The native camera plugin reports isInitialized: true and returns a texture ID.
  • No permission dialog ever appears.
  • No errors are logged by the camera plugin or AVFoundation.

The symptom is usually a "timeout fallback" firing in the plugin (e.g. DivineCamera macOS: Initialization completed via timeout, or similar 2-second init guards) because the plugin is waiting for a first sample buffer that never arrives. Camera metadata from the plugin shows iso: 0.0, exposureDuration: 0.0, aperture: 0.0 — the device was enumerated but never actually started delivering samples.

Context / Trigger Conditions

All of the following are true:

  1. App was launched via flutter run -d macos (or via flutter run from an IDE that wraps flutter in a terminal — VS Code, Cursor, Android Studio, cmux).
  2. The terminal emulator is a hardened-runtime app without camera/mic entitlements in its own code signature.
  3. macOS version is 10.15+ (TCC enforcement tightened; affects Big Sur onwards, intensifies on Sequoia/Tahoe).
  4. No explicit AVCaptureDevice.requestAccess(for: .video) call in the plugin, OR the call is being attributed to the wrong process.

Specifically, this is NOT:

  • flutter-macos-permission-handler-camera-failure (that's about permission_handler plugin silently failing to bridge to TCC).
  • flutter-macos-duplicate-camera-plugin (that's a build error).
  • A missing Info.plist entry (the usage description IS present).
  • A missing entitlement (the entitlement IS present).

Root Cause

macOS TCC attributes permission requests to the responsible process, not the accessing process. When flutter run launches the .app as a child of the terminal, TCC walks the process tree and picks the terminal as the "responsible" party for any protected resource access. This is the same mechanism that causes "Terminal wants access to ..." prompts instead of prompts for individual scripts.

Read the full file on GitHub · 266 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 266 lines · 231 tokens per session scan A 3796cbb9eacf

Subscribe to this mod's changes

flutter-macos-tcc-responsible-process-camera-denial is a skill published in the GitHub repository divinevideo/divine-mobile (265 stars, last pushed today), licensed MPL-2.0. It adds 231 tokens to every session and 2,719 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens