Aftergram docs

Documentation · Latest release

Aftergram docs

Everything Aftergram does, how to set it up, and how to run it without a window. Aftergram is an app for macOS, Windows and Linux that signs in to your own Telegram as one more device and keeps a private log of incoming and outgoing messages, so deleted and edited ones stay readable.

Install

Release version has not been verified on this page. Download links remain available.

Installer version is available in the download manifest.

Aftergram runs on macOS 13 Ventura or later on Apple silicon, Windows 10 and 11 (x64) and x86_64 Linux.

macOS

  1. Download the DMG and drag Aftergram.app to Applications.
  2. Open it. The first launch starts a 7-day Pro trial; after that, Free keeps working.
  3. Follow the three sign-in steps below. Aftergram then lives in the menu bar; closing the window doesn’t stop it.

Move the app to Applications before turning on the background service: the service remembers where the app was when you installed it.

The app isn't notarized yet, so macOS may say it can't be opened because Apple can't check it. Open it once with Control-click → Open and confirm, or remove the quarantine mark from Terminal: xattr -d com.apple.quarantine /Applications/Aftergram.app. The app itself is signed and runs on Apple silicon.

Windows

  1. Download the installer (.exe, Windows 10 or 11, x64) and double-click it. It installs for your user only; no administrator rights needed.
  2. Open Aftergram from the Start menu and follow the sign-in steps below. It then lives in the system tray.

The installer isn’t code-signed yet, so Windows SmartScreen may say it protected your PC. Choose More info → Run anyway.

Linux

x86_64 packages for Debian and Ubuntu (.deb) and for Fedora and openSUSE (.rpm). Install from the download folder:

sudo apt install ./Aftergram_*_amd64.deb      # Debian, Ubuntu
sudo dnf install ./Aftergram-*.x86_64.rpm     # Fedora (openSUSE: sudo zypper install)

The package pulls in WebKitGTK 4.1. Open Aftergram from your app menu; it then lives in the system tray.

Updating: Aftergram 1.6.2 and later checks for new releases at launch and every 12 hours. Choose Update now to download a signed update, install it and restart Aftergram and its running background service. Nothing installs until you choose. You can also check in Settings → Plan. Your log, settings and license stay. Older versions need one manual update: quit the app, replace it in Applications and restart the background service.

Telegram API keys

Telegram asks every app to use its own keys. You create yours once; they stay on your computer.

  1. Go to my.telegram.org and sign in with your phone number.
  2. Open API development tools and create an application. Any name and short description will do.
  3. Copy api_id (a number) and api_hash (32 characters) into Aftergram’s first step.

Sign in

  1. Phone: in international format, e.g. +44 7700 900123.
  2. Code: Telegram sends it as a message to your other devices.
  3. Cloud password, if two-step verification is on. A wrong password can simply be retried; Start over goes back to the phone step.

Aftergram appears in Telegram → Settings → Devices as Aftergram · Mac, Aftergram · Windows or Aftergram · Linux. On first sign-in it saves the recent history of your 50 latest chats, so a message deleted from then on is caught even if it was sent before you installed Aftergram.

Instead of the phone number you can choose Sign in with a QR code. Aftergram draws the code on your screen; you scan it with a phone that is already signed in to Telegram and confirm the sign-in there. The code is replaced by a new one when it expires, and two-step verification asks for the cloud password afterwards, in the same step as above. The code is drawn on the device, and the sign-in link behind it is never written to the log, the settings, the service status or an export.

You can also sign in from a terminal with aftergram login (on Windows, signing in from the window works best). With the background service running, both the window and the command line hand the new session to the service.

Reading the log

The main window with chats, the feed and the selected message.

Chat settings

Pick a chat, then Chat settings. The menu starts with the chat’s @username, or says it has none; usernames are learned from Telegram as Aftergram connects (groups you have left can’t be asked about).

Hidden chats

