Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Feature Request] [GOWS] Expose DeviceProps.PlatformType so "Linked devices" can show a clean custom app name

Aperta
  • Qualcosa non va?
#2,152 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
1-2 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
go
Ambito
backend

Direzione di ricerca

Start by tracing how GOWS maps WAHA_CLIENT_BROWSER_NAME and WAHA_CLIENT_DEVICE_NAME into whatsmeow's DeviceProps; the issue does not name the relevant files or tests. Compare the existing browser enum handling with the DESKTOP option described in the issue, then identify how configuration is documented and tested. Done when GOWS can emit a configurable platform type that produces the requested clean Linked devices label without changing the pairing-code display name.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Context

Since #1109 (thanks!), WAHA supports WAHA_CLIENT_DEVICE_NAME and WAHA_CLIENT_BROWSER_NAME, which on GOWS feed whatsmeow's store.DeviceProps (Os and PlatformType). This lets self-hosters customize the entry shown in WhatsApp → Linked devices.

Limitation

On GOWS, WAHA_CLIENT_BROWSER_NAME is mapped to DeviceProps.PlatformType through a fixed enum (chrome/firefox/safari/edge/opera/ie → that browser type; any other value → UNKNOWN). As a result, the only reachable outcomes for the Linked-devices entry are:

  • "<Browser> (<DeviceName>)" when a recognized browser is used — e.g. WAHA_CLIENT_BROWSER_NAME=Chrome, WAHA_CLIENT_DEVICE_NAME=MyApp → "Google Chrome (MyApp)", or
  • "Other device" (generic "?" icon) when the browser value is unrecognized (UNKNOWN) — and in this case WhatsApp drops the Os/device-name text entirely.

There is no configuration that shows just the app/brand name (e.g. "MyApp") as the primary label. The custom name can only ever appear inside parentheses after a browser name.

Root cause / why this is possible in whatsmeow

The primary label rendered by the phone is driven by DeviceProps.PlatformType. whatsmeow supports values (e.g. DESKTOP) that WhatsApp renders as a single clean label — just the OS/name, with no browser prefix (the same way an official "macOS" / "Windows" desktop entry appears). See whatsmeow discussion #469. GOWS currently never emits these — only the browser enums and UNKNOWN — so this clean rendering is unreachable through WAHA config.

Note: this is not about the pairing-code display name

This is purely about the persistent DeviceProps sent at registration. It does not touch the pairing-code clientDisplayName (hardcoded "Chrome (Linux)" in GOWS), which correctly keeps the pairing-code flow working — so this request does not risk the 400 validation the docs warn about for custom names.

Request

Allow controlling DeviceProps.PlatformType on GOWS, so integrators can show their own brand cleanly in Linked devices. Any of:

  1. A new value for WAHA_CLIENT_BROWSER_NAME (e.g. accept Desktop) that maps to PlatformType=DESKTOP, so WAHA_CLIENT_DEVICE_NAME renders as the sole label; or
  2. A dedicated env var, e.g. WAHA_GOWS_DEVICE_PLATFORM_TYPE; and/or
  3. Per-session support via config.client for GOWS (today it's env-only per the docs).
Use case

Self-hosted integrations that want their product name (not "Firefox (Ubuntu)" or "Other device") shown in the user's Linked-devices list, for trust and clarity.

Environment
  • WAHA Plus, engine GOWS, image waha_plus:gows-2026.5.1
  • Verified: WAHA_CLIENT_BROWSER_NAME=Chrome → "Google Chrome (MyApp)"; an unrecognized value → "Other device" with the device name dropped.
Image
Lingua principale
TypeScript
Stelle
7.6k
Fork
1.8k
Merge medio
2g 21h
PR unite (30g)
7

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di devlikeapro/waha

Tutte le issue di devlikeapro/waha

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.