I maintain DeepDeck, an open-source macOS desktop client built on DeepSeek Harness. I would like to provide implementation information for consideration in Browser and Agent Implementation Status.
The current release is v1.0.39, with Apple Silicon and Intel Mac packages.
Browser and agent support
- The Electron browser discovers actual page registrations through Chromium's WebMCP domain and observes tool additions and removals.
- The Harness site agent receives tool names, descriptions, and schemas, and can invoke tools in the live browser page. Discovery uses
browser_context; invocation uses browser_webmcp_call.
- Calls carry the tab, frame, and document identity. Generated tools also carry a saved revision. Navigation or replacement makes affected calls stale.
- Website-provided registrations are labelled Website in the tool list. The screenshot in the walkthrough shows
search_openai discovered on openai.com.
Separate generated-tool feature
DeepDeck also has a Builder mode. An agent explores a site through browser interaction, implements tools for selected workflows, checks registration and execution, and stores the source and versions locally for later visits. Those tools are labelled Built with DeepDeck. This is a DeepDeck feature and is distinct from the target website publishing native WebMCP support.
Reviewable evidence
To inspect it, open the desktop browser and a website with registered tools, then open Site Agent → WebMCP → Website. With a Harness model configured, switch to Use and request an operation covered by a listed tool. The walkthrough documents the existing discovery example and a separate X draft-editing example.
Support currently depends on DeepDeck's bundled Electron browser. This report does not claim conformance across every WebMCP API form or compatibility with other browser-agent implementations.
Would DeepDeck fit the agent implementation list, and is there a preferred evidence format for adding an entry? This issue supplies implementation metadata; it does not propose a specification change.
I maintain DeepDeck, an open-source macOS desktop client built on DeepSeek Harness. I would like to provide implementation information for consideration in Browser and Agent Implementation Status.
The current release is v1.0.39, with Apple Silicon and Intel Mac packages.
Browser and agent support
browser_context; invocation usesbrowser_webmcp_call.search_openaidiscovered on openai.com.Separate generated-tool feature
DeepDeck also has a Builder mode. An agent explores a site through browser interaction, implements tools for selected workflows, checks registration and execution, and stores the source and versions locally for later visits. Those tools are labelled Built with DeepDeck. This is a DeepDeck feature and is distinct from the target website publishing native WebMCP support.
Reviewable evidence
To inspect it, open the desktop browser and a website with registered tools, then open Site Agent → WebMCP → Website. With a Harness model configured, switch to Use and request an operation covered by a listed tool. The walkthrough documents the existing discovery example and a separate X draft-editing example.
Support currently depends on DeepDeck's bundled Electron browser. This report does not claim conformance across every WebMCP API form or compatibility with other browser-agent implementations.
Would DeepDeck fit the agent implementation list, and is there a preferred evidence format for adding an entry? This issue supplies implementation metadata; it does not propose a specification change.