# Available Tools

OpenHuman's agent doesn't ship empty. Every model behind the agent has a curated set of tools available the moment you install - no plugin marketplace, no API keys to wire up, no MCP servers to register. The whole toolbelt is in the box.

This page is the index. Each subpage covers one family of tools.

## Why ship them natively

A plugin-only model means tools live in different processes, behind RPC, with their own auth and packaging stories. That's fine for open-ended extensibility, but for the **core** tools every agent needs (read a file, search the web, edit code, set a reminder, join a meeting), shipping them in-process means:

* Consistent error handling.
* Zero install friction.
* All output passes through [Smart Token Compression](/openhuman/features/token-compression.md) for free.
* Predictable security boundary - filesystem tools respect workspace scoping, network tools go through the OpenHuman proxy.

## The toolbelt

| Family                                                                                 | What it covers                                                                                         |
| -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| [Web Search](/openhuman/features/native-tools/web-search.md)                           | Search the live web without bringing your own API key.                                                 |
| [Web Scraper](/openhuman/features/native-tools/web-scraper.md)                         | Pull clean text out of any URL - articles, docs, READMEs.                                              |
| [Coder](/openhuman/features/native-tools/coder.md)                                     | Read/write/edit/patch files, glob, grep, git, lint, test.                                              |
| [Browser & Computer Control](/openhuman/features/native-tools/browser-and-computer.md) | Open URLs, screenshot, click, type, move the mouse.                                                    |
| [Cron & Scheduling](/openhuman/features/native-tools/cron.md)                          | Recurring jobs, one-off reminders, scheduled agent runs.                                               |
| [Voice](/openhuman/features/native-tools/voice.md)                                     | Speech-to-text in, text-to-speech out, live Google Meet agent.                                         |
| [Memory Tools](/openhuman/features/native-tools/memory-tools.md)                       | Recall, store, forget, and search the [Memory Tree](/openhuman/features/obsidian-wiki/memory-tree.md). |
| [Third-party Integrations](/openhuman/features/integrations.md)                        | The agent's view of the [118+ connected services](/openhuman/features/integrations.md).                |
| [Agent Coordination](/openhuman/features/native-tools/agent-coordination.md)           | Spawn subagents, delegate to skills, plan, ask the user.                                               |
| [System & Utilities](/openhuman/features/native-tools/system-and-utilities.md)         | Shell, node, SQL, current time, push notifications, LSP.                                               |

## See also

* [Smart Token Compression](/openhuman/features/token-compression.md) - what keeps tool output costs bounded.
* [Third-party Integrations](/openhuman/features/integrations.md) - the user-facing pitch and OAuth flow for the 118+ catalog.
* [Privacy & Security](/openhuman/features/privacy-and-security.md) - the boundary every tool runs inside.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://tinyhumans.gitbook.io/openhuman/features/native-tools.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.