@lotagate/cli 0.1.18 → 0.1.20

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +3 -3
  2. package/package.json +7 -7
package/README.md CHANGED
@@ -111,9 +111,7 @@ lotagate goal run "Audit the project configuration" --max-turns 20
111
111
  lotagate agent stdio
112
112
  ~~~
113
113
 
114
- lotagate exec --json and lotagate exec --jsonl provide structured output for automation. lotagate agent stdio exposes the versioned JSONL protocol; it validates requests, bounds in-flight work, supports cancellation, and emits safe structured errors instead of raw provider failures. The Desktop bridge is available through `lotagate agent desktop`; its version-1 protocol supports image and file uploads with `attachment.begin`, ordered `attachment.chunk`, `attachment.complete`, and `turn.start` attachment references. Desktop turns run in streaming mode and forward assistant text deltas as they arrive. Image bytes are normalized by the CLI; other files are encoded as SDK-compatible `input_file` data parts. All bytes are chunked before they cross JSONL's bounded line size, and existing Desktop turns without attachments plus all standalone CLI surfaces keep their current behavior.
115
-
116
- Desktop turns also emit structured orchestration events when applicable: `plan.started`, `plan.step.started`, `plan.step.completed`, `plan.completed`, `plan.failed`, and `subagent.created`, `subagent.started`, `subagent.activity`, `subagent.completed`, `subagent.completed_with_warning`, `subagent.failed`, or `subagent.cancelled`. These events contain bounded plan metadata and presentation-safe subagent identity, status, last action, and handoff information; they do not expose child-agent content or tool payloads.
114
+ lotagate exec --json and lotagate exec --jsonl provide structured output for automation. lotagate agent stdio exposes the versioned JSONL protocol; it validates requests, bounds in-flight work, supports cancellation, and emits safe structured errors instead of raw provider failures.
117
115
 
118
116
  Run lotagate help for the complete direct-command reference. The executable command catalog is the source of truth for command arguments and flags.
119
117
 
@@ -137,6 +135,8 @@ lotagate video download <operation-id>
137
135
 
138
136
  Media input files supplied explicitly with `image edit`, `audio transcribe`, `audio translate`, or `exec --image` may be anywhere on the local machine; relative paths resolve from the current directory. Generated artifacts default to dedicated directories below <workspace>/tmp/. Use --out <filename> for a filename stem without an extension and optionally combine it with --out-dir <directory>; `--out-dir` accepts an absolute or relative local directory inside or outside the workspace. The CLI chooses the extension from the command's output format: image `--output-format`, audio `--response-format`, or `mp4` for video. Without --out, the CLI derives a safe filename from the input prompt or source file. The CLI does not overwrite an artifact unless --force is supplied with --out. Agent filesystem and shell tools remain confined to the trusted workspace.
139
137
 
138
+ Direct media commands keep their human-readable saved-path output. Protocol callers that provide the optional structured output sink also receive validated media metadata for each generated artifact; this does not change standalone terminal output.
139
+
140
140
  Video creation is asynchronous. It normally waits for the gateway operation and downloads the final artifact. Use --no-wait to return the operation ID, then use video status and video download later. The CLI never polls a provider directly; the LotaGate gateway owns provider credentials and polling.
141
141
 
142
142
  ## Trust, local tools, and approvals
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lotagate/cli",
3
- "version": "0.1.18",
3
+ "version": "0.1.20",
4
4
  "description": "Enterprise-grade terminal client for LotaGate AI agents.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -69,12 +69,12 @@
69
69
  "tiktoken": "^1.0.22"
70
70
  },
71
71
  "optionalDependencies": {
72
- "@lotagate/cli-native-linux-arm64-gnu": "0.1.18",
73
- "@lotagate/cli-native-linux-x64-gnu": "0.1.18",
74
- "@lotagate/cli-native-macos-arm64": "0.1.18",
75
- "@lotagate/cli-native-macos-x64": "0.1.18",
76
- "@lotagate/cli-native-windows-arm64": "0.1.18",
77
- "@lotagate/cli-native-windows-x64": "0.1.18"
72
+ "@lotagate/cli-native-linux-arm64-gnu": "0.1.20",
73
+ "@lotagate/cli-native-linux-x64-gnu": "0.1.20",
74
+ "@lotagate/cli-native-macos-arm64": "0.1.20",
75
+ "@lotagate/cli-native-macos-x64": "0.1.20",
76
+ "@lotagate/cli-native-windows-arm64": "0.1.20",
77
+ "@lotagate/cli-native-windows-x64": "0.1.20"
78
78
  },
79
79
  "devDependencies": {
80
80
  "@eslint/js": "9.39.5",