Browser and Computer Toolsets (1/4) Land in the OpenAI SDKs: BrowserToolset Turns Driver Methods into Function Tools

On 2026-10-14 the two official SDKs landed four stable releases in a single day: openai-python v3.30.0 and v3.31.0, plus openai-node v7.33.0 and v7.34.0 (all four version sections dated 2026-10-14 in the packages' CHANGELOGs, checked by this site on 2026-10-15). The headline is a feature that appears verbatim-identical in both packages — "add browser and computer toolsets (1/4)". As is this site's habit, this article sticks to what the CHANGELOGs and the v3.31.0 tag's source and docs can show; the official docs domains (openai.com / developers.openai.com) remain 403 for this site, so nothing is asserted beyond the SDK layer.

BrowserToolset: function tools, not a new native type

The v3.31.0 tag's docs/browser.md opens by drawing the shape:

BrowserToolset turns a supplied driver's methods into Responses function tools. It does not add a native browser tool type to the Responses API. The model must support function tools.

In other words, the model side sees no new native browser tool type — whatever methods the driver implements become the function tools the toolset exposes. Screenshots travel as native input_image parts inside function_call_output, with an input_text state report alongside.

The browser.py module docstring draws the responsibility boundary:

Drivers own the browser and may implement any subset of the documented members. Only direct URLs are checked here; network isolation belongs to the driver.

Direct URLs are checked at the toolset layer; network isolation belongs entirely to the driver. The constructor signature — BrowserToolset(driver, members=..., additional_members=..., confirm_reads=...) — shows tool exposure is selectable per member, with a read-confirmation switch. Four companion docs shipped with the release: browser.md, browser-forms.md, browser-navigation.md, browser-providers.md.

ComputerToolset: over the computer-tool surface

The computer counterpart is ComputerToolset, with a one-line module docstring: "Run the Responses computer tool with a caller-owned browser or desktop driver." The difference from the browser side is the surface — one wraps actions as ordinary function tools, the other reuses the Responses computer tool, and its drivers can be browsers or desktops.

The official quickstart demonstrates with Playwright (pip install openai playwright==1.63.0 + playwright install chromium, Python 3.10+): a local read-only browser reader example, plus a reservation-form demo called Fieldwork (examples/browser-use-demo).

(1/4): an official annotation

Both packages' CHANGELOGs annotate the feature "(1/4)". As of 2026-10-15 (this site's same-day check of both CHANGELOGs), parts 2-4 are undescribed in content or timing — this article makes no inference beyond noting the annotation exists.

The rest of the day: governance and compliance

openai-python v3.30.0's feature list is almost entirely governance-facing: beta session spending limits (#4058), OCI external-storage provider support (#4060), organization Decisions usage reporting (#4062), image tool error and moderation details (#4072), image URLs and detailed safety alert explanations (#4061), and project API key expiry updates (#4066); plus a streaming fix restoring async HTTP/1.1 connection reuse (#4041).

openai-node v7.33.0, beyond the toolsets, catches up with faces python 3.29.0 (2026-10-11) already had: the billing_not_active session error code (#2911), the shida named Live voice (#2912), vault updates and metadata filters (#2906), and beta pagination limits and non-null parameter alignment (#2915). The two packages' version numbers do not correspond — the same API face lands on different numbers, so align by feature name and PR, not by version.

openai-node v7.34.0 is a single-feature release: "add regional processing residency options" (#2942). As of 2026-10-15 no corresponding python release carries it.

Who benefits

• Agent builders doing browser automation: structured actions over function tools means no hand-rolled tool schemas — write a driver, pick the members; network isolation and browser lifecycle remain yours.
• Teams watching cost governance: session spending limits, project key expiry, and Decisions usage reporting all landed in stable SDKs the same day.
• Organizations with data-residency needs: node 7.34.0's residency options deserve separate evaluation (python has no counterpart yet — cross-language stacks should wait for parity).

Further reading

• For the SDKs' earlier agent-environments line, see Hosted agent environments surface in the OpenAI SDKs: prewarmed creation, idle suspension, expiration.
• For long-conversation context management, see The Responses API Compaction Progress Event: response.compaction.compacting and compaction_trigger.
• Once the official docs domains are reachable again, this site will add an end-to-end hands-on pass on the toolsets (lastTestedAt will be updated then).