A hidden chat is still logged but kept out of the chat list, the feed, stats, search, export, the command line and notifications. Open them from Settings → Hidden chats, optionally behind a password (at least 4 characters, stored as a PBKDF2 hash). Closing the window locks them again.

Accounts

The account switcher.

The switcher at the top of the sidebar shows the account on view or All accounts. Its list shows each account’s connection (green: listening) and how many messages it has kept, with a search field from six accounts on, and Add account. Free listens to one account, Pro to up to ten.

Sign out (Settings → Accounts) ends the session in Telegram and removes the account; its messages stay in the log.

Media and view-once

With Pro, photos, voice and video messages, videos, audio and files up to 20 MB are downloaded as they arrive, so they stay playable after a deletion. Stickers, contacts, locations and polls are described, not downloaded. Pro

View-once media

View-once photos, videos, voice and video messages are labelled as such (View-once voice message · 0:05). Settings → Recording → Save view-once media (off by default) downloads them on arrival:

Telegram’s API terms ask apps to respect self-destructing media. Whether to keep it is your decision; that’s why the switch is off by default.

Aftergram 1.9.0, 1.10.0, 1.10.1, 1.11.0, 1.12.0 and 1.13.0: contacts, history and local intelligence

Availability: the features in this section are included in Aftergram 1.9.0, 1.10.0, 1.10.1, 1.11.0, 1.12.0 and 1.13.0. ChatGPT subscription access remains unavailable because private-client registration is not configured. Windows background-service toast behavior still needs native Windows verification; notifications remain opt-in.

QR sign-in

Aftergram 1.10.0 adds Sign in with a QR code to the phone step. The code is drawn on the device from the deep link Telegram returns for it, a fresh code replaces it when it expires, and the sign-in finishes when the scanned code is accepted. Accounts with two-step verification ask for the cloud password in the existing step, and Aftergram 1.13.0 finishes that sign-in instead of stopping at the request: the token of the account’s data centre is kept and the sign-in continues once the password is accepted. The phone number and code flow, the account slots, the sessions, the capture rules and the plan limits are unchanged.

Contacts and source-linked context

Contacts uses the normal Aftergram workspace and topbar search. Search by name, username, phone or permanent ID; sort and distinguish quiet conversations, old outgoing activity and contacts with no saved history. Sync contacts queues a full saved-address-book read for the existing active listener. No second Telegram session is opened by the window. Missing history is labelled unknown, not interpreted as inactivity.

The private-contact dossier combines saved activity, observed profile metadata and Links & mentions. Mention scans examine retained incoming text in pages of 100 messages and display how much history has been scanned. View message opens the exact local source with saved deletion/edit history; it does not launch the URL or mark the Telegram message read. Mentions are not proof of ownership.

Durable attachment downloads

Downloads shows the latest 200 attachment jobs recorded since this update: queued, downloading, retrying, blocked, failed or saved. Interrupted transfers recover after restart; retries restart the file. Telegram download cooldowns persist and Retry does not bypass them. Files are saved through a private temporary file, checked against expected size and hashed locally before completion.

The file limit defaults to 20 MiB; the interface offers 20, 50, 100 and 512 MiB. Blocked jobs explain a plan/capture/view-once/size restriction. Adjust the relevant setting first, then choose Retry. Pro, per-chat Media and the explicit Save view-once choice remain enforced. Previously saved media stays in the message log; pre-update failed downloads without stored descriptors cannot be reconstructed. Existing message/media retention rules are unchanged.

Local AI facts and promises

Open a private contact dossier → Facts & promises. Enter an installed local Ollama GGUF language model name and choose Check model to verify readiness without sending conversation text. The runtime must be on 127.0.0.1:11434; remote/cloud and embedding-only models are rejected. Aftergram does not download models.

Analyze next 100 eligible queues up to 100 eligible nonempty saved texts, at most 8 KiB each, for this account and contact. Completed and active unchanged sources are skipped before the limit, so repeating the action can reach older saved history. One message is analyzed per request. Opening the tab does not start analysis. Hidden chats and ignored/plan-paused accounts are excluded. Keep the existing background service or window listening.

