mirror of
https://github.com/MODSetter/SurfSense.git
synced 2026-10-21 22:01:21 +00:00
433d2664fd
- Google Search: Google's sorry wall is recognised by host and path, not a "/sorry" substring, so a result linking to a page with "sorry" in its URL no longer burns the wave's exit (goto and the captcha check share captcha.is_sorry_url). - Walmart: a redirect still pending after the last allowed hop is a refused try, so the next exit is tried instead of reading an empty page. - Amazon: a hedge whose sticky lease is unavailable falls back to the gateway instead of spending the call's hedge budget on nothing. - Fixtures: live tracking and session tokens scrubbed from the captured pages (Indeed, Amazon, Google, Google Maps, TikTok, YouTube). - plugin-host.md: shared_access() everywhere, and the Reddit and Instagram gaps now describe their fail-fast latches. |
||
|---|---|---|
| .. | ||
| bundles | ||
| registry | ||
| remote | ||
| README.md | ||
Plugins
A plugin is a remote MCP server that gives SurfSense's agent tools. Its publisher hosts the server; SurfSense lists it, asks the user before connecting, and calls it. Any MCP server that works in other MCP clients works here unchanged. How SurfSense handles plugins is in plugins.
| Folder | What it holds |
|---|---|
registry/ |
The list of third-party plugins, their icons, the check every entry passes, and the container that serves them |
remote/ |
SurfSense's own plugins and the plugin host that runs them. Maintainers only for remote/proprietary/ |
bundles/ |
Deferred. The earlier, local design's SDK and tooling, kept for plugins that run on the user's machine |
Want to add your plugin? Read Add your plugin to SurfSense: what a plugin is, how to get your MCP server ready, try it in the app, and list it with one pull request. It is written for coding agents as well as people.