Control Chrome with AppleScript

Created By
Anthropica year ago
Control Google Chrome browser tabs, windows, and navigation
Overview

what is Control Chrome with AppleScript?

Control Chrome with AppleScript is an extension that allows users to control Google Chrome browser tabs, windows, and navigation through Apple's official AppleScript API.

how to use Control Chrome with AppleScript?

To use this extension, you can execute AppleScript commands to open URLs, manage tabs, execute JavaScript, and retrieve page content in Google Chrome.

key features of Control Chrome with AppleScript?

  • Open URLs in new or current tabs
  • Get information about the current active tab
  • List all open tabs in Chrome
  • Close specific tabs
  • Switch between tabs
  • Reload tabs
  • Navigate back and forward in browser history
  • Execute JavaScript in the current tab
  • Retrieve text content of the current page

use cases of Control Chrome with AppleScript?

  1. Automating web browsing tasks using scripts.
  2. Managing multiple tabs efficiently.
  3. Executing JavaScript for testing or automation purposes.
  4. Retrieving content from web pages for data analysis.

FAQ from Control Chrome with AppleScript?

  • Is this extension affiliated with Google or Chrome?

No, this extension is not affiliated with Google or Chrome.

  • What platforms does it support?

This extension is compatible with macOS (darwin).

  • Is there a license for this extension?

Yes, it is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Anthropic
Star
-
Language
-
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)

20 hours ago
Gpt Scrambler

2 days ago