skaile-cli 5.14.0 → 5.15.1

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 (3) hide show
  1. package/CHANGELOG.md +102 -0
  2. package/README.md +1 -1
  3. package/package.json +2 -2
package/CHANGELOG.md CHANGED
@@ -1,5 +1,107 @@
1
1
  # Changelog
2
2
 
3
+ ## 5.15.1
4
+
5
+ ### Patch Changes
6
+
7
+ - Updated dependencies [[`39a85d3`](https://github.com/skaile-ai/workspaces/commit/39a85d3eeac178e8852d56d92267f9fee0a8462d)]:
8
+ - @skaile/workspaces@5.15.1
9
+
10
+ ## 5.15.0
11
+
12
+ ### Minor Changes
13
+
14
+ - [#1073](https://github.com/skaile-ai/workspaces/pull/1073) [`b4631ac`](https://github.com/skaile-ai/workspaces/commit/b4631acb6071f5730732ff487062b300908960da) Thanks [@mortegro](https://github.com/mortegro)! - A hand edit of an agent instance file (`.claude/agents/default.md`, `.claude/agents/<id>.md`, and the omp and Codex files of the same instances) is drift: it is listed in the lock `rendered:` list of the agent the instance binds to, `check`, `doctor` and `outdated` exit 1, and `install --locked` prints `Restored <file>` (p812, p304).
15
+
16
+ `skaile rebuild <name>` takes an `agent:` ref, an instance id, an agent name or a path. A name that matches nothing exits 1 and rebuilds nothing (p814).
17
+
18
+ `skaile show` no longer lists the instance renderings as assets of publisher `unknown` (p813).
19
+
20
+ The connector prompt of a session without `connector_*` tools (omp) names the `skaile connector` CLI, not the tools (p810). `buildConnectorPromptSection` takes the option `toolsMounted`.
21
+
22
+ Docs: `drivers.md` says that Codex 0.159 does not load `.codex/agents/*.toml` as sub-agents (p428).
23
+
24
+ - [#1073](https://github.com/skaile-ai/workspaces/pull/1073) [`b4631ac`](https://github.com/skaile-ai/workspaces/commit/b4631acb6071f5730732ff487062b300908960da) Thanks [@mortegro](https://github.com/mortegro)! - `validate`, `library index`, `library publish` and `add` give one verdict for a library.
25
+
26
+ A symlink anywhere in a library is refused, also at the root level and a symlinked asset directory (p520). A manifest `root:` that leaves the library (`..`, absolute, through a symlink) is refused (p701). An asset renamed in its own file is renamed in place by `library index`; `validate` and the publish plan refuse a stale entry (p700). `library index` and the plan run the agent checks of `validate` (p415).
27
+
28
+ `library create --dir` refuses a path through a symlink inside the library (p702). `library init <name> --path <dir>` refuses a directory that holds a symlink and registers nothing (p703). The publish plan names a `.env`, a private key or a certificate as a secret, and the scaffolded `.gitignore` covers `.env`, `*.swp`, `*~`, `*.bak`, `*.log` (p704, p224).
29
+
30
+ `add` and `install` refuse an asset whose version is not semver, with the `validate` message (p743). The 15-digit limit of a version number is documented (p705).
31
+
32
+ `validate <file>` and `validate <empty directory>` exit 1 without `All manifests valid` (p745). A project `validate .` skips `.claude`, `.codex` and `.omp` (p853). `skaile create` is documented (p854).
33
+
34
+ `asset import` and `asset migrate` leave out `*.log`, `*.bak`, `*.swp` and `*~`. `asset migrate --mode link` is removed; `--mode move` refuses a source that holds a symlink (p224).
35
+
36
+ - [#1073](https://github.com/skaile-ai/workspaces/pull/1073) [`b4631ac`](https://github.com/skaile-ai/workspaces/commit/b4631acb6071f5730732ff487062b300908960da) Thanks [@mortegro](https://github.com/mortegro)! - Consume fixes from the 5.13.0 critique (p220, p544, p720, p721, p722, p723, p755, p756, p757, p758, p793, p855).
37
+
38
+ - `remove` no longer deletes a folder that no lock entry owns. It keeps it, prints why, and exits 1. `remove --force` deletes it. `install` refuses such a folder like `add` does. `install --force` replaces it (p720, p721).
39
+ - `update` skips the catalog refresh when no locked asset comes from the catalog. When the refresh is needed and fails, `update` exits 1 at once after 5 s, for a REST-framed catalog (any URL but `https://skaile.store`) as well as the store (p544).
40
+ - `source add --publisher` on a registered URL with another publisher exits 1 and names the declared refs it breaks. `--force` changes it (p722).
41
+ - `library link` says when the remote already has commits and names the `pull --rebase` command (p723).
42
+ - `install` and `install --locked` print `Restored <file>` for a deleted file they write back, and `check` advises `install --locked` (p755).
43
+ - `outdated` lists an asset that `update` would move to another library as `origin changes <old> → <new>` (p756).
44
+ - `search --local` re-registers a source reader library that another project's `source remove` dropped (p757).
45
+ - The publish plan lists the modified and deleted tracked files that `git add -A` also publishes (p758).
46
+ - A source asset is locked with the version of its asset file, as `search` and `info` list it (p793, p855).
47
+ - An agent instance whose locked library is not registered names the library fix, not `install --locked` (p220).
48
+
49
+ - [#1073](https://github.com/skaile-ai/workspaces/pull/1073) [`b4631ac`](https://github.com/skaile-ai/workspaces/commit/b4631acb6071f5730732ff487062b300908960da) Thanks [@mortegro](https://github.com/mortegro)! - `skaile session show`, `switch`, `delete` and `skaile resume --session` accept the 8-character run id that `skaile session list` prints (p851). A prefix that matches two sessions exits 1 and lists the matches. The runner exports `resolveSessionId`.
50
+
51
+ Docs: tutorial 01 step 3 says that `owner/repo` expands to the SSH URL (p858). Tutorial 02 says to skip `providers add anthropic` after tutorial 01 (p852). The flow example in `concepts/flow-execution.md` says that the skills it names must exist (p856). `serve.md` has the real loopback warning (p843). `protocol-v2.md` no longer prints a fixed `capabilitySignature` (p844). `client-server-architecture.md` no longer lists `configure` and `state_action` as live commands (p837). The bridge READMEs show `npm i` (p845). `migration-v2-to-v3.md` and `manifest-schema.md` say how to get the `migrate-skaile-manifest` skill (p674). `install <ref>` is described as a store install (docs defect).
52
+
53
+ - [#1073](https://github.com/skaile-ai/workspaces/pull/1073) [`b4631ac`](https://github.com/skaile-ai/workspaces/commit/b4631acb6071f5730732ff487062b300908960da) Thanks [@mortegro](https://github.com/mortegro)! - Harnesses and drivers (5.13.0 critique: p590, p598, p637, p770, p771, p772, p773, p811, p850).
54
+
55
+ - The `claude-sdk` and `codex` drivers (and `skaile serve`) load their SDK from the project's `node_modules` first, then from next to the skaile install. A missing SDK is one line that names both places and the install command (p770). The connector tool servers use the same lookup.
56
+ - The supported `@openai/codex-sdk` range is `>=0.160.0 <0.170.0` (was `^0.133.0`). A ChatGPT-login run with a model the login cannot use ends with one sentence, and a rejected key reads `codex driver: the API key was rejected (401).` instead of `Reconnecting... n/5` (p771, p598).
57
+ - The codex driver warns about a registry entry it cannot address only when that entry is the selected one, and logs the others at debug level (p773).
58
+ - The omp private home links only the login files and copies `config.yml`; sessions, history, `mcp.json` and extensions stay private, and the home is deleted when the run ends; each run gets its own home directory, so one run's cleanup cannot remove another's (p811).
59
+ - The omp credential hint (`skaile providers add <id> --credential env:<ID>_API_KEY`) is applied on every error path: start failure, response errors, turn errors and nested `agent_run` (p637).
60
+ - `check` and `doctor` test every rendered file of a locked agent (`.codex/skaile-agents/<name>.md`, `.omp/agents/<name>/agent.yaml` and `SOUL.md`), not only the primary one (p590).
61
+ - A project reads `dependencies:` only from its own `skaile.yaml`; what `add --global` declared no longer shows up in a project's `list`, `check`, `outdated` or `install` (p772).
62
+ - `skaile resume` prints the same one `✗` line as `run` when the driver cannot start, and continues the session it was given: same run id, driver thread resumed, no second session (p850).
63
+
64
+ - [#1073](https://github.com/skaile-ai/workspaces/pull/1073) [`b4631ac`](https://github.com/skaile-ai/workspaces/commit/b4631acb6071f5730732ff487062b300908960da) Thanks [@mortegro](https://github.com/mortegro)! - `skaile serve` with a bad `--port` (`abc`, `99999`, `-1`), a `--host` this machine does not have or cannot resolve, or a missing or empty `SKAILE_WS_AUTH_TOKEN_FILE` prints one line and exits 1, with no Node stack trace (p830, p832).
65
+
66
+ `serve` exits 1 after it sent `incompatible_protocol` (p835). On macOS, `serve --host <address>` also probes the port on all interfaces, so it no longer starts on a port that another process holds on `*` (p842); Linux needs no probe, as its bind already fails.
67
+
68
+ A `local` connector with a `mountPath` that does not exist fails to connect and the runner no longer creates the directory; a path outside the project logs a warning (p833). `skaile validate` fails on a connector with a missing or duplicate `id`, an unknown `access`, or a missing `mountPath`. The decoder reports an unknown `access` as `connector_invalid_access` (p834).
69
+
70
+ A `prompt` without a string `prompt`, or a message that is not a JSON object, gets a non-fatal validation `error` event instead of silence (p839). A reconnect no longer replays `status idle` twice (p831). `--session-id` help says it only labels the session; `--resume-session-id` restores it (p838).
71
+
72
+ `skaile plugin install` without a `skaile.yaml` exits 1 with `run skaile init first` and creates no file; `plugin remove` says there is no project. Installing a spec that is already declared prints `already declared` instead of `Updated` (p840, p841).
73
+
74
+ - [#1073](https://github.com/skaile-ai/workspaces/pull/1073) [`b4631ac`](https://github.com/skaile-ai/workspaces/commit/b4631acb6071f5730732ff487062b300908960da) Thanks [@mortegro](https://github.com/mortegro)! - `skaile install <ref>` without `#<version>` exits 1 before any call and says the version is missing. A versioned ref the store does not hold says `<ref> is not in the store`. The raw `400 Bad Request` and `404 Not Found` are gone (p740).
75
+
76
+ `skaile update` prints `Lock file written` whenever it rewrites `skaile.lock.yaml`, also when it only adds `rendered:` entries after an upgrade (p741).
77
+
78
+ A lock that locks a flow by the old slug of its `name:` gets a rename hint from `check`, `install`, `install --locked` and `update`: the library holds it as `flow:@pub/<id>` now, run `skaile remove` and `skaile add` (p742).
79
+
80
+ `skaile remove --global` of an omp asset also removes the copies that 5.12.0 wrote to `~/.omp/skills/` and `~/.omp/agents/` (p744).
81
+
82
+ `check` and `doctor` exit 1 when a skill that a flow names in `run.assets` (or a bundle `dependencies:` entry) was removed with `--force`, with `<flow> requires <skill> (run skaile install)`. Tutorial 03 says the same (p857).
83
+
84
+ `install`, `install --locked` and `update` print `Rewrote <file> (agent render changed)` when they rewrite a rendered agent file that a lock without `rendered:` did not cover and whose bytes change (p561).
85
+
86
+ Assets of one source locked at different commits (store assets added one by one) write the same `sources:` row from `add` and `install`, so the first `install` after the `add`s no longer prints `Lock file written` for a lock that did not change (p790).
87
+
88
+ - [#1073](https://github.com/skaile-ai/workspaces/pull/1073) [`b4631ac`](https://github.com/skaile-ai/workspaces/commit/b4631acb6071f5730732ff487062b300908960da) Thanks [@mortegro](https://github.com/mortegro)! - `install` and `update` no longer call a locked store asset `Missing` when the store cannot be asked. With `catalog.cache_ttl: 0` and with `update --no-catalog` the deployed copy is kept and the line says `kept as locked`, exit 0. A store that is down ends `Failed` with `store unreachable: could not check <ref> for updates`, exit 1. `update --no-catalog` never asks the store, also in the re-deploy (p792, p799).
89
+
90
+ `add <ref>#<version>` for a version the store does not hold lists the versions it has (p791).
91
+
92
+ A `SKAILE_GITHUB_PAT` that GitHub rejects no longer breaks a public repo: it is read anonymously. For a private repo the error says the token was rejected, and the raw `GET … 401` log line is gone (p794).
93
+
94
+ A store `mcp-server` with a `payload` has it downloaded, checked against its sha256 and written to `.skaile/assets/mcp-server/<name>/` before the entry goes into `.mcp.json`; bytes that miss the pin skip the entry with the reason. An entry whose url still holds a `<slug>` placeholder is skipped with a warning that names it (p795, p797).
95
+
96
+ The `requires` of a store agent are locked (`requires:` on the lock entry), so `why` names the agent, `remove` of a skill the agent requires is refused without `--force`, and `remove` of the agent prunes the skills only it required (p796).
97
+
98
+ `info` of a deployed agent prints its description and the locked version, without the asset scan warning (p798).
99
+
100
+ ### Patch Changes
101
+
102
+ - Updated dependencies [[`b4631ac`](https://github.com/skaile-ai/workspaces/commit/b4631acb6071f5730732ff487062b300908960da), [`b4631ac`](https://github.com/skaile-ai/workspaces/commit/b4631acb6071f5730732ff487062b300908960da), [`b4631ac`](https://github.com/skaile-ai/workspaces/commit/b4631acb6071f5730732ff487062b300908960da), [`b4631ac`](https://github.com/skaile-ai/workspaces/commit/b4631acb6071f5730732ff487062b300908960da), [`b4631ac`](https://github.com/skaile-ai/workspaces/commit/b4631acb6071f5730732ff487062b300908960da), [`b4631ac`](https://github.com/skaile-ai/workspaces/commit/b4631acb6071f5730732ff487062b300908960da), [`b4631ac`](https://github.com/skaile-ai/workspaces/commit/b4631acb6071f5730732ff487062b300908960da), [`b4631ac`](https://github.com/skaile-ai/workspaces/commit/b4631acb6071f5730732ff487062b300908960da)]:
103
+ - @skaile/workspaces@5.15.0
104
+
3
105
  ## 5.14.0
4
106
 
5
107
  ### Minor Changes
package/README.md CHANGED
@@ -14,7 +14,7 @@ in the project before the first `run` or `repl`:
14
14
  | Driver | Install |
15
15
  |---|---|
16
16
  | `claude-sdk` (default) | `npm i @anthropic-ai/claude-agent-sdk` (with Bun: `bun add @anthropic-ai/claude-agent-sdk`) |
17
- | `codex` | `npm i @openai/codex-sdk` (with Bun: `bun add @openai/codex-sdk`) |
17
+ | `codex` | `npm i @openai/codex-sdk` (0.160 or newer; with Bun: `bun add @openai/codex-sdk`) |
18
18
  | `omp` | none; needs the `omp` binary on your `PATH` and a configured model |
19
19
 
20
20
  Without the SDK, `skaile run` exits 1 with `Claude Agent SDK not installed` (or
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "skaile-cli",
3
- "version": "5.14.0",
3
+ "version": "5.15.1",
4
4
  "description": "Run the Skaile CLI via `npx skaile-cli` — thin wrapper around @skaile/workspaces",
5
5
  "type": "module",
6
6
  "bin": {
@@ -25,7 +25,7 @@
25
25
  "asset-manager"
26
26
  ],
27
27
  "dependencies": {
28
- "@skaile/workspaces": "5.14.0"
28
+ "@skaile/workspaces": "5.15.1"
29
29
  },
30
30
  "publishConfig": {
31
31
  "access": "public"