Results are unreviewed suggestions with an exact source quote. Facts are restricted to incoming messages. Incoming promises appear under Owed to you, outgoing promises under You owe. Open View message for the exact saved source, deletion marker and original/edit versions; this does not mark Telegram read. The model may suggest a date only when a valid literal YYYY-MM-DD appears in its source quote. A suggestion alone never schedules a reminder.

The queue shows pending, running, retrying, failed, completed, cancelled and changed-source states. Retries and deadlines persist; interrupted requests recover after a four-minute lease. Automatic attempts stop after four failures. Cancel analysis stops queued/in-flight work and prevents late results. Repeating Analyze preserves completed unchanged sources and queues failed, cancelled or changed ones again.

Source edits or a changed Telegram-deletion marker clear stale suggestions. Local message/chat removal and retention delete their jobs and derived text. Responses from an old revision cannot overwrite a changed source. The view shows the latest 100 jobs and 200 suggestions; summaries still need human review. Automatic new-message analysis is separately controlled in AI settings, off by default, and limited to future eligible live private text. It does not sweep saved history, backfills or imports. Changing local models or disabling the option cancels its pending work; cloud work always has separate source consent. Model quality depends on the installed language model and remains a separate verification step.

Review suggestions and opt into reminders

In Facts & promises, confirm, correct the text/category, reject, show rejected, restore the AI original, or mark a promise done and reopen it. The original output and exact source quote stay visible. Restoring corrections preserves the independently managed done/open state. Source direction cannot be edited.

Only a confirmed, open promise with an explicit RFC3339 deadline and time zone can receive a reminder. Relative phrases are never converted into deadlines. Snooze, dismiss or acknowledge it; changing the deadline rearms it. Completing, rejecting, changing or removing the source invalidates it. Notifications start off and require explicit opt-in. They contain no names or message text; the app or service must be running. Known delivery failures remain visible for retry. A crash after the OS accepts a notification may produce a duplicate. Windows background-service toast delivery uses a bounded self-executable helper; its native runtime still needs Windows verification.

Optional cloud API providers

Settings → AI analysis offers Local Ollama (default), OpenRouter and Ollama Cloud. Select a provider and exact model ID, enter its key and explicitly allow confirmed cloud batches, then save. Keys are stored in macOS Keychain, Windows Credential Manager or Linux Secret Service. They are never returned to the screen or stored in the message database/settings JSON. There is no plaintext-file fallback. Failed old-key deletion remains visible and can be retried after unlocking the system store.

Check model catalog sends credentials/model metadata only, without messages or inference. Catalog availability does not necessarily establish generation entitlement, valid credits or key access. Opening settings never starts analysis.

In the contact dossier, choose Preview cloud batch. Review the exact selected text, message direction, timestamps and saved deletion markers. Up to 100 eligible sources are selected; completed unchanged sources and active jobs are skipped. Send and analyze is disabled until you check the batch-specific consent box. Cancelling the preview sends nothing and consent is not remembered for another preview. Previews expire after ten minutes; source/settings changes or another account/chat cannot reuse them.

The selected text and incoming/outgoing direction go only to the displayed provider/model, one source per request, without attachment files or separate contact IDs. OpenRouter forwards to the selected model’s provider. Cloud charges may apply. Approved jobs keep the same provider/model/settings revision and source fingerprints across retries and restart. Rate-limit pauses persist; settings changes cannot bypass them. Changing provider/model/key or disabling cloud cancels old cloud work and requires fresh consent. Cancellation cannot recall a request already transmitted; late results from cancelled, hidden or changed sources are rejected.

ChatGPT subscription login is not included. The documented plan-usage flow is available to open-source and selected private clients; Aftergram remains private and no approved client registration is configured for this integration. API-provider keys are not ChatGPT subscription access. Provider access, available credits and model quality depend on your account and selected model.

Controlled Telegram history import

