| Feature | Feature status | claude | codex | cursor |
|---|---|---|---|---|
future-companion-source-pointers |
planned |
planned |
planned |
planned |
Support vocabulary: Feature Reference
Skillset owns one narrow project-local settings entry: the SessionStart command
npx skillset hooks run session-start. It composes that entry into the verified
Claude .claude/settings.json and Codex .codex/hooks.json destinations;
it never reads or writes user-level settings. Other provider settings remain
provider-native and externally managed.
Authoring
There is no portable settings source and no settings.source feature key. Those
shapes fail config validation. Set compile.session_start_hook to on, off,
or auto to control the single Skillset-owned project entry.
Target Rendering
| Source | Claude output | Codex output | Status | Notes |
|---|---|---|---|---|
| project SessionStart entry | .claude/settings.json |
.codex/hooks.json |
implemented |
Field-level ownership preserves foreign keys and array entries. |
| user runtime settings | n/a | n/a | externally_managed |
Setup and build commands do not write user settings, trust state, marketplaces, or symlinks. |
Diagnostics
- Treat user-level settings mutation as out of scope for
skillset build,check,diff,init, andcreate. - Keep manually suggested PostToolUse and Stop settings separate from the compiled SessionStart entry; neither build nor print installs or trusts runtime hooks.
- If an earlier local build left Skillset’s SessionStart command in
.claude/settings.local.json, remove only that entry before building the committed.claude/settings.jsondestination. Skillset stops rather than run both copies. - After turning the hook off, a source-backed settings island can retain foreign edits already present in the project file. If that authored island later changes too, reconcile the two versions before rebuilding; Skillset will not silently discard the retained edits.
- Do not use settings as an implicit escape hatch for an unsupported destination.
Provenance
The workspace lock records a settings-entry item with the destination file,
stable hooks.SessionStart[*].hooks[*].command address, and command hash. This
entry never authorizes deleting its containing settings file.
Evidence
Host-leak and setup tests verify that repository commands do not mutate user-level provider configuration. See Build Versus Activation and the reviewed settings proposal.