skill: document the change feed - #12
Merged
Merged
Conversation
Agents reading the skill would not otherwise know /changes exists, so a refreshed list_changes tool arrives with no explanation of what it is for. Records the two things that bite in practice: the cursor is opaque and bound to the scope that produced it, so it must not be constructed by hand or carried across a workspace or kind filter; and the MCP tool list is fixed at session connect, so a session older than the feature will not see list_changes until it reconnects.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The tracker skill is what agents read to learn how to use tracker. It did not mention the change feed shipped in v1.5.0, so a refreshed
list_changestool would arrive with no explanation.Adds a
## The change feedsection covering both the MCP tool and the HTTP/SSE endpoints, and the two things that actually bite:kindfilter returns 400 rather than silently skipping eventslist_changesuntil it reconnects; the HTTP endpoints work regardless and are the better choice for a long-running watcherDocs only.