Select one account → Contacts → Import history, choose 1–20 private contacts and inclusive local start/end dates, then count messages. A dossier’s Import history tab fixes that contact. The preview shows the exact interval and UTC offsets and expires ten minutes after requesting it. Changed dates, contacts, media or model require a fresh count. Queue only that reviewed preview; the existing listener makes the Telegram requests.

Jobs retain their cursor, scanned/newly saved/skipped counts and Telegram cooldowns across restart. Pause/resume does not reset cooldowns; cancel keeps committed pages. Media and optional local analysis are off by default. Media follows the existing plan, capture, view-once, size and retention rules. Local analysis requires an installed, checked Ollama language model and covers only newly saved eligible texts; cloud still requires a separate exact-source preview and consent.

Import never replaces retained originals, edits, deletion observations, manual removals or reviewed evidence with older duplicates. Hidden, ignored, unavailable and plan-paused contacts are excluded. Preview counts are estimates, not frozen snapshots. Telegram history cannot recover messages or edits Telegram no longer supplies, and existing retention can prune ordinary old imported texts and their derived work.

Local speech transcription and image text

Settings → AI analysis configures already installed FFmpeg, whisper.cpp and a speech model, plus Tesseract and its language data for OCR. Metadata readiness checks do not prove a tool can run. No tools, models or language data are downloaded. Speech and image automatic modes are separate and off by default; enabling either processes eligible existing current attachments and future saved files. Disabling cancels automatic queued/running work for that mode and preserves manual requests and unchanged completed results.

Open a saved attachment or Observed history → Attachments → Recognition status to request, retry or cancel that exact saved version. Older retained versions require a manual request. Generated text is separate from the Telegram caption; recognition never opens Telegram or marks messages read. Source/file/settings/policy changes invalidate it. Pro, media, hidden/ignored and view-once restrictions still apply.

Audio is limited to one hour; processing, output and temporary workspaces are bounded. PDF and multipage OCR are unsupported. Words searches current verified media text; historical recognition is excluded from ordinary search. Generated excerpts are labelled, and partial preparation/file-check coverage stays visible with Search more when another page is available.

Words preserves literal text, name and chat matching. Meaning adds optional local Ollama embeddings and bounded hybrid retrieval. In Settings → AI analysis → Meaning search, choose an installed local GGUF embedding model, check metadata if needed, explicitly enable indexing and save. Indexing starts off; opening settings, Words or a blank query never enables it or submits embedding text. Aftergram downloads no models.

Missing models, unavailable vectors or disabled indexing produce a visible Words fallback and partial-coverage reason. Search more appears only when another bounded page can be requested. Progress describes a checked sample of at most 16 documents and 64 chunks each, with further media verification bounds, never archive totals or a completion percentage. A background service’s semantic phase is unknown. Retry processes a bounded blocked batch; rebuild resets only the derived index and preserves the enabled choice. Pause indexing before externally replacing local models, then rebuild.

Select a result to open its exact retained private/group message even outside loaded feed pages. Current captions, machine-generated media text and reviewed fact/promise evidence remain separate; saved Telegram deletion observations and paged edit history remain visible. Hidden, ignored, stopped, plan-paused, locally removed and rejected sources are excluded as applicable. Changed evidence fails explicitly instead of opening a nearby message. No remote URL, Telegram read operation or media playback is triggered.

The background service after an update

Aftergram 1.10.1 repairs a newly signed-in account that stayed silent after an update of the app. The background service keeps the accounts it loaded when it started, and a new account only reaches it when the service restarts; the app could not restart it, because the restart first waits for the running service to confirm a safe stop and a service from an older build never answers that. The app now replaces a service that runs an older build, and it does so when the app starts, so the background service always serves the current code and every signed-in account is collected.

Shared context and workspace backup

Promises & reminders across contacts and Shared mentions: Contacts includes a paged board using the dossier review/reminder controls and exact source views. Shared mentions compares bounded, account-scoped incoming saved text from distinct contacts. Matching emails, literal links or wallet-shaped values do not establish relationships, ownership or wallet validity. Coverage is explicitly partial; it is not an archive-wide graph, and no links are crawled or opened.

