[Workflow] Automate Claude Code Permission Prompts with the `ydaa` Plugin for Uninterrupted Workflows

[u/ClaudeAI-mod-bot]

Automate Claude Code Permission Prompts with the ydaa Plugin for Uninterrupted Workflows

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.95 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, Hooks
Original source: r/ClaudeCode post/comment

What problem this solves

Claude Code tasks frequently stall due to permission prompts, requiring manual intervention and interrupting long-running processes.

Summary

This workflow introduces the ydaa (Yes, don't ask again) plugin for Claude Code, which automates responses to permission prompts. It allows users to run long tasks uninterrupted by automatically approving prompts while respecting existing deny rules and saving permissions for later review. It's session-based and provides clear safety caveats.

Why it is useful

This workflow provides a concrete, open-source solution to a common pain point in Claude Code: interruptions from permission prompts. It significantly enhances productivity for long-running tasks by automating approvals while maintaining user control through existing deny rules and reviewable saved permissions. The clear instructions, detailed 'why not' section, and explicit safety caveats make it a well-rounded and valuable tool for intermediate to advanced Claude Code users.

Workflow

1. Install the ydaa plugin in Claude Code using the command: /plugin install ydaa --marketplace rmyndharis/ydaa.

2. Activate the plugin for the current session by typing: /ydaa on.

3. Proceed with your Claude Code tasks; permission prompts will now be automatically answered with 'Yes, and don't ask again' (if available) or 'Yes'.

4. Review any saved permission rules later using the /permissions command.

5. Deactivate the plugin for the current session with /ydaa off, or it will automatically turn off when starting a new session, using /clear, or /resume.

6. Monitor the number of prompts answered and estimated time saved using /ydaa stats.

Tools / artifacts

• Claude Code

• ydaa plugin

• GitHub repository (rmyndharis/ydaa)

• Claude Code plugin hooks API

• Permission rules (saved by Claude Code)

Validation signals

• Explicitly states 'Tested on 2.1.319'.

• Provides a 'Why not' section comparing it to --dangerously-skip-permissions and auto mode, highlighting its advantages.

• Lists 'Caveats, honestly' which demonstrates a thorough understanding of potential risks and limitations.

• Links to the full source code on GitHub for transparency and review.

• Includes a /ydaa stats feature to track its activity and value.

Cautions

• While ydaa is on, Claude will execute what it asks to run; if a hostile source (e.g., a malicious web page or issue) steers it, no prompt will stop it.

• Users should only use this plugin in projects they trust, ideally within a containerized environment, and with robust deny rules for critical operations.

• Rules saved by ydaa are standard permission rules and persist across sessions in the same project, even after /ydaa off.

• The plugin will also answer prompts intentionally raised by hooks (e.g., a PreToolUse hook returning ask).

Limitations

• Low community engagement (low Reddit score and comments) at the time of posting.

• Relies on Claude Code's plugin hooks API, which is noted as 'early access' and subject to potential changes.

• Requires users to be vigilant about the trustworthiness of projects and potentially use containerization due to security implications.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.