https://github.com/GautamTalksDev/keyring/pull/new/fix/agent-registration-honesty - #6
Merged
Merged
Conversation
Abort prior card requests and require responses to match the active scan so old cards and terminal status cannot overwrite a new scan or its headline. Co-authored-by: Cursor <cursoragent@cursor.com>
Use a monotonic scan-start token to prevent late start responses from replacing the active scan or installing stale SSE subscriptions, keeping queue updates tied to the latest invocation. Co-authored-by: Cursor <cursoragent@cursor.com>
Use the raw TrueForge REST field names, select an available agent model, and make local Docker MCP endpoints reachable. Add streaming support and reconciliation handling to keep the stub harness compatible with TrueForge. Co-authored-by: Cursor <cursoragent@cursor.com>
PR Summary by QodoHarden TrueForge registration and prevent stale scan UI updates
AI Description
Diagram
High-Level Assessment
Files changed (5)
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can enable the Remediation agent and Qodo fixes findings in a dedicated fix PR |
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.
Running the live TrueForge path surfaced four defects, all fixed here.
bodies on non-2xx, verifies the agent via GET /api/v1/agents, and exits non-zero.
(base_url, auth.api_key, models[].model_id), so no provider ever registered and
the agent 422'd with "provider not configured". The TrueForge driver now works
end to end: 15 grants, 4 clusters, 1 unknown, 7 cards.
201 creates an invitation; access doesn't exist until accepted. Pending invitations
are now distinct and revoked via DELETE /invitations/{id}.
registration steps.