dsh-tabbit

dsh's built-in web_fetch tool lacks JavaScript rendering, has no login state, and does not honor system proxies. In fake-ip proxy environments, virtually every domain is rejected outright. For Agent tasks that require interacting with logged-in pages, filling forms, or scraping dynamically rendered content, this limitation renders dsh's web capabilities nearly useless. dsh-tabbit is the official Tabbit Browser plugin that routes dsh's browser operations through Tabbit's native code-first toolchain, giving the Agent real pages, real sessions, and real interactions without shell forwarding or render-less fetching.

The plugin bundles a full set of capabilities built around a live browser: the tabbit_browser tool reads and manipulates pages inside an already-logged-in Tabbit; a browser-proxied web_fetch gives dsh's fetcher JS rendering and intranet reach; typing @ in the Web UI input lists every tab in the current session or the user's browser, all selectable as context; dedicated pageAccess and intranetFetch permission gates ensure every cookie-sharing operation is explicitly approved by the user; and the package also includes environment preflight and auto-install, daily silent plugin updates, a /tabbit-info diagnostic command, and the official Tabbit skill that evolves alongside the browser Runtime.

Who it is for: engineers and teams that need web automation, data extraction, QA, or evaluation inside DeepSeek Harness; developers who are fed up with render-less fetchers failing across the board under proxy setups; and anyone who wants the Agent to operate exactly as their daily driver browser does.