claude-autoapprove

Created By
PyneSysa year ago
Autoapprove support for claude
Overview

What is Claude Autoapprove?

Claude Autoapprove is a command-line interface (CLI) tool designed to automatically approve tool requests for the Claude Desktop App, enhancing user experience by streamlining the approval process.

How to use Claude Autoapprove?

To use Claude Autoapprove, install it via PyPI with the command pip install claude-autoapprove, and then run it using claude-autoapprove [port], where the port is the listening port for remote debugging connections.

Key features of Claude Autoapprove?

  • Automatically injects JavaScript into the Claude Desktop App to manage tool requests.
  • Configurable auto-approval rules based on user-defined settings.
  • Supports remote debugging for both macOS and Windows platforms.
  • Smart logging and cooldown mechanisms to prevent multiple accidental approvals.

Use cases of Claude Autoapprove?

  1. Streamlining the approval process for tool requests in the Claude Desktop App.
  2. Enhancing productivity by reducing manual approvals for trusted tools.
  3. Facilitating remote debugging sessions with automatic tool request management.

FAQ from Claude Autoapprove?

  • What platforms does Claude Autoapprove support?

Claude Autoapprove supports both macOS and Windows platforms.

  • How do I configure trusted tools?

Trusted tools can be configured in the claude_desktop_config.json file located in your user profile.

  • Is Claude Autoapprove free to use?

Yes, Claude Autoapprove is free to use and is licensed under the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
PyneSys
Star
6
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago