
Local Plugins
Add local-plugins when you need browser automation, structured feature delivery loops, task routing, and TS/JS/Python LSP in one Claude Code marketplace.
Overview
local-plugins is a plugin marketplace for the Build phase that bundles browser automation, feature task workflows, task routing, and multi-language LSP for Claude Code.
What is this marketplace?
- 7-plugin marketplace spanning browser automation, feature workflows, and LSP
- agent-browser CLI for navigate, interact, screenshot, and data extraction
- feature-todo combines Serena MCP, Ralph Wiggum loops, and anti-duplication checks
- task-harness and task-router coordinate sequential dev task execution
- lsp-servers plugin configures TypeScript, JavaScript, and Python language servers
- Marketplace lists 7 plugins
- Includes agent-browser (Vercel Labs lineage), feature-todo, task-harness, lsp-servers, and task-router
- lsp-servers covers TypeScript, JavaScript, and Python
Community signal: 1 GitHub stars.
What problem does it solve?
Agents stall when browser testing, feature tracking, and language servers are manual one-offs instead of installed plugins.
Who is it for?
Solo builders shipping web features who want Vercel-style browser CLI plus structured todo harnesses in Claude Code.
Skip if: Teams that only need a single LSP language or who cannot run MCP-backed feature workflows locally.
What do I get? / Deliverables
After adding the marketplace, you can automate browsers, run harnessed feature loops, and get TS/JS/Python LSP support from one local bundle.
- Browser-driven verification and extraction via agent-browser
- Structured feature-todo execution with duplication guards
- TS, JS, and Python LSP configuration via lsp-servers
Plugins in this marketplace
7 plugins — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Most plugins wire external automation and dev workflows used while building features and verifying them in the browser. agent-browser and task-oriented harness plugins are integration layers between your agent and repos, browsers, and MCP tooling.
How it compares
Multi-plugin automation marketplace, not a single code-review or SEO skill.
Common Questions / FAQ
Who is Local Plugins for?
Developers using Claude Code who need integrated browser automation, task harnesses, and common language servers together.
When should I use Local Plugins?
Use it when you start feature work that requires web interaction tests, routed task execution, and TS/JS/Python editing in one agent setup.
How do I add Local Plugins to my agent?
Register the OmarA1-Bakri-Org Local Plugins marketplace in Claude Code, then enable agent-browser, feature-todo, lsp-servers, and related plugins as needed.