|
| 1 | +# How to Push These Changes |
| 2 | + |
| 3 | +## ⚠️ Important Note |
| 4 | + |
| 5 | +I've made all the stealth mode modifications locally, but I **cannot push to the nimbus21/chrome-devtools-mcp repository** because: |
| 6 | +1. I don't have GitHub authentication credentials |
| 7 | +2. I don't have write access to that repository |
| 8 | + |
| 9 | +## Your Options |
| 10 | + |
| 11 | +### Option 1: Push to Your Own GitHub Fork (Recommended) |
| 12 | + |
| 13 | +1. **Fork the repository on GitHub:** |
| 14 | + - Go to https://github.com/nimbus21/chrome-devtools-mcp |
| 15 | + - Click "Fork" button |
| 16 | + - Choose your GitHub account |
| 17 | + |
| 18 | +2. **Change the remote URL to your fork:** |
| 19 | + ```bash |
| 20 | + cd /tmp/nimbus-chrome-mcp |
| 21 | + git remote set-url origin https://github.com/YOUR_USERNAME/chrome-devtools-mcp.git |
| 22 | + ``` |
| 23 | + |
| 24 | +3. **Push the changes:** |
| 25 | + ```bash |
| 26 | + git push origin main |
| 27 | + ``` |
| 28 | + |
| 29 | +4. **Use your fork:** |
| 30 | + ```bash |
| 31 | + claude mcp add chrome-stealth npx github:YOUR_USERNAME/chrome-devtools-mcp -- --stealth |
| 32 | + ``` |
| 33 | + |
| 34 | +### Option 2: Create a New Repository |
| 35 | + |
| 36 | +1. **Create a new repository on GitHub** (e.g., `chrome-devtools-mcp-stealth`) |
| 37 | + |
| 38 | +2. **Change the remote:** |
| 39 | + ```bash |
| 40 | + cd /tmp/nimbus-chrome-mcp |
| 41 | + git remote set-url origin https://github.com/YOUR_USERNAME/chrome-devtools-mcp-stealth.git |
| 42 | + ``` |
| 43 | + |
| 44 | +3. **Push:** |
| 45 | + ```bash |
| 46 | + git push -u origin main |
| 47 | + ``` |
| 48 | + |
| 49 | +### Option 3: Move to Your Project Directory |
| 50 | + |
| 51 | +If you want to work with this locally without pushing: |
| 52 | + |
| 53 | +```bash |
| 54 | +# Copy to your project |
| 55 | +cp -r /tmp/nimbus-chrome-mcp /home/coder/project/chrome-devtools-mcp-stealth |
| 56 | + |
| 57 | +# Build and test |
| 58 | +cd /home/coder/project/chrome-devtools-mcp-stealth |
| 59 | +npm install |
| 60 | +npm run build |
| 61 | +npm start -- --stealth |
| 62 | +``` |
| 63 | + |
| 64 | +### Option 4: Create a Pull Request to Original Repo |
| 65 | + |
| 66 | +1. Fork the **original** Google repo: https://github.com/ChromeDevTools/chrome-devtools-mcp |
| 67 | +2. Apply these changes to your fork |
| 68 | +3. Submit a PR to contribute stealth mode to the official project |
| 69 | + |
| 70 | +## What Was Changed |
| 71 | + |
| 72 | +All changes have been committed locally: |
| 73 | + |
| 74 | +```bash |
| 75 | +cd /tmp/nimbus-chrome-mcp |
| 76 | +git log -1 --stat |
| 77 | +``` |
| 78 | + |
| 79 | +### Files Modified: |
| 80 | +- ✅ `package.json` - Added puppeteer-extra dependencies |
| 81 | +- ✅ `src/browser.ts` - Stealth mode implementation |
| 82 | +- ✅ `src/cli.ts` - New CLI options |
| 83 | +- ✅ `src/main.ts` - Pass stealth args |
| 84 | +- ✅ `STEALTH_FEATURES.md` - Full documentation |
| 85 | + |
| 86 | +### Commit Message: |
| 87 | +``` |
| 88 | +Add stealth mode and custom Chrome args support |
| 89 | +
|
| 90 | +- Added puppeteer-extra and puppeteer-extra-plugin-stealth dependencies |
| 91 | +- Implemented --stealth flag to enable bot detection bypass |
| 92 | +- Added --chromeArgs option to pass custom Chrome arguments |
| 93 | +- Updated browser.ts to conditionally use puppeteer-extra with stealth |
| 94 | +- Added anti-detection Chrome flags when stealth is enabled |
| 95 | +- Updated CLI with new options and examples |
| 96 | +- Created comprehensive documentation in STEALTH_FEATURES.md |
| 97 | +``` |
| 98 | + |
| 99 | +## Testing Before Pushing |
| 100 | + |
| 101 | +Build and test locally: |
| 102 | + |
| 103 | +```bash |
| 104 | +cd /tmp/nimbus-chrome-mcp |
| 105 | + |
| 106 | +# Install dependencies |
| 107 | +npm install |
| 108 | + |
| 109 | +# Build |
| 110 | +npm run build |
| 111 | + |
| 112 | +# Test with stealth mode |
| 113 | +npm start -- --stealth --executablePath /usr/bin/chromium |
| 114 | +``` |
| 115 | + |
| 116 | +Then in another terminal, test with an MCP client. |
| 117 | + |
| 118 | +## View Changes |
| 119 | + |
| 120 | +```bash |
| 121 | +cd /tmp/nimbus-chrome-mcp |
| 122 | + |
| 123 | +# View diff |
| 124 | +git show HEAD |
| 125 | + |
| 126 | +# View modified files |
| 127 | +git diff HEAD~1 |
| 128 | + |
| 129 | +# View file tree |
| 130 | +tree -L 2 -I 'node_modules|build' |
| 131 | +``` |
| 132 | + |
| 133 | +## Next Steps |
| 134 | + |
| 135 | +1. Choose which option above fits your needs |
| 136 | +2. Set up GitHub authentication if needed |
| 137 | +3. Push to your repository |
| 138 | +4. Share the stealth mode features! 🎉 |
| 139 | + |
| 140 | +## Quick Command Summary |
| 141 | + |
| 142 | +```bash |
| 143 | +# Option 1: Fork and push |
| 144 | +cd /tmp/nimbus-chrome-mcp |
| 145 | +git remote set-url origin https://github.com/YOUR_USERNAME/chrome-devtools-mcp.git |
| 146 | +git push origin main |
| 147 | + |
| 148 | +# Option 2: New repo |
| 149 | +cd /tmp/nimbus-chrome-mcp |
| 150 | +git remote set-url origin https://github.com/YOUR_USERNAME/NEW_REPO_NAME.git |
| 151 | +git push -u origin main |
| 152 | + |
| 153 | +# Option 3: Local use |
| 154 | +cp -r /tmp/nimbus-chrome-mcp ~/my-stealth-mcp |
| 155 | +cd ~/my-stealth-mcp |
| 156 | +npm install && npm run build |
| 157 | +``` |
| 158 | + |
| 159 | +## Need Help? |
| 160 | + |
| 161 | +The modified repository is at: `/tmp/nimbus-chrome-mcp` |
| 162 | + |
| 163 | +All changes are committed and ready to push once you set up your remote repository! |
0 commit comments