Introduction¶
In the agent development and debugging process for DeepSeek Harness (DSH), the Session ID is a key identifier for tracing logs, locating issues, or referencing specific conversations. The native Web UI does not provide a direct entry point for viewing and copying this ID, and developers usually need to look for it in the console or configuration files. The dsh-session-id plugin injects UI components to display and interact with this information directly on the right side of the conversation header.
What Is This¶
This plugin is maintained by developer LucienLL and is a client-side plugin. It addresses the need to quickly locate the current Session ID in the Web UI, without manually searching for or capturing console logs.
Core Features¶
- Header display: Displays the current Session ID on the right side of the Web UI header.
- Interaction and feedback: If the ID is too long, it is truncated automatically; hovering over the ID shows the full content. Clicking the ID copies it to the clipboard, and the interface briefly displays “Copied” or “Copy failed” (red prompt).
Installation and Activation¶
Install the plugin by running the following command:
dsh plugin --profile web add dsh-session-id
After installation, restart the dsh web process to activate the plugin.
Implementation Details¶
This is a pure client-side plugin. It renders using the sessionId variable automatically injected by the framework by injecting the official slot conversation.session.header.utilities (scope: session), without relying on host-side logic support.
Use Cases and Notes¶
This plugin is suitable for users who need to copy Session IDs frequently during debugging or everyday use. As a pure client-side plugin, its runtime environment is limited by the permissions of the current dsh process. Before installation, it is recommended to review the source code and the license (MIT).
Conclusion¶
This plugin significantly reduces the effort required to obtain the Session ID in the Web UI through simple UI injection. More information can be accessed via Plugin Catalog or GitHub repository.