lshed 0.12.0 → 0.14.0
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.
- package/CHANGELOG.md +23 -0
- package/README.md +273 -128
- package/dist/cli.js +158 -158
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,28 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.14.0 — 2026-09-05
|
|
4
|
+
|
|
5
|
+
`--agent codex` now puts skills in `~/.agents/skills/`, the location Codex documents, instead of `~/.codex/skills/`.
|
|
6
|
+
|
|
7
|
+
- Codex 0.153 still reads `$CODEX_HOME/skills`, but its source marks that directory deprecated and the docs name only `.agents/skills`. `AGENTS.md` and `config.toml` stay under `~/.codex` (or `$CODEX_HOME`). The managed set records the skills as `../.agents/skills/<id>` relative to the Codex root; switching profiles removes them there, and backups stay inside `~/.codex/lshed/backups/`.
|
|
8
|
+
- `--root <dir>` keeps the same shape with the directory's parent as the home, so a scratch root never writes into your real `~/.agents`.
|
|
9
|
+
- Since the `agents` target places into the same directory, use one of `--agent codex` and `--agent agents` per machine for skills, not both.
|
|
10
|
+
- Shed paths are now derived from the category name, never from where the agent keeps that category locally.
|
|
11
|
+
|
|
12
|
+
## 0.13.0 — 2026-09-05
|
|
13
|
+
|
|
14
|
+
`--agent agy` places into Google Antigravity (the `agy` CLI and the IDE).
|
|
15
|
+
|
|
16
|
+
- Skills go to `~/.gemini/config/skills/`, the one global location both the Antigravity IDE and CLI read. Instructions are concatenated into `~/.gemini/AGENTS.md`, one level above that root: agy reads both `AGENTS.md` and `GEMINI.md` there, and Gemini CLI also owns `GEMINI.md`, so lshed leaves that one alone. MCP servers go to `~/.gemini/config/mcp_config.json` in agy's shape (no `type`, `serverUrl` for http); `${VAR}` is filled by `restore`.
|
|
17
|
+
- A part above the root (`../AGENTS.md`) is backed up under `lshed/backups/<stamp>/__/` so backups never escape the backup directory.
|
|
18
|
+
- Verified on this machine with agy 1.1.26 through the VM probe (`scripts/vm/probe.sh agy`): skill, rules file, MCP list, and a linked skill all read. agy does not read `~/.agents/skills`, so it is not part of the `agents` target.
|
|
19
|
+
|
|
20
|
+
## 0.12.1 — 2026-09-05
|
|
21
|
+
|
|
22
|
+
- Fix: with `CLAUDE_CONFIG_DIR` set on a machine where Claude Code has not run yet, `restore` wrote MCP servers to `<dir>.json` next to the config dir instead of `<dir>/.claude.json` inside it, where Claude Code actually reads them. Found by the VM probe below. Without `CLAUDE_CONFIG_DIR` nothing changes.
|
|
23
|
+
|
|
24
|
+
VM probe for the other agents (`scripts/vm/`): `install-tools.sh` bakes an image with Codex, Gemini CLI, Copilot CLI, Cursor CLI and lshed; `cloud-init.yaml` injects API keys at boot and runs `probe.sh`, which restores a throwaway shed into each tool's real root and asks the tool, non-interactively, for a passphrase kept in a skill, a codeword kept in the instructions file, and the same skill again after `--link`. Where a tool can parse its own config without a model (`codex mcp list`, `gemini mcp list`, `codex debug prompt-input`) that is checked too. Run on this machine against Codex 0.153.2: Codex reads `$CODEX_HOME/skills` (deprecated in its source; the docs now name only `~/.agents/skills`), `$CODEX_HOME/AGENTS.md`, the `[mcp_servers.*]` table lshed writes, and a linked skill.
|
|
25
|
+
|
|
3
26
|
## 0.12.0 — 2026-09-04
|
|
4
27
|
|
|
5
28
|
MCP servers follow the shed into the other agents.
|