跪拜 Guibai
← All articles
Artificial Intelligence · Programmer

Tree New Bee: Postman-Style API Debugging for DeepSeek Harness

By 程序员Oak ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

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.

Summary

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.

Takeaways
— Package name is @oakzhong/dsh-tree-new-bee-api-client, version 1.0.3.
— Entry point is "Tree New Bee 接口请求" in the left sidebar.
— Supports seven HTTP methods: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS.
— Built-in set of 14 common request headers with defaults.
— Response body can be viewed as formatted JSON or raw text.
— Oversized responses are truncated at 4MB.
— History keeps the last 100 requests, each replayable with full snapshot.
— Data persists in localStorage under keys like dsh-tree-new-bee-api-client.collection.v1.
— Installation via plugin manager using the GitHub URL or package name.
— The Host half uses Node's native fetch with AbortController for timeouts.
— The Client half uses React without JSX, relying on React.createElement.
— The plugin has built-in Chinese and English localization.
Conclusions

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.

Concepts & terms
DSH (DeepSeek Harness)
The AI development environment or harness where this plugin runs, providing a sidebar, locale system, and plugin loader for extensions.
Cordis bundle
A plugin packaging format used by DSH, typically with a cordis.patch.yml file to inject loader entries and define both Host and Client parts.
Source: juejin.cn ↗ Google Translate ↗ Backup ↗