Tools an Agent Might Have: Filesystem, Browser, Code

Agents are only as useful as their tools. Tour the big three — filesystem, browser, code execution — plus the emerging MCP ecosystem, with examples of what each unlocks.

32 min · Reviewed 2026

Tools are superpowers

A language model without tools can only talk. Add a browser and it can research. Add a filesystem and it can build. Add code execution and it can compute. Tools turn 'smart autocomplete' into 'team member who can actually do things.'

The core three

Tool	What it unlocks	2026 reference products
Filesystem	Read, write, move, delete files.	Claude Code, Devin, OpenClaw.
Browser	Open pages, click, fill forms, scrape.	Computer Use, Browser Use, Operator, Atlas.
Code execution	Run scripts in Python, JS, shell.	Code Interpreter (ChatGPT), Claude Analysis tool, sandboxed shells.

Filesystem — the quiet workhorse

Once an agent can read and write files, half of knowledge work becomes automatable: summarize this folder of PDFs, rename these photos by date, collect all invoices from 2025, refactor this codebase. Filesystem is the single tool that unlocks the most 'I wish I didn't have to do this' tasks.

Browser — messy but essential

Browser tools let agents use any web app. No API required. The tradeoff: clicking pixels is slow, brittle, and vulnerable to UI changes. OSWorld scores jumped from under 15% in 2024 to 72.5% by early 2026 after Anthropic's Vercept acquisition improved Claude's vision-based perception. Still, browsers remain the hardest domain to make robust.

Code execution — compute on demand

When an agent needs to do real math, parse a CSV, transform data, or generate a plot, it writes code and runs it. ChatGPT's Code Interpreter, Claude's Analysis tool, and Devin's sandboxed environment all work this way. Much more reliable than asking the model to 'calculate in its head'.

The fourth category: MCP tools

MCP (Model Context Protocol) is the open standard launched by Anthropic and now backed by OpenAI and Google. It lets any AI client connect to any tool server with one protocol. As of April 2026, there are over 1,200 community MCP servers — think of them as apps for your agent.

GitHub MCP — create issues, review PRs, manage branches.
Notion MCP — read and write your workspace.
Supabase / Neon MCP — talk to your database.
Stripe MCP — query payments, create products.
Zapier MCP — reach 8,000+ connected apps.
Slack MCP — read channels, post messages.
Linear, Figma, Google Drive, Calendar — all officially supported.

Next we'll look at where those tools live — on someone else's cloud or on your own machine — and why the difference matters a lot.

End-of-lesson check

8 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-agentic-tools-overview-builders

What is the main idea of "Tools an Agent Might Have: Filesystem, Browser, Code"?
1. Agents are only as useful as their tools.
2. Use AI as the final authority for the whole decision
3. Avoid checking the answer once it sounds polished
4. Focus only on speed instead of judgment
Which concept is most central to "Tools an Agent Might Have: Filesystem, Browser, Code"?
1. filesystem
2. agent tools
3. browser automation
4. code execution
Which use of AI fits this topic best?
1. Let the AI decide what matters without your review
2. Use the answer before checking whether it fits the situation
3. GitHub MCP — create issues, review PRs, manage branches.
4. Use the first answer without checking it
What should a careful learner remember about "Captchas still win"?
1. Use AI to draft or organize ideas about agent tools, then verify before acting.
2. Skip the context so the tool can guess faster
3. Treat the output as private even after sharing it online
4. Use the answer without checking the source
You want to use AI after this lesson. What is the safest next step?
1. Act immediately because the AI answer is written clearly
2. Use the AI answer as a draft, then check it against a reliable source.
3. Hide uncertainty so the final answer looks cleaner
4. Use private or sensitive details before checking permission
How should AI output about agent tools be treated?
1. As proof that no other source is needed
2. As a replacement for context, consent, or expert review
3. As a draft or helper output that still needs human judgment and verification
4. As something that becomes correct when it sounds confident
Name one way to verify an AI answer about agent tools.
Which action would help you apply "Tools an Agent Might Have: Filesystem, Browser, Code" responsibly?
1. Use the tool to avoid thinking through the tradeoff
2. Keep going even if the output conflicts with a trusted source
3. Use the first answer without checking it
4. Notion MCP — read and write your workspace.

← Back to interactive lesson

Tendril · Builders · Agentic AI

Tools an Agent Might Have: Filesystem, Browser, Code

Agents are only as useful as their tools. Tour the big three — filesystem, browser, code execution — plus the emerging MCP ecosystem, with examples of what each unlocks.

32 min · Reviewed 2026

Tools are superpowers

The core three

Tool	What it unlocks	2026 reference products
Filesystem	Read, write, move, delete files.	Claude Code, Devin, OpenClaw.
Browser	Open pages, click, fill forms, scrape.	Computer Use, Browser Use, Operator, Atlas.
Code execution	Run scripts in Python, JS, shell.	Code Interpreter (ChatGPT), Claude Analysis tool, sandboxed shells.

Filesystem — the quiet workhorse

Browser — messy but essential

Code execution — compute on demand

The fourth category: MCP tools

GitHub MCP — create issues, review PRs, manage branches.
Notion MCP — read and write your workspace.
Supabase / Neon MCP — talk to your database.
Stripe MCP — query payments, create products.
Zapier MCP — reach 8,000+ connected apps.
Slack MCP — read channels, post messages.
Linear, Figma, Google Drive, Calendar — all officially supported.

Next we'll look at where those tools live — on someone else's cloud or on your own machine — and why the difference matters a lot.

End-of-lesson check

8 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-agentic-tools-overview-builders

What is the main idea of "Tools an Agent Might Have: Filesystem, Browser, Code"?
1. Agents are only as useful as their tools.
2. Use AI as the final authority for the whole decision
3. Avoid checking the answer once it sounds polished
4. Focus only on speed instead of judgment
Which concept is most central to "Tools an Agent Might Have: Filesystem, Browser, Code"?
1. filesystem
2. agent tools
3. browser automation
4. code execution
Which use of AI fits this topic best?
1. Let the AI decide what matters without your review
2. Use the answer before checking whether it fits the situation
3. GitHub MCP — create issues, review PRs, manage branches.
4. Use the first answer without checking it
What should a careful learner remember about "Captchas still win"?
1. Use AI to draft or organize ideas about agent tools, then verify before acting.
2. Skip the context so the tool can guess faster
3. Treat the output as private even after sharing it online
4. Use the answer without checking the source
You want to use AI after this lesson. What is the safest next step?
1. Act immediately because the AI answer is written clearly
2. Use the AI answer as a draft, then check it against a reliable source.
3. Hide uncertainty so the final answer looks cleaner
4. Use private or sensitive details before checking permission
How should AI output about agent tools be treated?
1. As proof that no other source is needed
2. As a replacement for context, consent, or expert review
3. As a draft or helper output that still needs human judgment and verification
4. As something that becomes correct when it sounds confident
Name one way to verify an AI answer about agent tools.
Which action would help you apply "Tools an Agent Might Have: Filesystem, Browser, Code" responsibly?
1. Use the tool to avoid thinking through the tradeoff
2. Keep going even if the output conflicts with a trusted source
3. Use the first answer without checking it
4. Notion MCP — read and write your workspace.

← Back to interactive lesson