Workspace backup and restore: Settings → Data writes a sanitized, unencrypted ZIP with a progress indicator. Sessions, API credentials, license keys, provider keys and active cloud grants are excluded. The existing Pro/7-day-trial export entitlement applies; hidden chats require unlock. Close Aftergram, then run aftergram restore <backup.zip> <empty-folder>. It validates checksums, schema and media paths and installs only into an absent or empty destination. Open the result with aftergram --archive-dir <folder>; it has no Telegram sessions and does not start background processing. The separate Shadow Dossier archive importer is not included. ChatGPT subscription access still needs private-client registration.

Contact/profile metadata, transfer references, AI suggestions, reviews, reminders, recognition and index state remain local. They are not included in the existing text/JSON export or Postgres message copy; Postgres remains scoped to messages, text edits and direction/read metadata. Workspace backup is a separate full-workspace ZIP. Website screenshots use sample conversations.

Export

Export saves what the feed shows — one chat, one account or everything, with the current filter — as .txt or .json. Pro

=== Dan K. · private chat ===
[2026-09-27 14:26:30] Dan K.: forget what I said yesterday about Alex
    ↩ reply to You: so what's the story with Alex?
    ✕ deleted 2026-09-27 14:27:13

JSON has one object per chat with its messages: id, date, sender, text, media, mediaFile, deletedAt, replyTo and versions (every version, when edited).

Settings

Settings (⚙) is one window with the sections on the left, grouped by what each group decides: Capture (Recording, Hidden chats), Accounts & service (Accounts, Background), Intelligence (AI analysis), Storage (Data & Postgres) and Subscription (Plan).

Aftergram 1.12.0 splits Settings → AI analysis into four sections of its own: Model & cloud, Media recognition, Meaning search and Automatic. Each section keeps its own fields, its own buttons and its own saved state, so a half-finished edit stays where it is while another section is open. The providers, tools, models and permissions are configured exactly as before.

RecordingDefault recording for private chats and groups: media, deletions, edits, notifications. How long to keep regular messages: 7 days (Free) up to 10 years (Pro/trial); deleted and edited ones are kept forever. Save view-once media (off by default, Pro).
Hidden chatsOpen or lock hidden chats, set or change their password. Not logged lists chats you stopped logging, with Resume.
BackgroundBackground service: Run in background, Start, Stop, Remove (see below). Open at login. Keep the computer awake: Off, On power, Always.
AccountsEach account’s connection, Sign out, Add account.
Data & PostgresSize on disk split into messages and media; Show in Finder (Explorer, file manager). Postgres copy: URL, Test, Turn on/off, status, Copy all local data (Pro).
PlanFree, trial or Pro; Upgrade or Remove key.

Background service

The service listens to Telegram without the window: it starts at login and keeps going when you close Aftergram. macOS and Linux restart it after a crash; Windows starts it again at the next login or when you choose Start. Turn it on in Settings → Background → Run in background, or:

If it is stopped, choose Start service on the startup screen or Start in Settings. Aftergram waits until it reports running and shows launch errors. You can retry or choose Use this window instead to remove the service and collect messages while the window is open. Starting from the app refreshes the executable path after a move or update; move the app to its permanent location first.

aftergram service install
aftergram status            # running? each account listening?
macOSlaunchd agent app.aftergram.service.
Linuxsystemd user service aftergram.service (systemctl --user status aftergram).
WindowsA login entry that starts it in the background. It isn’t restarted automatically after a crash; start it again from Settings or with aftergram service start. The background service logs ordinary message notifications. Optional promise reminders use a native toast helper; Windows delivery still needs native verification.

While it runs, the window is a viewer: it shows what the service collects and changes to settings reach the service within seconds. Signing in, adding and signing out accounts work from the window too — the window does the sign-in and restarts the service with the new session. Only one process listens at a time; the other waits.

