Settings

{{ h }}

Edit SELF_HANDLES in ~/.chatwire/config.json (or re-run setup) and reload the agent to change.

{% for n in contact_names %} {% endfor %}

Phone (+15551234567), email, a Contacts name, or a named group chat.

{% include "_whitelist_rows.html" %}

Pinned contacts appear at the top of the sidebar with a ★ gold star badge.

{% include "_favorites_rows.html" %}

{% include "_password_card.html" %}

{% include "_appearance_card.html" %}

chatwire monitors outbound messages for broadcast spam. If the same message (after normalisation) is sent to too many different recipients, sending is progressively throttled and you receive an ntfy alert.

Broadcast-whitelist names

Contact names or words stripped from messages before broadcast hashing. One entry per line. Personalised greetings ("Hi Alice,") won't trigger false positives when Alice is listed here.

Saved

ntfy topic for spam alerts

Your ntfy.sh topic. Leave blank to suppress notifications.

Saved

Notification detail

Controls how much information appears in web-push notifications.

Saved

{% if contacts %}

Who can notify you

Notify from all contacts, or only hand-picked ones.

All contacts Selected contacts only

Checked contacts will trigger notifications.

{{ name or handle }}

{% endif %} {% if contacts %}

Mute contacts

Muted contacts produce no web-push notification at all.

{{ name or handle }} {% if handle in notification_muted_contacts %} muted {% endif %}

{% endif %}

Hiatus mode

Suppress notifications while you're actively chatting — no buzz if you just sent a message to that contact within the last N minutes.

Enable hiatus mode

Silence window (minutes):

Saved

Reminder timers

Push a daily reminder when you haven't heard from someone in N days. Checks once per day.

Enable reminders

Remind after (days):

Saved

Port

Port change saved — restart chatwire web for it to take effect.

Listen on

Warning: chatwire will accept connections from any network interface. Only use this if you are behind a trusted firewall.

Trust reverse proxy headers

When enabled, chatwire trusts X-Forwarded-For and X-Forwarded-Proto headers from an upstream proxy (e.g. nginx, Caddy). Do not enable if chatwire is exposed directly to the internet.

Service status

{% for svc_key, svc_label in [('bridge', 'dev.chatwire.bridge'), ('web', 'dev.chatwire.web'), ('keepawake', 'dev.chatwire.keepawake')] %} {% endfor %}

…

REST API for programmatic access to chatwire. Authenticate with X-API-Key: <key> on all /api/v1/ requests. Endpoints: POST /api/v1/send, GET /api/v1/messages, GET /api/v1/conversations, GET /api/v1/events.

Current API key

New key — copy now, it will not be shown again

{% if plugins %}

Plugins

{% include "_plugin_sections.html" %} {% endif %}

chatwire v{{ app_version }}

Made by Allen Bina

Released under the MIT License. Source code on GitHub.

Key dependencies

FastAPI MIT
Uvicorn BSD-3-Clause
Jinja2 BSD-3-Clause
htmx BSD-2-Clause
Tailwind CSS MIT
cryptography Apache-2.0 & BSD
httpx BSD-3-Clause
pywebpush MPL-2.0

chatwire v{{ app_version }} {%- if chatwire_latest is defined and chatwire_latest and chatwire_latest != app_version %} (v{{ chatwire_latest }} available) {%- endif %} · Report a bug · ♥ Sponsor

{% if plugins %}

Browse available plugins →

{% endif %}

Self handles

Whitelist

Favorites

Password

Appearance

Anti-spam

Notifications

Advanced

API

About