@lotagate/cli 0.1.9 → 0.1.11

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 +12 -1
  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 <file> for an exact path or --out-dir <directory> for a directory. The CLI does not overwrite an artifact unless --force is supplied with --out.
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.
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
 
@@ -187,6 +187,17 @@ lotagate plugin install <source> --scope user --sha256 <sha256>
187
187
 
188
188
  Plugins are declarative packages with .lotagate-plugin/plugin.json. The CLI copies and validates them atomically; it does not run package-install scripts. Skills are validated SKILL.md directories and can be user, project, plugin, or immutable bundled skills. Project hooks are loaded only from <project>/.lotagate/hooks/ in a trusted project.
189
189
 
190
+ Each project hook is a JSON file with an `event`, executable `command`, optional string-array `args`, and a `timeoutMs` between 100 and 120000. Supported lifecycle events are `session.start`, `prompt.before`, `tool.before`, `tool.after`, `response.after`, and `session.end`. The `tool.before` event runs immediately before a local or MCP tool is executed; `tool.after` runs after it completes.
191
+
192
+ ~~~json
193
+ {
194
+ "event": "tool.before",
195
+ "command": "node",
196
+ "args": [".lotagate/hooks/audit.mjs"],
197
+ "timeoutMs": 10000
198
+ }
199
+ ~~~
200
+
190
201
  ## Configuration and data
191
202
 
192
203
  Configuration is merged in this order, with later layers taking precedence:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lotagate/cli",
3
- "version": "0.1.9",
3
+ "version": "0.1.11",
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.9",
73
- "@lotagate/cli-native-linux-x64-gnu": "0.1.9",
74
- "@lotagate/cli-native-macos-arm64": "0.1.9",
75
- "@lotagate/cli-native-macos-x64": "0.1.9",
76
- "@lotagate/cli-native-windows-arm64": "0.1.9",
77
- "@lotagate/cli-native-windows-x64": "0.1.9"
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"
78
78
  },
79
79
  "devDependencies": {
80
80
  "@eslint/js": "9.39.5",