Skip to content

Automate browser based workflows with AI

remove terminate in cua fallback (#2195)

Shuchang Zhengb56ac3f3bda7
diff --git a/skyvern/forge/prompts/skyvern/cua-fallback-action.j2 b/skyvern/forge/prompts/skyvern/cua-fallback-action.j2
index f635c2cd7..47d35f976 100644
--- a/skyvern/forge/prompts/skyvern/cua-fallback-action.j2
+++ b/skyvern/forge/prompts/skyvern/cua-fallback-action.j2
@@ -6,12 +6,11 @@ Help the user decide what to do next based on the assistant's message. Here's th
- solve_captcha: the task is blocked by captcha and the assistant is asking the user to solve the captcha
- complete: the user goal has been achieved
- get_verification_code: the assistant is asking the user to provide a verification code (2FA, MFA or TOTP code). At this point, the code should have been sent to the user. If code hasn't been sent, do not return get_verification_code action.
-- terminate: the user goal cannot be achieved. Terminate the task. Examples: 1) there's not enough data provided to achieve the goal and the assistant is asking the user to provide more information. For examples: login is required and the user has not provided the login credentials or incorrect credentials are provided; a form needs to be filled and a required field is missing. 2) The site is stuck or not loading after multiple attempts. Do not terminate if receiving verification code is an option which has not been sent.
- other: the assistant is asking the user to do something else
Return the action to take next in the following JSON format:
{
- "action": str // complete, terminate, solve_captcha, get_verification_code, other
+ "action": str // complete, solve_captcha, get_verification_code, other
"useful_information": str // If there is any useful information the assistant has provided that contributes to the user goal, put it here.
}