Skip to content

feat - LSP data layer + confirmationService skeleton (Auto-approve Part 1 )#132

Open
xinyi-gong wants to merge 2 commits intofeature/auto-approvefrom
tori/auto-approve-task-1
Open

feat - LSP data layer + confirmationService skeleton (Auto-approve Part 1 )#132
xinyi-gong wants to merge 2 commits intofeature/auto-approvefrom
tori/auto-approve-task-1

Conversation

@xinyi-gong
Copy link
Copy Markdown
Member

No description provided.

@xinyi-gong xinyi-gong force-pushed the tori/auto-approve-task-1 branch from 43ee7e3 to 320cec3 Compare April 29, 2026 08:33
@xinyi-gong xinyi-gong marked this pull request as ready for review April 29, 2026 08:34
* Evaluates whether a tool confirmation request can be auto-approved.
* Each implementation handles a specific category of tool (terminal, file operations, MCP, etc.).
*/
public interface ConfirmationHandler {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe move this class to core bundle?

* request should be auto-approved or shown to the user. Currently a no-op skeleton that
* always requires confirmation; concrete logic will be added in subsequent sub-tasks.
*/
public class ConfirmationService {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe move this class to core bundle?

* @param params the confirmation request parameters from CLS
* @return the confirmation result (currently always {@link ConfirmationResult#NEEDS_CONFIRMATION})
*/
public ConfirmationResult evaluate(InvokeClientToolConfirmationParams params) {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How will this class looks like ultimately? (I'm trying to understand why it is a standalone class, not just a utility)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants