Telegram Desktop

Decision Guide

• Read references/repository-map.md when the task starts with "where is this implemented?" or spans multiple subsystems.
• Read references/build-and-conventions.md when the task is about building, style compliance, localization, request wiring, or validation.
• Prefer the repository root AGENTS.md over generic build habits when the two disagree.
• Prefer the local .style, lang.strings, and .tl schema files over assumptions drawn from other Qt or Telegram clients.

Constraints

• Do not edit generated build output under out/ unless the user explicitly asks for generator or build-output work.
• Do not hardcode dimensional constants in C++ when a .style value is appropriate.
• Do not use std::optional::value(); use value_or, operator bool, or dereference after checks.
• Prefer direct subtype casts such as asUser() plus null-check over isUser() followed by cast.
• Keep multi-line calls one argument per line and keep continuation operators at the start of continued lines.
• Assume full from-scratch builds require Telegram API credentials (TDESKTOP_API_ID and TDESKTOP_API_HASH) and platform-specific dependency setup.

Resources

• references/repository-map.md: root layout, SourceFiles hotspots, and where to look for each class of change.
• references/build-and-conventions.md: build paths, stop conditions, style rules, localization guidance, API request patterns, and validation expectations.