Weather

Ask your AI client for the weather anywhere: right now, hours or days ahead, or on a specific day in the past. Orchard answers with Apple’s weather data. Weather is a Pro integration built around a single tool.

What you can do

“What’s the weather in Tokyo right now?”
“Give me the hourly forecast for Tokyo from 2pm to 6pm tomorrow.”
“What was the weather in Beijing last Tuesday?”
“Give me the 10-day forecast for New York.”
“What’s the weather like where I am?”

Available tools

Tool	Description
`weather_get`	Current conditions, a daily forecast/history range, or an hourly forecast range, depending on `granularity`, `start_date`, and `end_date`.

Key parameters:

Parameter	Notes
`location`	Location name (e.g. `"Beijing"`) or `"lat,lon"` coordinates. Omit to use the device’s current location.
`granularity`	`daily` (default) or `hourly`.
`start_date` / `end_date`	ISO 8601. Omit both for current weather; provide `start_date` alone for a single period.

daily granularity supports historical data back to August 1, 2021 and forecasts up to 10 days ahead, with a 10-consecutive-day maximum range. hourly granularity is forecast-only, up to 7 days ahead, with a 7-consecutive-day maximum range. The tool docs recommend including a time component (e.g. 2024-01-20T14:00:00Z) for hourly requests; a date-only value parses as midnight UTC, likely failing the “must be in the future” check rather than being rejected for missing a time.

Required permissions

Weather itself needs no permission. The only one involved is Location (When In Use), and only when you omit location (or --lat/--lon): Orchard falls back to the device’s current location, triggering the standard macOS prompt the first time it’s used.

CLI usage

orchard weather get --location "Tokyo"

orchard weather get --lat 35.6762 --lon 139.6503 --granularity hourly --start-date "2024-01-20T14:00:00Z" --end-date "2024-01-20T18:00:00Z"

orchard weather get --location "Beijing" --start-date "2024-01-15" --json

For a negative latitude or longitude, write it as --lon=-74.0060 rather than --lon -74.0060 — the CLI reads a space-separated negative number as a new flag and fails with a usage error.

Structured output

Most measurements — temperature, feels-like temperature, wind speed, pressure, visibility, precipitation amount, snowfall, and dew point — are returned as {"value": ..., "unit": ...} objects, for example {"value": 32.8, "unit": "°C"}. A few fields (humidity, UV index, cloud cover, precipitation chance, and wind gust) are returned as plain numbers without a unit wrapper. Add --json to get this wrapped in the CLI’s standard {output, success, message} envelope.

Tips & limitations

Requesting a date range that mixes past and future days (e.g. start_date last week through end_date tomorrow) is handled automatically: Orchard fetches the historical and forecast portions separately and merges them.
An hourly request with a start_date in the past is rejected outright; hourly data is forecast-only.
A daily range longer than 10 consecutive days, or an hourly range longer than 7 consecutive days, returns a validation error rather than being silently truncated.
If location resolution fails (bad location name, no coordinates, and no device location available), the tool returns an error asking for a specific location instead of guessing.