Stop Copy-Pasting Code: Build Chrome Extensions With Claude Co-work in Minutes
Tired of wrestling with manifest.json and file chaos? You don’t need to be a JavaScript wizard. Claude’s Co-work mode writes, edits, and reloads a Chrome extension right inside a local folder. You experiment, break things, and roll back instantly. Many builders finish a working prototype in under an hour. Ready when you are.

What you’ll walk away with
- A working Chrome extension running locally.
- A repeatable Co-work workflow you can use again.
- A checklist to zip, publish, and iterate without hand-editing files.
Roadmap
- Create the workspace.
- Tell Claude what you want.
- Load, test, iterate.
- Publish (optional).
Follow the steps below.

Why Claude Co-work matters
Claude runs locally in a folder you control. That means:
- No copy-paste chaos. Claude generates every file—manifest, content scripts, icons, popup UI.
- Instant edits. Tell Claude to fix a selector; it rewrites the file and saves.
- One-click reload. Chrome picks up changes without manual uploads.
Use Sonnet for fast, cheap iterations and switch to Opus only for stubborn bugs.

Make a Chrome extension in minutes
Here’s a simple, real-world example: “GPT Focus.” It strips distractions from chat.openai.com—sidebars, banners, model pickers—leaving only the conversation.
Step 1 — Create a workspace folder
- Open Claude Desktop → select Co-work.
- Click the folder icon → Choose a different folder → New Folder → name it GPT Focus → Open.
- Grant “Always allow” so Claude can read/write inside the folder.
Step 2 — Craft the prompt
Tell Claude exactly what you want. Short, specific prompts work best.
Example prompt: “Build a Chrome extension for chat.openai.com called GPT Focus. When enabled, hide the left menu, top model picker, upgrade banner, profile menu, and the ‘What are you working on?’ text. Add a toggle that turns focus mode on/off without a page reload.”
Claude instantly creates a sub-folder (e.g., gpt-focus-v1) with manifest.json, content scripts, icons, and a popup UI.

Step 3 — Load the unpacked extension
- In Chrome, go to Chrome Extensions.
- Turn Developer mode on.
- Click Load unpacked → select the …-v1 folder.
- Toggle the extension on and refresh ChatGPT.
Step 4 — Debug in seconds
First try fails? Don’t sweat it. Tell Claude what broke.
Example: “The toggle stays greyed out.”
Claude finds the wrong DOM selector, rewrites the content script, and saves. Back in chrome://extensions click the reload icon, refresh the page, and test again—no file juggling.

Step 5 — Visual polish and small features
Ask Claude to tweak UI or animations: “Add a subtle shadow in light mode and a neon glow in dark mode.” Or: “Remove animations, keep the toggle fix.” Iterate until it feels right.
Quick wins
- Don’t move the workspace folder: Chrome links the extension to that path. If you move it, reload the unpacked build from the new location.
- Keep versioned folders (gpt-focus-v2, v3) so you can roll back easily.
- If you have tight quotas, use Sonnet for most work. Switch to Opus for stubborn issues.
- Claude’s browser integration (the official Claude for Chrome extension) can inspect live pages to produce precise selectors.

Mini success snapshot
Carlos launched a small productivity extension using this workflow. He added a simple premium toggle and earned about $1.2k in his first month from a few hundred users. Small, focused features scale if they solve a real pain.
Publish to the Chrome Web Store
- Zip the build: right-click the …-v1 folder → Compress (macOS) or Send to › Compressed (zipped) folder (Windows).
- Create a developer account: visit Chrome Web Store Developer Dashboard. One-time fee $5–$10.
- Upload the package: New item → choose your ZIP. Let Claude draft your description, single-purpose text, and permission justifications. Paste its output into the dashboard.
- Assets & screenshots: the Web Store wants 1280×800 px images. Quick fix: capture a screen, open Canva → Custom size → 1280×800 → drop your screenshot → download.
- Privacy policy: ask Claude to write “we collect no data” wording, paste it into a public Google Doc, copy the share link, and add it to your listing.
- Submit for review: Save draft → Submit for review. Extra permissions (like “storage”) may extend review time.

Action box — Do this next
- Open Claude Desktop → Co-work.
- Create a workspace folder named after your idea.
- Paste a one-paragraph prompt describing the extension’s single purpose.
- Load the unpacked folder in chrome://extensions and test.
Best practices
- One big idea per extension. Keep it focused.
- Write concise prompts. Claude performs better with clear constraints.
- Log changes in a quick changelog file inside the folder. You’ll thank yourself later.
You can ship a polished Chrome extension without manually editing files. Claude writes the code, fixes bugs, and drafts your listing—your job is to dream and iterate. Try building your first extension with Claude Co-work, then level up your AI skills at tixu.ai — a beginner-friendly AI learning platform that helps you go from curiosity to confidence.



Leave a Reply