Preface

When building automated tasks with DeepSeek Harness (DSH), the Agent needs to access real business backends. Common issues include losing login state after the browser closes, or the Agent not knowing which account to use. This plugin provides local-first platform account and persistent browser session management capabilities, helping the Agent know “which account to use, which platform to access, and through which browser data directory.”

What It Is

This is a local-first plugin for platform account and persistent browser session management for DeepSeek Harness. It is neither a password manager that logs in on behalf of people, nor an automation tool responsible for clicking and filling web pages; rather, it is the account directory, session container, and browser lifecycle layer between the Agent and real business backends.

Core Capabilities

Platform Account Management

  • Supports adding, editing, archiving, restoring, and permanently removing account records.
  • Platform names can be entered freely and are not limited to fixed enumerated values.
  • Each account record is uniquely identified by “platform name + account name”.

Browser Data Directory Management

  • Fixed user and type: Uses Chromium’s Default user and supports Google Chrome and Microsoft Edge.
  • Isolation and sharing: Supports two modes: dedicated directories and shared directories.
    • Dedicated directory: Suitable for multiple accounts on the same platform or scenarios requiring strict Cookie isolation.
    • Shared directory: Suitable for different trusted platforms under the same organization, allowing sharing of a single browser process.
  • New directory restrictions: A new data directory must be empty to avoid overwriting existing browser data. After creation, rebinding or moving to another directory is not supported.
  • Lifecycle: Supports archiving and two deletion modes: removing the registration while keeping local files; or deleting local data as well (only applicable to directories under the plugin’s default root whose ownership markers match).
  • Cookie reading: Reads session cookies in the current browser context via CDP.
  • Persistence: Writes session cookies that are safe to copy back to the original directory.
  • Keep-alive: Supports scheduled session keep-alive by accessing the backend and syncing cookies to maintain login state.

Typical Usage

  1. Create an account in Platform Management, and enter the platform name, account name, and backend URL.
  2. Create a dedicated browser data directory for the account, or reuse an existing trusted directory.
  3. Open the platform and manually complete login in the Chrome/Edge instance launched by the plugin.
  4. Click “Detect Login Status” to confirm that the backend can be accessed normally.
  5. Later, have the Agent open that platform account; the plugin will reuse the same browser data directory.
  6. Sync session cookies before the browser closes; on restart, Chromium restores the local state.

Permissions and Security

  • Minimal Agent permissions: The Agent cannot see cookies, passwords, browser data directories, or the CDP endpoint.
  • Dangerous deletion validation: Physically deleting a browser data directory requires proof of ownership. Only directories under the plugin’s default root whose ownership markers exactly match are allowed to be physically deleted.
  • No permanent login-free access: The plugin can only preserve browser state that can be saved locally and cannot bypass CAPTCHAs or risk-control mechanisms.

Applicable Scenarios and Notes

  • This plugin runs with the current DSH process permissions.
  • Before installing, check the source code and license (MIT License).
  • It has no affiliation, authorization, cooperation, or compatibility relationship with Accio Work.

Conclusion

By using explicit data directory ownership and isolation mechanisms, this plugin solves account mapping confusion and login state loss when the Agent operates business backends.

Plugin Directory
GitHub Repository