dreampiler/kandev
1
0
Fork 0
Code Issues 43 Pull Requests Actions 6 Packages Projects Releases Wiki Activity

fix: isolate managed npm config and report policy failures (#3902) (#3907)

Browse Source
This commit is contained in:
Carlos Florêncio
2026-09-24 19:08:13 +01:00
committed by GitHub
parent 8796d6948f
commit 200af92fbe
59 changed files with 2116 additions and 125 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/public/agents-and-profiles.md
+12 -4
View File
@@ -38,8 +38,8 @@ Muse Code has no native ACP server, so Kandev runs it through the community
[`@bex-co/muse-code-acp`](https://github.com/bex-co/muse-code-acp) adapter,
which is not affiliated with Meta:
- Structured ACP sessions and one-shot inference use
`npx --yes --prefer-offline @bex-co/muse-code-acp@<effective-version>`, which
- Structured ACP sessions and one-shot inference use the managed
`@bex-co/muse-code-acp` package at the selected effective version. This
needs Node.js 22 or later.
- The adapter drives the native `muse` executable through `muse serve`; CLI
Passthrough starts `muse` directly.
@@ -67,8 +67,8 @@ pin one model for both, set it there, for example
Pi uses separate executables for its two Kandev modes:
- Structured ACP sessions and one-shot inference use
`npx --yes --prefer-offline pi-acp@<effective-version>`.
- Structured ACP sessions and one-shot inference use the managed `pi-acp`
package at the selected effective version.
- CLI Passthrough starts the globally installed `pi` executable.
- The Pi install action runs `npm install -g --ignore-scripts @earendil-works/pi-coding-agent`.
@@ -177,6 +177,14 @@ silently select another version. When the retry succeeds, no recovery card is
shown. When it fails again, Kandev and Office show one **Retry runtime** action
with collapsed technical details.
Managed `npx` runtimes use a Kandev-owned npm project directory, so an `.npmrc`
in the task repository does not change the managed runtime's package lookup.
The task repository remains the command's working directory. User and global npm
settings still apply, including `min-release-age` and `before` policies. If an
age policy blocks the selected version, Kandev does not repair the npm cache or
repeat the lookup online. Wait until the version meets the policy, or select an
older trusted version, then choose **Retry runtime**.
Do not use `npm cache clean --force` as the normal recovery step. It removes
unrelated npm data and does not target the stale execution tree. If the
specialized retry cannot resolve the runtime, check that the Kandev service