On macOS the aftergram command is linked to ~/.local/bin/aftergram when the service is installed. If your shell doesn’t find it:

echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc && source ~/.zshrc

On Linux the package installs /usr/bin/aftergram. On Windows it is aftergram.exe in the install folder.

Command line

The app binary is also the command line — Aftergram.app/Contents/MacOS/aftergram on macOS, /usr/bin/aftergram on Linux, aftergram.exe in the install folder on Windows. Without a command it opens the window.

CommandWhat it does
service installRun Aftergram in the background (starts at login, restarts itself).
service start · stopStart the installed service now; stop it until the next login.
service uninstallRemove the background service. Data stays.
statusService, plan, each account’s state, the Postgres copy.
loginAdd an account, or sign back in to one whose session ended (API keys, phone, code, cloud password).
accountsList accounts.
chatsTable of logged chats: messages, deleted, edited, last message. Hidden chats are left out.
logsThe last 40 lines of the service log.
db set <url>Test and turn on the Postgres copy.
db statusIs the copy up to date; queue; last sync; URL without password.
db migrateCopy every local message to Postgres again (safe to repeat).
db offStop copying. What is in Postgres stays.
runListen in the foreground (what the service runs).

Postgres copy

RecordingDefaults for every chat. Any chat can differ via Chat settings.
PrivateGroups Mediaphotos, voice, video, files Deletionsmark what disappears Editskeep every version Notificationswhen something is deleted
Keep regular messages forDeleted and edited ones are kept forever.
Save view-once mediaSaved on arrival, stays unopened in Telegram. Off by default.
Hidden chatsStill logged, kept out of the list, feed, search and notifications.
2 hidden chatsShown only when opened with the password.
Password is onAsked every time you open hidden chats.
Not logged
FLFlat 42 · noiseJack · new messages are ignored
BackgroundHow Aftergram keeps listening while you’re not looking.
Background serviceListens without the window, starts at login, restarts itself.Running · pid 4242
aftergram status · aftergram logs
Open at loginAftergram starts in the menu bar, without a window.
Keep the computer awakeA sleeping computer can’t receive messages.
AccountsSigning out keeps that account’s messages on this computer.
JJackConnected · 871 kept
JWJack · workConnected · 1,204 kept
2 of 10 on Pro
Data & PostgresEverything stays on this computer unless you copy it to your own database.
On this computer · 391 MB~/Library/Application Support/app.aftergram.mac Messages 286 MB   Media 105 MB
Postgres copyEvery message in your own Postgres, for scripts and dashboards.Up to date · 5 s ago
postgres://me@db:5432/aftergram
PlanYour key is checked on this computer, never online.
Aftergram ProLicensed to jack@example.com · free updates for 1.x
IncludedUp to 10 accounts · history up to 10 years · media and view-once · per-chat settings · export · Postgres copy

Aftergram can mirror its log into a Postgres database you run — for SQL, scripts, Grafana or Metabase. Your computer stays the source of truth. Pro

Turn it on

Settings → Data & Postgres: paste a URL, Test, Turn on. Or aftergram db set <url>. Aftergram creates its tables itself. A local database in Docker:

docker run -d --name aftergram-pg --restart unless-stopped \
  -e POSTGRES_USER=aftergram -e POSTGRES_PASSWORD=aftergram -e POSTGRES_DB=aftergram \
  -p 5432:5432 -v aftergram-pg:/var/lib/postgresql/data postgres:17

aftergram db set postgres://aftergram:aftergram@localhost:5432/aftergram

Hosted Postgres works too; TLS is used when the server offers it, and ?sslmode=require insists on it.

How it syncs

Tables

messages
account, scope, msg_idPrimary key. account is your Telegram user id; scope is 0 for private chats and basic groups, the channel id for supergroups.
chat_id, chat_title, chat_kindChat (user or group).
sender_id, sender_nameWho sent it.
date, textUnix seconds; current text.
media_kind, media_label, media_pathMedia type, label, local file path.
deleted_atWhen it disappeared from the chat, or null.
edit_count, last_edit_atEdits.
reply_to, reply_sender, reply_textThe message it answered, as it was then.
synced_atWhen Postgres last got this row.

