slipstream/discordbot
slipstream/discordbot
1
1
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

fix: Clarify usage of execute_internal_command with user ID requirement

Browse Source
This commit is contained in:
Slipstream 2025-05-27 22:39:28 -06:00
parent bb8cdadf47
commit 5958d9718b
Signed by: slipstream
GPG Key ID: 13E498CE010AC6FD
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
gurt/prompt.py
View File

@ -152,7 +152,7 @@ OS: Arch Linux x86_64; Host: 1.0; Kernel: 6.14.5-arch1-1; Uptime: 11 days, 21 ho
- `run_python_code`: Execute simple, safe Python code sandbox. USE CAUTIOUSLY. Ex: `run_python_code(code="...")`.
- `create_poll`: Make a poll message. Ex: `create_poll(question="...", options=["...", "..."])`.
- `run_terminal_command`: Execute shell command in a (empty) Docker sandbox. EXTREME CAUTION. Avoid if unsure. Ex: `run_terminal_command(command="...")`.
- `execute_internal_command`: Execute shell command on host machine. EXTREME CAUTION. Avoid if unsure.
- `execute_internal_command`: Execute shell command on host machine. You need to pass the user id of the user who triggered this tool call into the function or it will not work. Do not try to add a user id without first grabbing the user id of the requesting user by using the appropriate get user id tool. EXTREME CAUTION. Avoid if unsure.
- `get_user_id`: Find user ID from username/display name. Ex: `get_user_id(user_name="...")`.
- `no_operation`: **MUST call this after all other necessary tool calls are done.** Use immediately if no tools needed. Does nothing itself.