🎩 You're Invited:Meet the Socket team at Black Hat in Las Vegas, August 3-6.RSVP
Sign In

dimcode-linux-x64

Package Overview
Dependencies
Maintainers
3
Versions
167
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

dimcode-linux-x64 - npm Package Compare versions

Comparing version
0.2.28
to
0.2.29-beta.0
+10
-2
bin/skills-assets/dim-modality/references/cli-recipes.md

@@ -21,6 +21,6 @@ # CLI Recipes

The JSON result includes `outputPath`. Resolve it to an absolute path and respond with:
The JSON result includes `outputs[].path`. Require at least one output, resolve each path to an absolute path, and respond with every output:
```
![Generated image](/absolute/path/to/artifacts/image.png)
![Generated image](</absolute/path/to/artifacts/image.png>)
```

@@ -56,2 +56,10 @@

The requested length must be passed with `--duration`. Writing a duration only
inside `--prompt` leaves the provider duration unset and may use its default.
Run this command through exec with `timeoutMs: 1800000`. If exec returns a
background task, wait for the completion notification and read its
`outputPath` to obtain the CLI JSON. The notification path is an exec log; the
generated video path is the JSON `outputs[].path`.
Respond with:

@@ -58,0 +66,0 @@

+8
-3

@@ -73,3 +73,3 @@ ---

5. After success, respond with the output in a format the user's client can render. Read the `outputPath` field from the JSON result and convert it to an absolute path (resolve relative paths against `cwd`). Then:
5. After success, respond with every output in a format the user's client can render. For media generation and transcription commands, read `outputs[].path` from the JSON result. `outputs` is required and must contain at least one item for those commands; a missing or empty array is a command-contract failure. Resolve any relative path against `cwd` before rendering it. Then:

@@ -83,4 +83,6 @@ | Output type | Response format | Example |

The absolute path is required — relative paths like `./artifacts/image.png` will not render in Desktop.
`dim ocr recognize` uses its dedicated success contract instead of `outputs`: require `ok: true` and a non-empty absolute `resultPath`. Return `text` or `textPreview` to the user, link `resultPath` as the complete structured result, and also link optional `textPath` and `pagesPreview[].imagePath` values. Missing `outputs` is valid for OCR. Treat a missing `resultPath` as a command-contract failure.
The absolute path is required — relative paths like `./artifacts/image.png` will not render in Desktop. Wrap Markdown destinations in angle brackets so paths containing spaces remain valid, for example `![Generated image](</workspace/my artifacts/image.png>)`.
## Operating Rules

@@ -93,3 +95,6 @@

- Put provider-specific parameters in a JSON object file and pass it with `--options <path>`.
- Video generation can be slow. Use a generous `--timeout`, and never claim completion unless an output file exists.
- When the user requests a video length, always pass it through the CLI `--duration <seconds>` flag. Duration text inside the prompt does not set the provider duration.
- Video generation can be slow. Use a generous CLI `--timeout` and set the exec tool's `timeoutMs` to the same value or higher. The exec timeout is independent, defaults to 300000 ms, and accepts at most 3600000 ms. For a longer CLI timeout, start exec with `runInBackground: true` and `timeoutMs: -1`.
- A video command may move to an exec background task after 30 seconds. Use `wait` for its completion notification; do not run `sleep` or provider polling commands. Then read the notification `outputPath`. That path is the exec log containing the CLI JSON, not the generated video. Parse the log's `outputs[].path` and render those media paths.
- Never claim completion unless an output file exists.
- For failed commands, explain `error.code`, `error.message`, and `details` from the JSON output. Do not hide the original provider or CLI error.

@@ -96,0 +101,0 @@ - Keep LLM model selection separate from multimodal defaults. A chat model change does not change modality defaults.

{
"name": "dimcode-linux-x64",
"version": "0.2.28",
"version": "0.2.29-beta.0",
"description": "dimcode binary for Linux x64",

@@ -5,0 +5,0 @@ "os": [

Sorry, the diff of this file is not supported yet