Skip to content

feat(app-server): add a skills/changed v2 notification#13414

Merged
owenlin0 merged 1 commit intomainfrom
owen/skills_change_v2_notification
Mar 4, 2026
Merged

feat(app-server): add a skills/changed v2 notification#13414
owenlin0 merged 1 commit intomainfrom
owen/skills_change_v2_notification

Conversation

@owenlin0
Copy link
Collaborator

@owenlin0 owenlin0 commented Mar 4, 2026

This adds a first-class app-server v2 skills/changed notification for the existing skills live-reload signal.

Before this change, clients only had the legacy raw codex/event/skills_update_available event. With this PR, v2 clients can listen for a typed JSON-RPC notification instead of depending on the legacy codex/event/* stream, which we want to remove soon.

@owenlin0 owenlin0 force-pushed the owen/skills_change_v2_notification branch from e9d0354 to 450501d Compare March 4, 2026 00:33
@owenlin0 owenlin0 force-pushed the owen/skills_change_v2_notification branch from 450501d to 5e1e83c Compare March 4, 2026 00:36
@owenlin0 owenlin0 marked this pull request as ready for review March 4, 2026 00:39
@owenlin0
Copy link
Collaborator Author

owenlin0 commented Mar 4, 2026

@codex review

"properties": {
"method": {
"enum": [
"skills/changed"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why changed vs updated?

Copy link
Collaborator Author

@owenlin0 owenlin0 Mar 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had updated in mind as well but codex pushed me away with this justification:

skills/changed is a better fit for what this notification actually means.

updated implies the server is telling the client “here is the new authoritative state” or at least “the resource has been refreshed.” That’s not what we have here. This notification is just an invalidation signal coming from the watcher: something on disk changed, and the client should re-run skills/list if it cares.

changed is weaker and more accurate:

  • it doesn’t imply the server is pushing the updated skill list
  • it matches the underlying watcher concept (SkillsChanged)
  • it leaves room for changes that are additive, deletions, edits, enable/disable effects, or anything else that should cause a refresh

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if you feel strongly happy to update! i'm ok either way I think

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

don't feel strongly

@chatgpt-codex-connector
Copy link
Contributor

Codex Review: Didn't find any major issues. Bravo.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@owenlin0 owenlin0 merged commit 0fbd840 into main Mar 4, 2026
29 of 31 checks passed
@owenlin0 owenlin0 deleted the owen/skills_change_v2_notification branch March 4, 2026 01:01
@github-actions github-actions bot locked and limited conversation to collaborators Mar 4, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants