Incorporation source map
The researched projects, the capabilities they suggest and their intended integration boundary.
| Source | Capability to extract | Boundary |
|---|---|---|
| MCP-SuperAssistant | Provider adapter registry, lifecycle and remote selector configuration | Port with license review; normalize into adapter descriptors and shared drivers |
| Violentmonkey | Mature userscript compatibility, migration and script-management UX | Compatibility tests and selectively reusable permissive code |
| Nanobrowser | Multi-agent side panel, task history and provider flexibility | Apache-2.0 direct-reference candidate with attribution |
| AIPex / open-claude-for-chrome | Local-first MCP browser tools and compact browser representation | Permissive direct-reference candidate after revision pinning |
| BrowserOS | Chromium-native agent services, CLI and evaluation | AGPL-aware clean implementation or compatible separate distribution |
| Algonius | Typed extension ↔ native-messaging ↔ MCP architecture | Apache-2.0 reference candidate |
| Automa | Visual block workflows, scheduling and reusable blocks | Behavioral study; clean implementation where licensing requires |
| UI.Vision | Recording, OCR, visual matching and Selenium interchange | Behavior/format compatibility after current license audit |
| SingleFile | Self-contained reproducible page capture | AGPL-aware isolated bridge or clean capture implementation |
| Vimium | Keyboard command palette and link hints | Feature extraction with independent UI integration |
| Tab Session Manager | Versioned tab/workspace capture and restoration | Format study and Operation Graph implementation |
Each row becomes a capability contract plus one or more Prompt Commits. Repository revisions and final legal classification must be refreshed during implementation.