feat(telegram): parse location and venue messages#194
Closed
nachoiacovino wants to merge 1 commit intoopenclaw:mainfrom
Closed
feat(telegram): parse location and venue messages#194nachoiacovino wants to merge 1 commit intoopenclaw:mainfrom
nachoiacovino wants to merge 1 commit intoopenclaw:mainfrom
Conversation
- Add TelegramLocation, TelegramVenue, and TelegramMessageWithLocation types - Add formatLocationMessage() to convert location/venue shares to text - Add extractLocationData() for structured location access in ctxPayload - Handle both raw location pins and venue shares (places with names) - Include location in reply-to context for quoted messages Location messages now appear as: - [Location: lat, lon ±accuracy] for raw pins - [Venue: Name - Address (lat, lon)] for places ctxPayload includes LocationLat, LocationLon, LocationAccuracy, VenueName, and VenueAddress fields for programmatic access.
nachoiacovino
force-pushed
the
feat/telegram-location-parsing
branch
from
6381b2c to
56f7867
Compare
Contributor
|
Hi Nacho, that's a great PR, thanks! |
Contributor
|
Thanks @nachoiacovino! I merged this manually due to conflicts; the commit is in main as 255e77f. Really appreciate the contribution. |
Contributor
Author
awesome! thank you so much! |
dgarson
added a commit
to dgarson/clawdbot
that referenced
this pull request
Feb 7, 2026
* feat: work queue overhaul * Web: add agents dashboard * Web: add core files editor * UI: add agent skills, channels, and cron tabs * Build: prepare vercel ai agent * feat: work queue CLI commands, graph view * Web: add full web dev script * Update a2ui bundle * Work Queue: implement schema migration system with Umzug Adds proper database schema migration support to work queue backend using Umzug migration library. This fixes the "no such column: workstream" error that occurred when the gateway started with an existing database. Changes: - Add umzug dependency for schema migrations - Create migrations directory with two migrations: - 001_baseline.ts: Initial schema (work_queues + work_items) - 002_workstream_and_tracking.ts: Workstream and execution tracking - Update SqliteWorkQueueBackend to run migrations on initialization - Remove old ensureSchema() and migrateSchema() methods - Add comprehensive migration tests for all scenarios The migration system: - Tracks migration history in umzug_migrations table - Runs pending migrations automatically on initialization - Is idempotent (safe to run multiple times) - Provides a foundation for future schema changes All tests passing (7/7). Fixes startup errors with existing databases. Co-Authored-By: Claude Sonnet 4.5 (1M context) <[email protected]> --------- Co-authored-by: Claude Sonnet 4.5 (1M context) <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Parse Telegram location shares and venue messages so the agent can see them.
Changes
formatLocationMessage()to convert location/venue shares to textextractLocationData()for structured location access in ctxPayloadHow it works
Location messages now appear as:
[Location: 48.858844, 2.294351 ±12m]for raw pins[Venue: Eiffel Tower - Champ de Mars, Paris (48.858844, 2.294351)]for placesctxPayload includes new fields:
LocationLat,LocationLon,LocationAccuracyVenueName,VenueAddressUse case
Enables location-aware skills like restaurant finders - user can share their location and the agent knows where they are without needing a paired iOS/Android node.
Testing
Tested live with Telegram location shares ✅