edits(account, scope, msg_id, at, text) holds every version of edited messages, the original first. aftergram_meta holds the schema version.

Example queries

-- what was deleted this week
SELECT chat_title, sender_name, text, to_timestamp(deleted_at) AS deleted
FROM messages WHERE deleted_at > extract(epoch FROM now() - interval '7 days')
ORDER BY deleted_at DESC;

-- every version of edited messages
SELECT m.chat_title, e.text, to_timestamp(e.at) AS at
FROM edits e JOIN messages m USING (account, scope, msg_id)
ORDER BY m.date, e.at;

-- who deletes the most
SELECT sender_name, count(*) FROM messages
WHERE deleted_at IS NOT NULL GROUP BY 1 ORDER BY 2 DESC LIMIT 10;

Where data lives

Everything is in one folder in your user account:

macOS~/Library/Application Support/app.aftergram.mac/
Linux~/.local/share/app.aftergram.mac/
Windows%APPDATA%\app.aftergram.mac\

On macOS and Linux the files are readable only by your user account; on Windows they live in your user profile. Inside:

aftergram.dbThe log (SQLite).
media/Downloaded media.
accounts/<slot>/session.dbEach account’s Telegram session.
config.jsonAPI keys, settings, per-chat rules, Pro key, Postgres URL.
service/Service status, service.log, Postgres copy status.

There is no Aftergram content server. Telegram traffic goes directly to Telegram. Only the text and direction of a cloud batch you review and explicitly approve are sent to the selected provider; a Postgres copy is sent only to the database you configure.

Plans and licence

Every install starts with 7 days of Pro. Free then keeps catching deletions and edits for one account, retaining regular messages for 7 days and deleted or edited messages indefinitely. Pro is a one-time 20 USDT key for all your computers: up to 10 accounts, up to 10 years of regular messages, media and view-once media, per-chat settings, export and the Postgres copy. Enter the key in Settings → Plan; it is checked on your computer, offline.

Buy Pro with USDT through Crypto Bot. Enter your email on the purchase form, then pay the individual invoice. Crypto Bot displays your license key after payment; save it and paste it into Aftergram. We do not email the key. The same download includes Free, the 7-day trial and Pro.

Troubleshooting

“needs sign-in” in aftergram status

Telegram ended the session (for example, it was terminated in Devices). Sign in again from the window or with aftergram login; the log is kept.

Nothing arrives after the computer slept

Aftergram reconnects by itself after sleep and fetches what arrived meanwhile. A message sent and deleted during sleep can’t be caught; set Settings → Background → Keep the computer awake → On power. On a Mac this works while charging and can hold off sleep even with the lid closed; on Windows and Linux it blocks idle sleep, but closing the lid may still put the computer to sleep.

aftergram: command not found

On macOS, add ~/.local/bin to your PATH (see Background service), or use the full path to the app binary. On Windows, run aftergram.exe from the install folder.

macOS: “Aftergram cannot be opened because Apple cannot check it for malicious software”

The app isn't notarized yet, so Gatekeeper blocks the first launch. Open it once with Control-click → Open and confirm, or remove the quarantine mark from Terminal: xattr -d com.apple.quarantine /Applications/Aftergram.app.

Windows: “Windows protected your PC”

SmartScreen warns about apps that aren’t code-signed yet. Choose More info → Run anyway.

Postgres says “stopped”

The URL, password or permissions are wrong. aftergram db status shows the server’s message; fix it with aftergram db set <url>.

More detail

aftergram logs shows the service log; aftergram status shows each account and the Postgres copy.

Uninstall

First run aftergram service uninstall if you used the background service. Then:

Finally remove the Aftergram session from Telegram → Settings → Devices.

Contacts

Questions, bug reports or ideas — write wherever is easiest.