tai/research/tui-framework-design/mini-apps-docs-settings-button.md

# Mini Apps SDK docs — SettingsButton

## Metadata

| Field | Value |
|---|---|
| Institute | Molodetz Institute — Research & Retrieval Division |
| Subject | tui-framework-design |
| Document type | Source Dossier |
| Tier | 1 |
| Source title | Settings Button documentation (Telegram Mini Apps SDK docs) |
| Source URL | https://docs.telegram-mini-apps.com/platform/settings-button |
| Source publisher / author | Telegram Mini Apps community (docs.telegram-mini-apps.com, over the official protocol) |
| Source type | vendor docs |
| Source date (published) | Unknown — not stated |
| Date researched | 2026-10-11 |
| Researched by | tai (agent), model: Muse Spark, on behalf of retoor |
| Research method | direct page fetch |
| Confidence | Medium |
| Status | Active |

## Summary

Community SDK documentation for the Mini App Settings button: a top-right menu item that developers opt into showing, publicly available to all developers since version 6.10.

## Key findings

- The Settings button lives in the top-right menu of the Mini App chrome.
- It is opt-in: the developer calls `show()` to make it appear.
- It has been public to all developers since v6.10.

## Pros / strengths

- Settles placement (menu, not header button) and availability (opt-in, v6.10+) in three checkable facts.
- Consistent with the official chrome inventory (Settings as context-menu item).

## Cons / limitations / caveats

- Community docs over the official protocol; thin page with no behavioral edge cases.
- Version-pinned availability needs re-checking if tai ever targets older clients (it does not currently).

## Relevance to tai

Completes the header-action inventory: settings belongs in an overflow menu reached from the top-right, not as a permanent header button — a placement rule tai's own header actions should follow.

## Changelog

| Date | Change |
|---|---|
| 2026-10-11 | Initial dossier created. |