remove unnecssary value param from fillform tool in dom mode
why
The fillForm tool (DOM mode) had a value field in its input schema that the LLM would populate, but it was never actually used during execution. The execute function only read f.action to build the observe instruction — the value was completely ignored. This meant the tool relied entirely on the action string (e.g. "type foo into the email field") to carry both the target and the value, while value was dead weight.
This was also a problem for the variables feature: the schema told the LLM to use %variableName% syntax in the value field, but since value was never consumed, variable substitution through it could never work.
what changed
fillform.ts: Removed thevaluefield from the input schema. Theactionfield now explicitly guides the LLM to include the value to type within the action description (e.g."type foo@bar.com into the email field"). When variables are available, the description shows%variableName%syntax with an example. This aligns the schema with how the tool actually works —observeparses the action string and returnsActionobjects with the correctmethod,selector, andarguments, whichactthen executes.agentSystemPrompt.ts: Removed the stale reference tovaluein the variable usage instructions for DOM mode ("value/action fields"→"action fields").cache.ts: UpdatedAgentReplayFillFormStep.fieldstype to dropvalue.- Tests: Removed
valuefrom test fixtures intimeouts.spec.tsandagent-execution-model.test.ts.
test plan
- Run unit tests:
agent-execution-model.test.tspasses with the updated fillForm field shape - Run integration tests:
timeouts.spec.tsfillForm timeout test passes - Run agent eval with a form-filling task (e.g.
sign_in) to verify the LLM correctly embeds values in the action string and fields get filled as expected - Test with variables: confirm
%variableName%in the action string gets substituted correctly (e.g."type %password% into the password field")
Summary by cubic
Removed the unused value field from the DOM-mode fillForm tool and moved values into the action string to match actual execution. Updated variable guidance, types, and tests to simplify form filling and fix variable substitution.
- Migration
- Update
fillForminputs to only useaction, e.g.{ fields: [{ action: "type hello into name" }] }. - Use
%variableName%inside theactionstring, e.g.type %password% into the password field. - If you reference replay types,
AgentReplayFillFormStep.fieldsnow only includes{ action: string }.
- Update