Install
Inside DeepSeek Harness, with dsh-market
dsh plugin --profile web add dshmarket
Or from the command line
dsh plugin --profile web add @ottermind/sqlx-dsh
Installing runs third-party code with your own permissions — it can read your files, use your credentials and reach the network. Review the source first, and pin a commit (github:owner/repo#sha) when you can.
README
Native SQLX tools for DeepSeek Harness. The plugin registers six defineTool tools and calls the
sqlx CLI for each one, so encrypted credentials, TLS policy, worker downloads and local result
pages stay CLI responsibilities.
Install
dsh plugin --profile <profile> add @ottermind/sqlx-dsh
cordis.patch.yml is declared as dsh.bundle.patch, so installing the package appends the plugin
row to the profile's bundle stack; no profile file edits are needed. Remove it with
dsh plugin --profile <profile> remove @ottermind/sqlx-dsh.
Requirements
- DeepSeek Harness 0.1.5 or later.
@deepseek-ai/dsh-tools(peer dependency) — bundled with dsh, and the profile installer runs pnpm withautoInstallPeers: false, so nothing extra is installed.- The
sqlxCLI 0.1.15 or later. The plugin looks forSQLX_BIN, thensqlxonPATH, then the official user-level installation (~/.local/bin/sqlx,%LOCALAPPDATA%\Programs\SQLX\sqlx.exe, orSQLX_INSTALL_DIR), and when none of them exists it installs the CLI itself withnpx -y @ottermind/sqlx@latest --target dsh. Adding the plugin is therefore the only setup step.
Tools
| Tool | Purpose | May modify data |
|---|---|---|
sqlx_datasource_list |
List saved datasources (no secrets) | no |
sqlx_datasource_show |
Show one datasource by UUID or unique name | no |
sqlx_datasource_test |
Test connectivity; executes no SQL | no |
sqlx_sql_execute |
Execute statements, return the table-shaped result with a preview (full returns every row) |
yes |
sqlx_results_rows |
Read one page of a stored result; read-only | no |
sqlx_sql_view |
Execute once, return a local result-page URL | yes |
sqlx_prefetch |
Download mysql, postgres, oracle, sqlserver, ui, skill or all |
downloads only |
The two execution tools describe the authorization rule themselves: run them only after the user authorized that exact operation and scope. Results are never replayed automatically.
Credentials
Save credentials in the SQLX data directory (sqlx datasource add --connection-stdin, or the local
sqlx ui page). A datasource created with --username-env/--password-env reads environment
variables at execution time, and a harness started from a GUI usually cannot see your shell
environment.
Links
- Repository: https://github.com/OtterMind/sqlx
- Integration guide: https://github.com/OtterMind/sqlx/blob/main/integrations/README.md
Comments
Comments live in GitHub Discussions. Sign in with GitHub to post or react.