fix(core): relax active skill tool restrictions by default#72
Conversation
|
Thanks for this — the design itself is sound. Reframing an active skill's That said, I'd hold off on merging it as-is, for a few reasons: 1. Stale branch + no green CI signal. This PR predates the v4.0.0 release. 2. It overlaps files that changed in v4.0.0. It touches
3. It's a security-relevant default change. Flipping active-skill tool restrictions off by default is a deliberate behavior change (anyone relying on "activate skill ⇒ lock the session to its allowed-tools" loses that default). It should get explicit maintainer sign-off plus a CHANGELOG entry — ideally landing in a 4.1.0 minor, since v4.0.0 just shipped. Suggested path to merge: rebase onto current |
5b41c71 to
8c8a29f
Compare
|
Updated after review. Changes in this update:
Validation run locally:
GitHub currently reports no checks configured for this PR branch. |
Release the active-skill tool-restriction relaxation (#72). Bumps all packages 4.0.0 -> 4.1.0 (core, node/python SDKs, bootstrap, lockfiles) and dates the CHANGELOG entry. Verified by scripts/check_release_versions.sh 4.1.0. Co-authored-by: Claude <claude@anthropic.com>
Summary
allowed-toolsfrom globally denying ordinary session tool calls by default.enforceActiveSkillToolRestrictions/with_active_skill_tool_restrictions(true)as a compatibility switch for legacy behavior.allowed-toolsenforced insideSkillchild execution contexts.allowed-tools: "*"as a skill grant wildcard without bypassing permission policy, hooks, HITL, or AHP.Tests
cargo fmt --all -- --checkrustfmt --edition 2021 --check sdk/node/src/lib.rs sdk/python/src/lib.rsgit diff --checkcargo test -p a3s-code-corecargo test --manifest-path sdk/node/Cargo.tomlcargo test --manifest-path sdk/python/Cargo.toml