dsh-browser-bsk

A number of plugins in the DSh ecosystem declare ctx.browser in their inject list as a hard gate. The fill entry in dsh-accounts is a textbook case: when no service named browser exists in the profile, that entry stays in pending indefinitely, and the Harness boot-time assertion treats any unactivated entry as a fatal failure, so the whole profile refuses to start. Upstream has filed the issue and opened a PR to move the check to runtime detection, but until that lands, affected profiles are simply stuck.

dsh-browser-bsk closes that gap precisely. It wraps the bsk CLI that browser-skill already depends on into a standard ctx.browser service, implementing the seven methods a fill workflow actually calls: open, listTabs, setValue, click, key, detectChallenge, and close. Methods that are not implemented are simply absent rather than silently no-op-ing. The plugin registers zero tools and ships no Electron or CDP engine of its own, so it never collides with browser-skill six tools by name. Both share the same bsk daemon, the same Agent Window, and the same login session, achieving true zero-overhead coexistence.

This plugin is aimed at developers who already drive their own browser through browser-skill, who have installed dsh-accounts or another plugin with a hard browser inject, and who do not want to pull in the 33-tool, Electron-bundled dsh-builtin-browser as a workaround. Once installed and DSH restarted, the fill entry activates on the next pass, and any disabled flag previously added to cordis.patch.yml just to keep the boot green can be safely removed.