Загрузка видео...

Не удалось загрузить видео

На главную

Introducing: Browser Use Extensions 🧩 Your agent has been browsing the internet naked. Not anymore. > Any Chrome extension, uploaded once > Loaded before the first page > Ad blockers, password managers, your own Live today 💯

14,243 просмотров • 3 дней назад •via X (Twitter)

Комментарии: 13

Фото профиля Ali Sharjeel
Ali Sharjeel3 дней назад

I also released a browser use extension last week but 100% free:

Фото профиля Marcus Eagan
Marcus Eagan3 дней назад

@waynesutton Wow.

Фото профиля Stan Sadokov | NodeMaven
Stan Sadokov | NodeMaven3 дней назад

does extension state persist with the browser profile across sessions? especially local storage and auth.

Фото профиля RetroRanger Anonymous
RetroRanger Anonymous3 дней назад

we've been browsing naked the whole time? the real bug. loading extensions before first page is the win

Фото профиля zachhurst
zachhurst3 дней назад

Who’s creating a repository of extention packs? Asking for the community.

Фото профиля Guilherme Vasques
Guilherme Vasques2 дней назад

If add, login with Google.. with full sync. Will be Amazing :)

Фото профиля soulblocks
soulblocks2 дней назад

omfg thank you

Фото профиля r/69
r/693 дней назад

i want to approve the extension's permissions before the agent loads it

Фото профиля Enric Baltasar 🚀
Enric Baltasar 🚀3 дней назад

This is awesome

Фото профиля Aapakari
Aapakari3 дней назад

Do extensions stay logged in across runs, or is uploaded once just the files?

Фото профиля shydev
shydev3 дней назад

giving my agent ublock origin 🤣

Фото профиля Babak
Babak2 дней назад

finally

Фото профиля Rohan
Rohan3 дней назад

Do uploaded extensions also load in headless runs? Chrome has historically limited them there.

Похожие видео

Meet WebBrain: An Open-Source, Local-First AI Browser Agent That Reads Pages and Automates Tasks in Chrome and Firefox WebBrain lives inside your browser and can run entirely on your own local model — no cloud, no account, no data leaving your machine. Most "AI browser agents" are a chat box that pastes your page into someone else's server. That's not an agent that lives where you browse — and WebBrain draws a very clear line between the two. It's an open-source (MIT), local-first browser agent for Chrome and Firefox. It runs inside your existing authenticated session, on a model you pick — so with llama.cpp or Ollama, nothing leaves your machine. Here's what's actually interesting: → Two modes, cleanly separated. Ask reads the page (read-only, content scripts). Act clicks and types through the Chrome DevTools Protocol (chrome.debugger) — trusted input events that modern sites honor, reaching cross-origin iframes and shadow DOM. → UI-first by design. For anything that submits, sends, or buys, it drives the visible UI and refuses to hit REST/GraphQL endpoints directly. It starts read-only and asks before consequential actions. → Bring any model. llama.cpp, Ollama, LM Studio, vLLM — or OpenAI, Claude, Gemini, DeepSeek, Groq, OpenRouter. Recommended local: Qwen 3.6 35B (Qwen3.6-35B-A3B), which beat Gemma 4 on the project's screenshot benchmark. → Tuned for cost and privacy. Token-conscious screenshots, oldest-first context trimming, a dedicated vision model, 40+ tools (~20 in Compact mode). No telemetry. No accounts. Full analysis: GitHub Repo: Chrome Extension: Firefox Add-on: Portal:

Marktechpost AI

203,011 просмотров • 3 месяцев назад

The search bar will never be the same. Introducing Magic City, a fundamentally new Internet protocol for AI agents to browse, shop, and complete online work for you - autonomously, securely, and privately. Just tell Magic City what you want to buy and its native agent, the Magic Internet Agent, handles the rest. Developers can connect their own agents and models, publish custom extensions for anyone to use, or integrate Magic City into any website for free. Today, we're especially excited to debut Magic City for customers who like to be early, with a two-week alpha testing phase: 1) Try it today ( Login, enter Local Data Vault info, Claim your daily free credits, Install the Chrome extension, and start on the Happy Path. 2) Happy Path #1 - Magic Internet Agent. Tell Magic City: “I want to buy nature valley crunchy granola bars from Amazon, $4 max spend” 3) Happy Path #2 - SantaClawz Code Audit Agent. Tell Magic City: ‘I want a code audit for [insert github repo link] 4) Having fun? i) Top-up your credits with Stripe, and try a few more different prompts, ii) Devs, start customizing and integrating Magic City agents into your website, as a white-label service. 5) Visit Zeko Discord or contact the Zeko team for support Why Happy Path testing? The internet is a massive place; we’re showcasing the core utility of Magic City and the Magic Internet Agent, but we want to you to take it to the next level, with your own extensions and agents that work natively with your website - so you can monetize the search bar.

Zeko Labs

50,275 просмотров • 24 дней назад

yesterday i showed claude code using codex's computer use, today i got some more fucking fire for you claude can also drive codex's official chrome extension, and it controls chromium browsers beautifully all in the background, without the "allow" popup chrome devtools mcp throws at you every time a new agent connects it even handles more than one browser: each install of the extension gets its own instance id, so claude knows which is which i have helium as my main and chrome for work, and claude code now uses both first, install the chrome plugin in the codex app and add openai's chatgpt extension to your chromium browser (or all of them, if you have a few) then give this to your claude: "Set up Codex's Chrome extension for you on my Mac. I've installed the Chrome plugin in the Codex app and the extension. Use Codex's computer use MCP server as user MCP "codex-cu": keep it if it's already registered, otherwise copy the "cua_repl" entry from ~/.codex/plugins/cache/openai-bundled/unified-computer-use/ /.mcp.json. Its browser side rejects calls without Codex turn metadata, so put a small stdio proxy in front that adds _meta["x-codex-turn-metadata"] (session_id and turn_id as a JSON string) to every tools/call. Add a Stop hook that tells this session's proxy to call the hidden turn_ended tool and start a new turn_id, so your tabs get released without touching other sessions. Test it by opening a tab straight at a URL in each browser with cua.createBrowserTab(browserId, url). Browsers can all report as "Chrome", so if I have several, ask me which test tab showed up in which browser." got more than one browser and ok with it touching your claude.md? give it this too: "Write each browser's name and metadata.extensionInstanceId into my global CLAUDE.md, with a note to pick browsers by that id and open tabs straight at a URL."

🥔🥔🥔

71,675 просмотров • 4 дней назад