Built-in capabilities

Kernel tools are Tater's native action layer.

They handle files, web inspection, memory, artifacts, and delivery before Hydra reaches for a Verba.

Kernel tools

Catalog and inspection

list_tools

list kernel and enabled verba tools for current portal

Kernel tools

Workspace and files

attach_file

attach an available artifact/local file and optionally send it to a destination platform/target

Workspace and files

delete_file

delete a local file

Workspace and files

download_file

download a file from a concrete file URL after discovery/inspection (actual file retrieval)

Workspace and files

extract_archive

extract archives to a target directory

Workspace and files

list_archive

inspect archive entries

Workspace and files

list_directory

list files and folders

Workspace and files

list_workspace

list workspace notes

Workspace and files

read_file

read local file contents

Workspace and files

search_files

search text across local files

Workspace and files

write_file

write content to a local file

Workspace and files

write_workspace_note

append a workspace note

Kernel tools

Web and media

image_describe

describe an explicit image using an artifact_id, URL, blob, or local path

Web and media

inspect_webpage

inspect and extract content from a specific webpage URL (title, summary text, links, images)

Web and media

search_web

Search the public web through Google's Programmable Search backend after Web Search is configured in Tater WebUI.

Kernel tools

Memory and delivery

send_message

queue a cross-portal notification/message only when the user explicitly asks to notify or message a destination (never for normal chat replies)

Web search setup

How to enable Google's search backend for the search_web kernel tool.

This is a core capability, not a Verba. The current Tater WebUI path is Settings -> Integrations -> Web Search.

Google CloudCustom Search JSON APIAPI key

Create a Google API key

The search_web kernel tool uses Google's Custom Search JSON API credentials.

Open Google Cloud Console, create or select a project, then enable Custom Search API under APIs and Services -> Library.
After the API is enabled, go to APIs and Services -> Credentials and create an API key for Tater.
Keep that key handy because Tater's WebUI expects it as the Google API Key for web search.

Google Cloud Console Custom Search JSON API Docs

Programmable Search EngineCXEntire web

Create a Search Engine ID (CX)

Google also requires a Programmable Search Engine and its Search Engine ID.

Create a Programmable Search Engine, then open its control panel and enable Search the entire web if you want broad public-web results.
Open the generated search page URL and copy the value after cx=, because that is the Search Engine ID Tater stores.
Tater's core search flow is only ready once both the API key and the CX value are saved.

Programmable Search Engine

Settings -> IntegrationsWeb SearchKernel tool

Enter the keys in Tater

Web search is configured from Integrations because it powers a kernel tool, not a Verba.

Open Tater WebUI and go to Settings -> Integrations -> Web Search.
Paste Google API Key and Google Search Engine ID (CX), then save the settings.
The current code stores those values as tater:web_search:google_api_key and tater:web_search:google_cx, with a legacy fallback for older plugin-style settings.
After that, Hydra can call search_web for current web research and article lookup tasks.

querysitecountrylanguage

What the kernel tool supports

The current search_web implementation accepts a few focused filters on top of the main query.

query is required, while num_results, start, site, safe, country, and language are optional.
site narrows results to one domain, country maps to Google's gl parameter, and language maps to lr.
If the Google credentials are missing, the tool returns a configuration error that points operators back to WebUI settings.

API Reference