| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Ensure session-level permission rules are merged before tool exposure so denied tools are not advertised to providers. Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-opencode) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
Align tool and tool/ids endpoints with runtime visibility rules so API consumers receive only tools they can invoke. Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-opencode) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
Expose provider/model/agent/sessionID query fields in generated SDK contracts so clients can request permission-aware tool listings. Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-opencode) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
Replace raw declaration path placeholders with valid triple-slash references so workspace typecheck and pre-push hooks pass on Windows. Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-opencode) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
|
Hey! Your PR title Align tool visibility with session permissions and update SDK query types doesn't follow conventional commit format. Please update it to start with one of:
Where scope is the package name (e.g., app, desktop, opencode). See CONTRIBUTING.md for details. |
Sorry, something went wrong.
|
The following comment was made by an LLM, it may be inaccurate: Based on my searches, I found one potentially related PR: Related PR:
However, the search results indicate that #7725 appears to be a separate feature focused on configuration-level tool management (subagent_tools), while your PR (#17089) focuses on runtime permission filtering at the session level for the experimental tool endpoints. The other results (#15028, #8943, #7756, #12731) don't appear to be directly related to the core functionality of this PR. No exact duplicates found for PR #17089. |
Sorry, something went wrong.
|
Thanks for your contribution! This PR doesn't have a linked issue. All PRs must reference an existing issue. Please:
See CONTRIBUTING.md for details. |
Sorry, something went wrong.
|
Thanks for updating your PR! It now meets our contributing guidelines. 👍 |
Sorry, something went wrong.
|
Follow-up on CI status:
I attempted to trigger a failed-job rerun via API, but this token does not have permission to rerun upstream Actions jobs (403). |
Sorry, something went wrong.
|
Maintainer context for merge decision:
If maintainers are comfortable with the current E2E flake baseline, this PR appears otherwise ready from a code/policy perspective. |
Sorry, something went wrong.
|
Thanks! is what I need! |
Sorry, something went wrong.
|
Any update on this PR? I would need this |
Sorry, something went wrong.
|
I need this too |
Sorry, something went wrong.
|
Same here! It would be very helpful for me |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Issue for this PR
Closes #17090
Type of change
What does this PR do?
This patch aligns tool visibility with permission enforcement so the model and API only see tools that are actually callable.
Concretely:
How did you verify your code works?
Screenshots / recordings
Not a UI change.
Checklist