Using tools

Extend a WEDNESDAY turn with search, files, research, location context, projects, connectors, and other bounded execution capabilities. Tool work is represented as typed runtime state rather than hidden model side effects.

SearchFilesResearchProjectsConnectors

User request
   ↓
WEDNESDAY runtime
   ↓
Tool start → progress/state → completion
   ↓
Structured result returned to the active turn

Available tool families

⌕Search and retrievalSearch durable WEDNESDAY state and support retrieval-oriented workflows. ▣Files and LibraryUpload, inspect, select, attach, retrieve, and manage account-owned file resources. ✦Deep researchTrack longer-running research work as durable task state rather than a single request. ◇Projects and contextUse project instructions, settings, files, conversations, connectors, and work history as scoped context. ↗ConnectorsWork with explicitly authorized external resources while preserving connector scope and approval boundaries. ◎Location and place contextUse location preferences and place-enrichment capabilities where the product flow authorizes them.

Tool lifecycle

The live stream protocol can represent tool start, progress, state transition, and completion events. Stable turn, part, and tool hierarchy identifiers let a client render nested or parallel work without inferring execution state from prose.

Authority and approvals

Tool availability never implies unlimited authority. File operations remain account-scoped, connector operations remain connector-scoped, public-network access is bounded by runtime policy, and risky external actions can require explicit approval before execution.

Failure handling

A tool result can fail independently of the surrounding model turn. Clients should preserve tool state, surface meaningful failures, and avoid rewriting a failed execution as if the model merely “changed its mind.”

Public capability policy

A tool becomes a supported developer capability only when its public name, inputs, outputs, authority requirements, failure behavior, and lifecycle are stable enough to depend on.

Internal tool kinds, telemetry labels, and implementation-specific execution modules are not automatically public developer tools.