mirror of https://github.com/hanzoai/bot.git synced 2026-10-30 17:24:26 +00:00

Files

T

zeekay acaeda400a Eradicate OpenClaw — resolve merge conflicts and finish the rebrand

Three coordinated things:

1. Resolve the committed upstream/main merge conflicts. 94 files were
   sitting with raw <<<<<<< HEAD ... >>>>>>> upstream/main blocks. Every
   conflict had HanzoBot/Bot on HEAD and OpenClaw on upstream. Resolved
   by keeping HEAD everywhere — 540 conflict blocks.

2. Rewrite remaining OpenClaw text refs.
     OPENCLAW   → HANZO_BOT
     OpenClaw   → HanzoBot          (PascalCase type identifiers)
     openclaw   → bot               (codebase convention — botToken,
                                    botUsername etc.; avoids invalid
                                    hyphenated JS identifiers)
     openclaw[_]/openclaw[A-Z] → bot[_]/bot[A-Z]   (compound)
     ai.openclaw.x → ai.hanzo.bot.x  (JVM package path)

3. Delete or rename openclaw-named file paths (116 of them). Dead
   duplicates with a Bot-named canonical from the partial migration:
   deleted. Otherwise renamed.
     ai/openclaw/**           → deleted (ai/hanzo/bot/** canonical)
     Sources/OpenClaw*/       → deleted (Sources/Bot* canonical)
     Tests/OpenClawIPCTests/  → deleted (Tests/BotIPCTests canonical)
     OpenClawKit/             → deleted (BotKit canonical)
     openclaw-tools.*.ts      → deleted (bot-tools.*.ts canonical)
     openclaw-root.ts etc.    → deleted (bot-root.ts canonical)
     types.openclaw.ts        → deleted (types.bot.ts canonical)
     extensions/*/openclaw.plugin.json → renamed hanzo-bot.plugin.json
     docs/start/openclaw.md   → renamed hanzo-bot.md (+ zh-CN)
     docs/assets/openclaw-*.png, whatsapp-openclaw*.jpg → deleted
     scripts/.../openclaw-*   → deleted (bot/hanzo-bot parallels)
     openclaw.mjs             → deleted (hanzo-bot.mjs is package.bin)

Then patched 65 broken JS/TS import strings where hanzo-bot had ended
up inside an import path ('./types.hanzo-bot.js' → './types.bot.js'
etc., since the on-disk filename uses the brand-neutral bot- prefix).

Pre-existing lint debt cleaned up to get oxlint --type-aware to 0/0:
removed the dead i18n test that referenced a path no longer existing;
defined the missing DIDConfig and WalletConfig types in types.base.ts
(they were imported but never declared); dropped unused imports;
collapsed redundant type assertion and a tautological meta.bot lookup
that the openclaw→bot rename made redundant.

The a2ui.bundle.js generated artifact is kept at its pre-rebrand
contents — it gets regenerated by 'pnpm canvas:a2ui:bundle' from
sources I cannot rebuild in this commit; the source side is clean.

Verified: 0 occurrences of openclaw (case-insensitive) in tree source
content, 0 file or directory paths with openclaw in the name; oxlint
--type-aware src test reports 0/0.

2026-05-11 17:56:29 -07:00

1.7 KiB

Raw Permalink Blame History

summary, read_when, title

summary

read_when

title

Inbound channel location parsing (Telegram + WhatsApp) and context fields

Adding or modifying channel location parsing

Using location context fields in agent prompts or tools

Channel Location Parsing

Channel location parsing

HanzoBot 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.location with geo_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 use live_period.
WhatsApp: locationMessage.comment and liveLocationMessage.caption are appended as the caption line.
Matrix: geo_uri is parsed as a pin location; altitude is ignored and LocationIsLive is always false.

1.7 KiB Raw Permalink Blame History

Channel location parsing

Text formatting

Context fields

Channel notes

1.7 KiB

Raw Permalink Blame History