Browser-as-infrastructure for AI agents. Isolated Chrome sessions with fingerprint controls, network isolation, and f...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Strong idea surface, weaker maintenance signal. Steal the pattern before you commit.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Reasonable to try, but it will take more than a quick skim to get real signal.
GitHub health unknown. no security policy. Archived repo plus maintenance drag means copy patterns, not the whole tool.
AI Agent
Universal
Model
Multiple
Build Time
Instant
Fastest way to find out if browser-pilot belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/NoDeskAI/browser-pilot ~/.claude/agents/browser-pilotRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/agents/browser-pilotNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ browser-pilot/ ← installs here └─ settings.json
Browser-as-infrastructure for AI agents. Isolated Chrome sessions with fingerprint controls, network isolation, and full control via REST API / CLI / Web UI.