@lotagate/cli 0.1.11 → 0.1.13

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
@@ -135,7 +135,7 @@ lotagate video status <operation-id>
135
135
  lotagate video download <operation-id>
136
136
  ~~~
137
137
 
138
- All media inputs and outputs are confined to a trusted workspace. 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>. 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.
138
+ 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
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
 
@@ -149,7 +149,7 @@ lotagate trust grant
149
149
  lotagate trust revoke
150
150
  ~~~
151
151
 
152
- In a trusted project, local tools remain bounded by workspace path validation, symlink escape checks, structured shell arguments, output and timeout limits, and the approval policy. A tool approval allows or denies that one action; the TUI can remember a narrow local rule for a previously approved operation.
152
+ In a trusted project, agent filesystem and shell tools remain bounded by workspace path validation, symlink escape checks, structured shell arguments, output and timeout limits, and the approval policy. Explicit media input paths and media output directories are separate user-supplied local paths and may be outside the workspace. A tool approval allows or denies that one action; the TUI can remember a narrow local rule for a previously approved operation.
153
153
 
154
154
  Project policy lives in <project>/.lotagate/settings.json. For example:
155
155
 
@@ -244,7 +244,7 @@ lotagate goal pause <session-id>
244
244
  lotagate goal resume <session-id>
245
245
  ~~~
246
246
 
247
- Trusted agents can delegate bounded research or explicitly scoped worker tasks to subagents. Child agents cannot create unrestricted nested work, and a safety-limit stop returns a resumable handoff rather than silently continuing.
247
+ Trusted agents can proactively delegate bounded independent research or explicitly scoped worker tasks to subagents when a request benefits from parallel work. The parent agent remains responsible for integration, verification, and the final response; child agents cannot create unrestricted nested work, and a safety-limit stop returns a resumable handoff rather than silently continuing. Long-running agent runs automatically compact their context between model/tool iterations at the configured context threshold while preserving a durable summary for resumed sessions.
248
248
 
249
249
  ## Supported hosts
250
250
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lotagate/cli",
3
- "version": "0.1.11",
3
+ "version": "0.1.13",
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.11",
73
- "@lotagate/cli-native-linux-x64-gnu": "0.1.11",
74
- "@lotagate/cli-native-macos-arm64": "0.1.11",
75
- "@lotagate/cli-native-macos-x64": "0.1.11",
76
- "@lotagate/cli-native-windows-arm64": "0.1.11",
77
- "@lotagate/cli-native-windows-x64": "0.1.11"
72
+ "@lotagate/cli-native-linux-arm64-gnu": "0.1.13",
73
+ "@lotagate/cli-native-linux-x64-gnu": "0.1.13",
74
+ "@lotagate/cli-native-macos-arm64": "0.1.13",
75
+ "@lotagate/cli-native-macos-x64": "0.1.13",
76
+ "@lotagate/cli-native-windows-arm64": "0.1.13",
77
+ "@lotagate/cli-native-windows-x64": "0.1.13"
78
78
  },
79
79
  "devDependencies": {
80
80
  "@eslint/js": "9.39.5",