Configuring dsh-data-agent
DeepSeek Harness loads the data-agent preset into a profile and preloads its database tools and commands. The profile configuration can add non-standard client locations or pin a client executable:
| Key |
Purpose |
clients.<database>.searchPaths |
Directories to search before system-standard locations |
clients.<database>.command |
An absolute path to the client command |
For example, clients.mysql.searchPaths can contain /opt/company/mysql/bin, while clients.mysql.command can point directly to /opt/company/mysql/bin/mysql. The current profile's PATH takes precedence. DeepSeek Harness also checks the client HOME environment variable and common Windows, macOS and Linux installation locations.
dsh-data-agent commands
In dsh-tui, DeepSeek Harness provides the /database command group for the active connection:
/database connect opens the connection form.
/database status shows the current connection.
/database test tests it.
/database disconnect closes it.
The data-agent mode retains str_replace_editor, sql-query, sql-write and sql-cmd. Web profiles additionally load render-analysis; dsh-tui does not load its chart or browser dependencies.
Requirements for dsh-data-agent
DeepSeek Harness must be able to reach the target database from the local machine. The relevant client must be installed and available through PATH, a recognised installation location, searchPaths or command. SQLite is commonly available with macOS or Linux; MySQL, PostgreSQL, Oracle, Hive and Impala require their respective command-line clients.
Behaviour and safety
The agent can inspect table structures, execute SQL, use errors and results to revise its analysis, and save analysis files such as analysis/repurchase.sql when asked. Web reports are persisted with the session log and are read-only. Read-only mode and a read-only account restrict changes; otherwise requested updates or management statements can run with the account's permissions. Connections are isolated between sessions, and TUI passwords are masked and not restored.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub