Repository navigation
fix: correct the skill on schema changes, re-signing in and search - #11
Merged
Merged
Conversation
The skill sent users to the consent page for schema tools that are never offered, and a plain reconnect keeps the old grant. Compat search skips some field types, so an empty result isn't proof.
bram2w
approved these changes
Oct 25, 2026
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
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.
enabled = Falseand never appear on the consent page, so telling the user to tick them sent them in a loop.compatsearch mode,search_all_fieldsskips link-to-table and boolean fields (per its docstring), plus collaborator and duration fields per the review. When a search on those finds nothing, the agent now pages and compares instead of saying the row doesn't exist.