The fastest, cheapest, most efficient open-source agent harness. Run more than 500 agents on a $10 VPS.
tools/impl
Built-in implementations of the cross-cutting tool families that tools/ops.rs
assembles into the agent registry. Ownership rule from AGENTS.md: only
cross-cutting capabilities (filesystem, browser, generic process/system, generic
here. Domain-owned tools (memory, cron, wallet, composio, integrations, voice,
agent sub-dispatch, ...) live in their own domain's tools.rs and are only
re-exported through tools/mod.rs. Do not add a family under impl/ for a
domain capability.
tools/mod.rs mounts this directory as #[path = "impl/mod.rs"] pub(crate) mod implementations (impl is a keyword) and glob re-exports it, so tool structs
are imported as crate::tools::*. impl/mod.rs gates document/ and
presentation/ behind the documents Cargo feature; the other five families
See ../README.md for the registry, policy, and RPC layer this
feeds, and ../../security/README.md for the
SecurityPolicy threaded through nearly every tool here (path validation,
trusted roots, egress gating).
Families
The gates below are what tools/ops.rs::all_tools_with_runtime checks before
registering a tool. "Exported, not registered" means the struct is public and
tested but no production assembly site constructs it today.
| Family | Tools | Registration gate |
|---|---|---|
system/ |
ShellTool, InstallToolTool, DetectToolsTool, CurrentTimeTool, ResolveTimeTool, ProxyConfigTool, PushoverTool, workspace and retrieval helpers. |
|
filesystem/ |
Host adapter only: SecurityPolicy implements tinyagents_harness_tools::fs::filesystem::FsGate. The tools (FileReadTool, FileWriteTool, EditFileTool, ApplyPatchTool, GrepTool, GlobTool, ListFilesTool, ReadDiffTool, CsvExportTool, GitOperationsTool, RunLinterTool, RunTestsTool, UpdateMemoryMdTool) live in tinyagents_harness_tools::fs::filesystem and are imported directly by tools/ops.rs |
always registered, except ReadDiffTool, RunLinterTool, and RunTestsTool, which are exported, not registered |
browser/ |
BrowserTool (TinyComputer browser members and tasks), BrowserOpenTool (simple TinyComputer navigation), ImageInfoTool |
Both browser tools need browser.enabled and the modules feature, and are deferred until tool_search; ImageInfoTool remains direct. Browser navigation uses the shared http_request.allowed_domains policy, and the checksum-pinned TinyComputer release module. Consequential actions go through the forced approval gate; browser_unattended.rs lets trusted cron/background/approval-free workflow turns skip it for the kinds listed in [browser] unattended_actions. |
network/ |
HttpRequestTool, WebFetchTool, CurlTool, GitbooksSearchTool, GitbooksGetPageTool, and under the mcp Cargo feature McpListServersTool, McpListToolsTool, McpCallTool; url_guard.rs is the shared SSRF/allowlist validator, not a tool |
http_request, web_fetch, curl always registered; gitbooks_* need gitbooks.enabled and, when the active profile sets an mcp_allowlist, an entry named gitbooks; mcp_list_servers/mcp_list_tools/mcp_call_tool register only when the static [[mcp_client.servers]] registry (after the profile allowlist) is non-empty |
document/ (feature documents) |
DocumentTool (generate_document) |
always registered when compiled. Builds .docx bytes via the pure-Rust engine module (docx-rs, no subprocess) inside spawn_blocking + tokio::time::timeout; allocates the artifact with artifacts::create_artifact (kind Document), persists args.json next to it for the failed-card Retry path, then finalize_artifact or fail_artifact |
presentation/ (feature documents) |
PresentationTool (generate_presentation) |
always registered when compiled. Same shape as document/ with ppt-rs producing .pptx and kind Presentation |
Notes
The update tools are owned and registered from
platform/update/tools.rs, alongside the update domain they call.document/andpresentation/are kept structurally parallel (validate input, allocate artifact, generate bytes off the async runtime, finalize or fail the artifact) so further artifact-producing tools follow the same shape. tool surface, not a host capability.filesystem/gate.rsowns workspace descriptor scoping. The filesystem gate and system policy resolver use the same helper, which grants the descriptor root asaction_dirplus aReadWritetrusted root on a per-call clone ofSecurityPolicy;is_always_forbiddenandis_workspace_internal_pathare evaluated before any trusted-root shortcut.