AgentKit Browser Automation

Created By
tmahesha year ago
agentkit for playwright-mcp server
Overview

What is AgentKit Browser Automation?

AgentKit Browser Automation is a sophisticated framework designed for intelligent web navigation and task execution using a multi-agent system.

How to use AgentKit Browser Automation?

To use this project, clone the repository, install the necessary dependencies, set up your environment variables, and run the Playwright MCP server along with the Inngest CLI.

Key features of AgentKit Browser Automation?

  • Intelligent task planning that breaks down complex tasks into manageable steps.
  • State management to track browser state and action results.
  • Robust error handling and recovery mechanisms.
  • Comprehensive event logging and monitoring.
  • Extensible action registry for custom behaviors.
  • Built-in validation for task completion.
  • Memory management to maintain context and history of actions.

Use cases of AgentKit Browser Automation?

  1. Automating repetitive web tasks such as form submissions.
  2. Testing web applications by simulating user interactions.
  3. Scraping data from websites efficiently.
  4. Validating web content and functionality.

FAQ from AgentKit Browser Automation?

  • What are the prerequisites for using this project?

You need Node.js (v14 or higher), npm or yarn, and an OpenAI API key for GPT models.

  • Is there a community for support?

Yes! You can contribute to the project on GitHub and engage with other users and developers there.

  • Can I customize the agents?

Absolutely! The framework is designed to be extensible, allowing you to create custom behaviors.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tmahesh
Star
0
Language
TypeScript
License
-
Tags

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