Configuration

The install patch reads everything from the environment, so most deployments need no configuration. To override, add an entry to ~/.dsh/profiles//cordis.patch.yml:

- id: litefuse
  config:
    environment: staging
    agentName: My Agent
    requestInput: delta
    tags: [dsh, team-platform]

An id-targeted patch replaces the whole config, so restate the fields you keep.

Field	Default	Meaning
`enabled`	`true`	`false` mounts the plugin and exports nothing
`baseUrl`	`https://litefuse.cloud`	Litefuse endpoint; the OTLP trace path is appended
`publicKeyEnv` / `secretKeyEnv`	`LITEFUSE_PUBLIC_KEY` / `LITEFUSE_SECRET_KEY`	credential references; `LANGFUSE_*` is the fallback
`environment`	`production`	Litefuse tracing environment on every span
`agentName`	`DeepSeek Harness`	the name in `— Turn N`
`userId`	`$USER`	trace-level `user.id`
`tags`	`[dsh]`	trace tags, beside the generated `model:`
`release`	—	optional release identifier on every trace
`requestInput`	`full`	`full` sends the whole request; `delta` only the messages added since the last call; `none` omits inputs
`maxValueChars`	`1000000`	truncation budget per input/output, the trace input included
`delegationTools`	`[subagent, subagent_fork]`	tool names whose in-flight call hosts a subagent container
`exportDelayMillis`	`1000`	how long an ended span waits for company before its batch posts
`requestTimeoutMillis`	`10000`	per-request deadline
`shutdownTimeoutMillis`	`3000`	outer bound on the drain at teardown
`logFile`	`$DSH_HOME/litefuse.log`	the integration's own log
`debug`	`$DSH_LITEFUSE_DEBUG`	keep verbose lines

Credentials are references, not values: configuration names an environment variable, and the value comes from the harness credential store (~/.dsh/.credentials.yaml) when one is mounted, otherwise from the process environment that ~/.dsh/.env feeds. Nothing here ever writes a key to a file, and only the public key's first ten characters are ever logged.

dsh-litefuse-plugin

安装

说明文档

Configuration