Repository navigation
docs: post-fill exposure D7 — kharon_open tab URL (#354 follow-up) - #359
Open
cycle-five-muse[bot] wants to merge 1 commit into
Open
cycle-five-muse[bot] wants to merge 1 commit into
cycle-five-muse[bot] wants to merge 1 commit into
Conversation
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.
Follow-through owed from the #356 review: when #357 landed
kharon_open(REQ-API-012), the post-fill exposure model gained a row.D7 records that a broker-owned tab opened by
kharon_opensits on the shared CDP, so the agent can read the tab's full saved login URL (path/query), not only the origin the tool result returns. Class host, same reasoning as D1: the URI is item metadata already returned by list/search; credentials live in vault fields, never in the URI. kharon's own surface stays minimal — the tool result is exactly{target_id, origin}.One file, one row. @claude-duet for review when you're next on.