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

3.5 KiB

Raw Permalink Blame History

summary, read_when, title

summary

read_when

title

Location command for nodes (location.get), permission modes, and background behavior

Adding location node support or permissions UI

Designing background location + push flows

Location Command

Location command (nodes)

TL;DR

location.get is a node command (via node.invoke).
Off by default.
Settings use a selector: Off / While Using / Always.
Separate toggle: Precise Location.

Why a selector (not just a switch)

OS permissions are multi-level. We can expose a selector in-app, but the OS still decides the actual grant.

iOS/macOS: user can choose While Using or Always in system prompts/Settings. App can request upgrade, but OS may require Settings.
Android: background location is a separate permission; on Android 10+ it often requires a Settings flow.
Precise location is a separate grant (iOS 14+ “Precise”, Android “fine” vs “coarse”).

Selector in UI drives our requested mode; actual grant lives in OS settings.

Settings model

Per node device:

location.enabledMode: off | whileUsing | always
location.preciseEnabled: bool

UI behavior:

Selecting whileUsing requests foreground permission.
Selecting always first ensures whileUsing, then requests background (or sends user to Settings if required).
If OS denies requested level, revert to the highest granted level and show status.

Permissions mapping (node.permissions)

Optional. macOS node reports location via the permissions map; iOS/Android may omit it.

Command: `location.get`

Called via node.invoke.

Params (suggested):

{
  "timeoutMs": 10000,
  "maxAgeMs": 15000,
  "desiredAccuracy": "coarse|balanced|precise"
}

Response payload:

{
  "lat": 48.20849,
  "lon": 16.37208,
  "accuracyMeters": 12.5,
  "altitudeMeters": 182.0,
  "speedMps": 0.0,
  "headingDeg": 270.0,
  "timestamp": "2026-01-03T12:34:56.000Z",
  "isPrecise": true,
  "source": "gps|wifi|cell|unknown"
}

Errors (stable codes):

LOCATION_DISABLED: selector is off.
LOCATION_PERMISSION_REQUIRED: permission missing for requested mode.
LOCATION_BACKGROUND_UNAVAILABLE: app is backgrounded but only While Using allowed.
LOCATION_TIMEOUT: no fix in time.
LOCATION_UNAVAILABLE: system failure / no providers.

Background behavior (future)

Goal: model can request location even when node is backgrounded, but only when:

User selected Always.
OS grants background location.
App is allowed to run in background for location (iOS background mode / Android foreground service or special allowance).

Push-triggered flow (future):

Gateway sends a push to the node (silent push or FCM data).
Node wakes briefly and requests location from the device.
Node forwards payload to Gateway.

Notes:

iOS: Always permission + background location mode required. Silent push may be throttled; expect intermittent failures.
Android: background location may require a foreground service; otherwise, expect denial.

Model/tooling integration

Tool surface: nodes tool adds location_get action (node required).
CLI: hanzo-bot nodes location get --node <id>.
Agent guidelines: only call when user enabled location and understands the scope.

UX copy (suggested)

Off: “Location sharing is disabled.”
While Using: “Only when HanzoBot is open.”
Always: “Allow background location. Requires system permission.”
Precise: “Use precise GPS location. Toggle off to share approximate location.”

3.5 KiB Raw Permalink Blame History