Tree New Bee: Postman-Style API Debugging for DeepSeek Harness
HTTP endpoint testing now happens from inside DeepSeek Harness, eliminating the context switch to a separate tool for developers who already work there, and the zero third-party HTTP dependencies keep the plugin install light.
Tree New Bee API Client runs inside DeepSeek Harness (DSH) as a dual-part plugin: a Host half registers an HTTP requesting endpoint, and a Client half renders the entire user interface. The plugin supports GET, POST, PUT, PATCH, DELETE, HEAD, and OPTIONS, with Params and Headers editors, raw JSON body input, and timeout control. Responses show status, duration, size, and formatted JSON, with a 4MB truncation guard for oversized payloads.
The tree-based collections mirror Postman's folder hierarchy, including nested folders, rename via double-click, deletion confirmation, fuzzy search across folder names, request names, methods, and URLs, and one-click backfill to the editor. Environments define key-value variables that substitute into URL, Params, Headers, and Body using {{variable}} syntax, with an undefined variable left untouched. A built-in set of 14 common headers supports multi-select insertion with deduplication, plus custom header definitions that persist. The most recent 100 requests are stored in history and can be replayed in full.
Storing all collections, history, and environments in browser localStorage keeps the plugin self-contained but ties it to a single browser, so developers lose access to their API configs across machines unless they sync manually.
The decision to use Node's native fetch with AbortController means the plugin inherits the exact fetch behavior of the Node runtime, avoiding the dependency bloat of dedicated HTTP clients.
A dual-part architecture separates HTTP request execution (Host) from UI (Client), fitting DSH's plugin model and keeping the client-side footprint small.