mirror of
https://github.com/hanzoai/bot.git
synced 2026-10-30 17:24:26 +00:00
Comprehensive rename of all openclaw references to hanzo-bot equivalents: - Package: openclaw → @hanzo/bot - Binary: openclaw → hanzo-bot - Types: OpenClaw* → Bot* - Env vars: OPENCLAW_* → BOT_* - Android: ai.openclaw.android → ai.hanzo.bot.android - iOS/macOS: ai.openclaw.* → ai.hanzo.* - Swift modules: OpenClaw* → Bot* - Plugins: openclaw.plugin.json → bot.plugin.json - Paths: .openclaw/ → .hanzo/bot/ - URLs: github.com/openclaw → github.com/hanzoai
1.7 KiB
1.7 KiB
summary, read_when, title
| summary | read_when | title | ||
|---|---|---|---|---|
| Inbound channel location parsing (Telegram + WhatsApp) and context fields |
|
Channel Location Parsing |
Channel location parsing
Hanzo Bot normalizes shared locations from chat channels into:
- human-readable text appended to the inbound body, and
- structured fields in the auto-reply context payload.
Currently supported:
- Telegram (location pins + venues + live locations)
- WhatsApp (locationMessage + liveLocationMessage)
- Matrix (
m.locationwithgeo_uri)
Text formatting
Locations are rendered as friendly lines without brackets:
- Pin:
📍 48.858844, 2.294351 ±12m
- Named place:
📍 Eiffel Tower — Champ de Mars, Paris (48.858844, 2.294351 ±12m)
- Live share:
🛰 Live location: 48.858844, 2.294351 ±12m
If the channel includes a caption/comment, it is appended on the next line:
📍 48.858844, 2.294351 ±12m
Meet here
Context fields
When a location is present, these fields are added to ctx:
LocationLat(number)LocationLon(number)LocationAccuracy(number, meters; optional)LocationName(string; optional)LocationAddress(string; optional)LocationSource(pin | place | live)LocationIsLive(boolean)
Channel notes
- Telegram: venues map to
LocationName/LocationAddress; live locations uselive_period. - WhatsApp:
locationMessage.commentandliveLocationMessage.captionare appended as the caption line. - Matrix:
geo_uriis parsed as a pin location; altitude is ignored andLocationIsLiveis always false.