Building Apps with Claude Opus 4.6 Agent Teams & Firecrawl Agent

Video Description

I evaluate the workflow of building a Chrome extension using Claude Opus 4.6 and the new Agent Teams architecture. The video demonstrates how to configure tmux for multi-agent orchestration and integrates the Firecrawl Agent to handle complex data scraping tasks autonomously. I also share the specific branding prompt strategy used to ensure the final application remains consistent with design requirements while fixing bugs in real-time. Github repository: https://github.com/firecrawl/firecrawl-coupon-finder Timestamps: 0:00 - Coupon Finder Demo 1:13 - tmux Agent Setup 3:24 - Adding Firecrawl Plugin 4:06 - Branding Prompt Logic 7:12 - Testing The Extension 👇 Learn more about Firecrawl 👇 🔥 Website: https://www.firecrawl.dev/ ⚡ Get started: https://www.firecrawl.dev/blog/mastering-firecrawl-scrape-endpoint 📚 Docs: https://docs.firecrawl.dev/ 🔔 Subscribe for more tutorials and feature updates from Firecrawl: @Firecrawl_dev 📱 More Links: 💻 GitHub: https://github.com/firecrawl/firecrawl 🎧 Discord: https://discord.com/invite/gSmWdAkdwd 🐦 X (Twitter): https://x.com/firecrawl_dev 💼 Linkedin: https://linkedin.com/company/firecrawl PROMPT: ---------------------------------------- Create a chrome extension that uses Firecrawl /agent to search for coupons. (Needs to use firecrawl to scrape/search if not authenticated help the user authenticate) This should use plasma as the framework and shadcn for UI components. The plugin should be a side panel. The usage should follow: - whenever a user is inside of a checkout page they should be able to right click the input field for the coupon and click “Search for coupons with Firecrawl”. - the extension should open up as a side panel and proceed to use Firecrawl’s /agent endpoint. - make sure to add as context in the prompt enough information for the agent to successfully fetch for the correct coupon. So the website name, url, product being purchased, current date, localization etc. - the agent should also have a schema defined: an array of objects that contains: coupon code, reliability score, description, discount. The discount can either be in cash or percentage off… so keep this field as a string since the currency symbols might vary as well. Finally there should also be an order parameter decided by the agent based on the reliability score and discount. - as soon as the data is retrieved the user should see it all listed on the side panel. Clicking on “add coupon” button next to the coupon should make it add to the input field previously clicked (from right click)… if the input field isn’t identified the button should just be a “copy”. Cache these results in the extension’s memory so that in a next request in the same website they immediately show up. Also make sure the user can delete the codes and trigger a new fetch as well. But limit to max of 5 coupon codes per website. - allow light and dark mode (default to system) - make sure to design everything using firecrawl’s branding: Primary: FF4C00 Accent: FF4C00 Background: F9F9F9 Text Primary: 262626 Link: FF4D00 Personality Tone: Modern Energy: High Audience: developers and AI enthusiasts Firecrawl logo : https://www.firecrawl.dev/brand/firecrawl-logo.png Use firecrawl’s skill (cli) to search for fire crawl’s documentation on implementing with /agent. Prefer Firecrawl CLI when search/scrape There should be a nice button at the top right to configure firecrawl api key. In this same api settings part there should be the remaining amount of firecrawl credits the user still has (check firecrawl documentation for that)Do not let the extension active on every website. It should only be triggered when the user clicks the fetch button. Create an agent team to build each part. Understand how everything can be handled by the team and create the different angles. ----------------------------------------