Skip to content

Add optional input data#4

Merged
nchapman merged 2 commits into
developfrom
feature/input-data
Jun 10, 2025
Merged

Add optional input data#4
nchapman merged 2 commits into
developfrom
feature/input-data

Conversation

@nchapman
Copy link
Copy Markdown
Contributor

@nchapman nchapman commented Jun 10, 2025

You can now pass in input data (a js/json object) which gets used in planning and then is available to the agent as it browses. Also updated the README with examples.

@nchapman nchapman force-pushed the feature/input-data branch from b0517d0 to fe3d60b Compare June 10, 2025 23:47
@nchapman nchapman force-pushed the feature/input-data branch from bdd8ff6 to e513d4f Compare June 10, 2025 23:57
@nchapman nchapman merged commit 4065e0a into develop Jun 10, 2025
1 check passed
@nchapman nchapman deleted the feature/input-data branch June 10, 2025 23:58
lmorchard added a commit that referenced this pull request May 16, 2026
The hard rejection from the previous commit (be609b6) caused two task
failures on the 100-task CI eval (Google Map #4 and ESPN #0):
gemini-2.5-flash passes outputSchema:{}, sees the recoverable error,
retries with outputSchema:{} again, and after 5 consecutive errors
the agent layer aborts the whole task.

Soften the guard: when outputSchema is non-null but has no keys,
silently treat it as if it were omitted (fall through to the markdown
branch). An empty {} schema gave no validation anyway — the structured
branch with an empty schema is indistinguishable from the markdown
branch. The fall-through is logged via an AGENT_STATUS event so the
downgrade is visible in traces.

Updated the outputSchema prompt copy: "an empty {} provides no
validation and is silently downgraded to a markdown extract" instead
of "will be REJECTED with a recoverable error".

Test: updated to assert the markdown branch IS called and the status
event IS emitted when outputSchema:{} is passed. Previously asserted
the recoverable-error shape; that behavior is gone.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant