By Jetformat
The Jetformat Harness plugin is an adapter that invokes the local document CLI. Installing the adapter and installing the binary are separate steps. The machine running the tool must be able to find both the executable and the source file.
Add the plugin
dsh plugin --profile web add github:jetformat/dsh-plugin
dsh web
Source: jetformat/dsh-plugin.
Available tools
jetformat_to_pdf: runsword to-pdf,excel to-pdf, orppt to-pdfby file extension.jetformat_textfor existing text layers.jetformat_validatefor supported file checks.jetformat_pdffor info, merge, extract, and render.
Each tool shells out to the local CLI and returns its output. Keep one real input path per command and let the process exit code decide whether the job succeeded.
Review the installation steps.
Verify one tool invocation
- Run
jetformat --versionin the same environment that launches Harness. - Confirm that a free
jetformat validatecommand can read a real supported input path. - Add the plugin using the command above, then start the configured profile.
- Request a small conversion and check the returned command outcome before using its output.
- Read the resulting PDF page count and open any requested previews.
Choose the tool for the requested result
| Request | Adapter tool | What to verify |
|---|---|---|
| Convert an Office file | jetformat_to_pdf |
Written PDF and page count |
| Read existing text | jetformat_text |
Completeness and reading order |
| Check the input | jetformat_validate |
Validation outcome |
| Inspect or process a PDF | jetformat_pdf |
Result of the selected PDF verb |
Diagnose the execution boundary
If the command works in your terminal but fails in Harness, compare the execution environment, PATH, working directory, and source path. A plugin registration does not prove that the process can read a file on another machine. Use an explicit input path when the working directory is uncertain.
Free reads need no account. Metered writes require the CLI’s account authorization on the executing machine. If billing refuses a job, follow CLI login and credits rather than repeatedly reinstalling the adapter. A successful 5-page conversion uses 5 credits; rendering 1 preview adds 1 credit. These are example counts, not a promise about the user’s file.