tool-combinations changedagents-and-tools/tool-use/tool-combinations
Nearest release: v2.1.238, published an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+18added
Lines−11removed
From line
53
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits3to this page, all time
## Long-running agent: memory + any other tools ## Browser agent: browser\_use ## Long-running agent: memory + any toolset
The whole hunk
from line 53, old and new numbered
/
from line 53
5353
5454This pairing is useful when the answer lives in long-form content (documentation pages, articles, specifications) that a search snippet can't fully capture. Fetch pulls the complete page so Claude can cite specific passages.
5555
56## Long-running agent: memory + any toolset
56## Long-running agent: memory + any other tools
5757
5858Memory persists state across conversations; the other tools do the work. Add memory to any agent that needs to remember prior sessions, such as a support agent that recalls a customer's earlier issues or a project assistant that tracks decisions made last week.
5959
from line 65
6565
6666Add your other tools alongside `memory` in the same array.
6767
68Memory is orthogonal to the rest of your toolset. It doesn't change how other tools behave; it gives Claude a place to write down and later retrieve facts that would otherwise be lost when the context window resets. See [Memory tool](https://platform.claude.com/docs/en/agents-and-tools/tool-use/memory-tool) for the storage model.
68Memory is orthogonal to your other tools. It doesn't change how they behave; it gives Claude a place to write down and later retrieve facts that would otherwise be lost when the context window resets. See [Memory tool](https://platform.claude.com/docs/en/agents-and-tools/tool-use/memory-tool) for the storage model.
6969
7070## All-in-one: computer\_use
7171
from line 73
7373
7474```json
7575{
76 "tools": [
77 {
78 "type": "computer_20250124",
79 "name": "computer",
80 "display_width_px": 1280,
81 "display_height_px": 800
82 }
83 ]
76 "tools": [{ "type": "computer_toolset_20260801" }]
8477}
8578```
8679
87Computer use is the most general option and also the slowest, because every action requires a screenshot roundtrip. Prefer narrower tools when they cover your use case, and reach for computer use when nothing else fits. See [Computer use tool](https://platform.claude.com/docs/en/agents-and-tools/tool-use/computer-use-tool) for the sandbox setup.
80The toolset entry takes no `name` or display dimensions: coordinates are expressed in the pixel space of the screenshots you return, and you can turn individual actions off through the entry's `configs` field.
81
82Computer use is the most general option and also the slowest, because Claude typically needs a fresh screenshot after each batch of actions. Prefer narrower tools when they cover your use case, and reach for computer use when nothing else fits. If the task stays inside a web browser, use the browser agent pattern in the next section. See [Computer use tool](https://platform.claude.com/docs/en/agents-and-tools/tool-use/computer-use-tool) for the sandbox setup.
83
84## Browser agent: browser\_use
85
86When the whole task happens inside webpages (filling forms, reading page content, working across tabs), the browser use tool is a closer fit than computer use. Your application drives a browser it controls and returns screenshots or page state; Claude calls page-aware member tools such as `read_page`, `find`, `form_input`, and `get_page_text` alongside clicks and typing, so it can act on element references in addition to pixel coordinates.
87
88```json
89{
90 "tools": [{ "type": "browser_toolset_20260801" }]
91}
92```
93
94Like the computer use toolset, the entry takes no `name`, and you turn individual member tools off through its `configs` field. See [Browser use tool](https://platform.claude.com/docs/en/agents-and-tools/tool-use/browser-use-tool) for the execution contract.
8895
8996## Next steps
9097
No line in this hunk matches that.