Caricamento in corso...
Caricamento in corso...
Last synced: Today, 22:00
Technical reference for the OpenClaw framework. Real-time synchronization with the official documentation engine.
Use this file to discover all available pages before exploring further.
OpenClaw normalizes shared locations from chat channels into:
Currently supported:
m.locationgeo_uriLocations are rendered as friendly lines without brackets:
📍 48.858844, 2.294351 ±12m📍 48.858844, 2.294351 ±12m🛰 Live location: 48.858844, 2.294351 ±12mIf the channel includes a label, address, or caption/comment, it is preserved in the context payload and appears in the prompt as fenced untrusted JSON:
textLocation (untrusted metadata): ```json { "latitude": 48.858844, "longitude": 2.294351, "name": "Eiffel Tower", "address": "Champ de Mars, Paris", "caption": "Meet here" } ```
When a location is present, these fields are added to
ctxLocationLatLocationLonLocationAccuracyLocationNameLocationAddressLocationSourcepin | place | liveLocationIsLiveLocationCaptionThe prompt renderer treats
LocationNameLocationAddressLocationCaptionLocationName/LocationAddresslive_periodlocationMessage.commentliveLocationMessage.captionLocationCaptiongeo_uriLocationIsLive© 2024 TaskFlow Mirror
Powered by TaskFlow Sync Engine