Repository navigation
Closed
Labels
bugSomething isn't workingSomething isn't workinghelp wantedExtra attention is neededExtra attention is needed
Description
What changed upstream
browser-use 1.0 rebuilt its agent on Pydantic AI, so the method Tracekit's Browser Use integration replaces to gate each action, Tools.registry.execute_action (tracekit/integrations/browser_use.py, _wrap, L77-84), no longer exists, and nothing replaces it one for one. At the 1.0.0 tag:
Tools.registryreturns theToolsitself (browser_use/tools.pyL164-166), and any other old method raisesAttributeError(L168-171).actandcreate_action_modelare gone.- Custom actions are Pydantic AI tools in
Tools.functions(tools.pyL162), passed to the agent's Pydantic AI agent (browser_use/agent/service.pyL398). - The model drives the browser through a
pythontool that runs code in a persistent REPL (browser_use/agent/loop.pyL159). - Every tool call runs through
BrowserLoop.wrap_tool_execute(loop.pyL478), a Pydantic AI capability (class BrowserLoop, L402). - 1.0 needs Python 3.11+ and pins
pydantic-ai-slim==2.66.0. 1.0.2 is out.
The nightly contract run against @latest fails on it (run 42817996539, tracked in #688).
What that means for a Tracekit user on 1.0
tracekit.instrument()still replacesTools.__init__(tracekit/autowire.py,_browser_use, L305-317), and only warns that 1.0 is untested (L452-453).- An agent that passes its own
Tools()stops there with anAttributeErrorfrom_wrap. - An agent that passes none (1.0's
Agenttakestools=Noneby default,service.pyL235 and L288) runs, and the Browser Use wiring gates none of its browser work: neither thepythoncells nor any action. instrument()also wires Tracekit's Pydantic AI capability on the same install (pydantic-ai-slim 2.66, outside its tested range). Whether that reaches browser-use's internal agent and itspythoncells is untested.
What's needed
- Find the 1.0 seam that sees every tool call before it runs, with its name and arguments (
wrap_tool_execute, or adding Tracekit's Pydantic AI capability to the agent browser-use builds), and say in the PR which you chose and why. - Decide each call through
_Actions.gateas today. Read apythoncell as code the agent runs (decide its source, at least as the shell rules read a script), and each custom action as itself. Keep 0.13.x working: pick by what the installed version has, not by its version string. - Until 1.0 is gated,
instrument()must say so: when the 0.13 seam isn't there, wiring fails with a message naming the supported versions, soinstrument()prints "not wired" rather than "wired but untested".
Acceptance
- Contract tests that run against browser-use 1.0.x (Python 3.11+) and 0.13.x: a custom action and a
pythoncell are each decided before they run, and a denied one doesn't run.OnRealToolsintests/test_contract_browser_use.pyusestools.actandcreate_action_model, which 1.0 removed, so 1.0 needs its own test. - The tested range in
FRAMEWORKS(tracekit/autowire.pyL352-353) anddocs/integrations/browser-use.mdname 1.0, anddocs/limits.mdsays what apythoncell's decision can and can't read. - Run a Browser Use 1.0 agent with
tracekit.instrument()and paste thetracekit lastsummary (not the run's content) in the PR.
Comment here to claim it. Commits need a DCO sign-off (git commit -s).
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workinghelp wantedExtra attention is neededExtra attention is needed
Activity
Koloyaaa commentedon Nov 11, 2026
Claiming this one. I'll start by reproducing the 1.0 behaviour with a minimal Browser Use agent, then check
BrowserLoop.wrap_tool_executeand the Pydantic AI capability path to decide which seam sees every tool call before it runs. I'll keep 0.13.x working, add contract coverage for both versions, and makeinstrument()say "not wired" when the 0.13 seam is gone. I'll comment here if the acceptance criteria need clarification.LoopGlitch26 commentedon Nov 11, 2026
It's yours, @Koloyaaa. The plan fits. Two notes: the
pythoncell is the part that does the browser work, so its decision is the one that matters most; say in the PR what that decision can read of a cell (its source only, or the calls it makes). And make the "not wired" message the first commit, so a 1.0 user is told the truth even before the new seam lands.Browser Use 1.0: decide the delivery and both Repl.call ops (Cygnux-L…
Browser Use 1.0: keep the fallback when the 1.0 wiring fails (Cygnux-…
Browser Use 1.0: gate every function tool at BrowserLoop.wrap_tool_ex…