Skip to content

Automate browser based workflows with AI

SKY-10140 Name Copilot parameters by domain intent (#6104)

Andrew Neilson6e2f56e47fd7
diff --git a/skyvern/forge/sdk/copilot/tools.py b/skyvern/forge/sdk/copilot/tools.py
index a2b1b4611..0386c5550 100644
--- a/skyvern/forge/sdk/copilot/tools.py
+++ b/skyvern/forge/sdk/copilot/tools.py
@@ -4036,6 +4036,11 @@ async def update_workflow_tool(
Provide the complete workflow YAML as a string.
Returns the validated workflow or validation errors.
+ Top-level workflow parameter keys appear in the run-input UI. When you
+ add runtime inputs in `workflow_definition.parameters`, name keys for the
+ reusable domain value the user supplies, not the page widget or action used
+ to enter it.
+
If a `goto_url` URL encodes dynamic page state, do not wire it
directly to extraction. Add a `code`, `validation`, or `navigation` block
first that verifies the live page state from active chips, checked controls,
@@ -4258,6 +4263,11 @@ async def update_and_run_blocks_tool(
Use this instead of calling update_workflow and run_blocks_and_collect_debug separately.
The workflow must validate successfully before blocks are run.
+ Top-level workflow parameter keys appear in the run-input UI. When you
+ add runtime inputs in `workflow_definition.parameters`, name keys for the
+ reusable domain value the user supplies, not the page widget or action used
+ to enter it.
+
For diagnostic complaints, follow the system prompt's ASK-vs-EDIT routing.
A complaint with no prior edit goal needs context inspection or
clarification first. A diagnostic follow-up after an explicit edit goal may