apunkt/SurfSense
1
0
Fork 0
mirror of https://github.com/MODSetter/SurfSense.git synced 2026-04-30 19:36:25 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

feat: enforce single invocation for tool actions across various services

Browse source 
- Added a guideline to ensure that each tool (Gmail, Google Calendar, Google Drive, Linear, Notion) is called only once per user request.
- Updated documentation to clarify that the system will automatically select the most relevant match when multiple items share the same title or subject, enhancing user experience and preventing redundant calls.
This commit is contained in:
Anish Sarkar 2026-03-21 03:07:13 +05:30
parent 0d47233580
commit 744ad1fa79
14 changed files with 49 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

4
surfsense_backend/app/agents/new_chat/tools/linear/delete_issue.py
View file

@ -64,6 +64,10 @@ def create_delete_linear_issue_tool(
- If status is "not_found", inform the user conversationally using the exact message
provided. Do NOT treat this as an error. Simply relay the message and ask the user
to verify the issue title or identifier, or check if it has been indexed.
- ONLY call this tool ONCE per user request. The system automatically picks the
most relevant match when multiple issues share the same title. The user will
see the exact issue details in the approval card and can reject if it is not
the right one. Do NOT call this tool multiple times for the same issue reference.
Examples:
- "Delete the 'Fix login bug' Linear issue"

4
surfsense_backend/app/agents/new_chat/tools/linear/update_issue.py
View file

@ -78,6 +78,10 @@ def create_update_linear_issue_tool(
- If status is "not_found", inform the user conversationally using the exact message
provided. Do NOT treat this as an error. Simply relay the message and ask the user
to verify the issue title or identifier, or check if it has been indexed.
- ONLY call this tool ONCE per user request. The system automatically picks the
most relevant match when multiple issues share the same title. The user will
see the exact issue details in the approval card and can reject if it is not
the right one. Do NOT call this tool multiple times for the same issue reference.
Examples:
- "Mark the 'Fix login bug' issue as done"