mirror of
https://github.com/VibedByKaKi/t3-code-android-nightly.git
synced 2026-10-09 11:51:15 +02:00
Co-authored-by: maria-rcks <maria@kuuro.net> Co-authored-by: Bilal Bakr <62337003+Bil0000@users.noreply.github.com> Co-authored-by: shivam <91240327+shivamhwp@users.noreply.github.com> Co-authored-by: Vitalii Yehorov <vitalyiegorov@gmail.com> Co-authored-by: Jake Leventhal <jakeleventhal@me.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: Alex Southwell <saphid@gmail.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Nicholas Wasmiller <derped@mineperial.com> Co-authored-by: PB <poilmb@gmail.com> Co-authored-by: Exotic <118054752+extoci@users.noreply.github.com> Co-authored-by: Yash Singh <saiansh2525@gmail.com> Co-authored-by: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com> Co-authored-by: Theo Browne <me@t3.gg> Co-authored-by: Gabriel De Andrade <30420087+gabrielelpidio@users.noreply.github.com> Co-authored-by: Dara Adedeji <76637177+SunkenInTime@users.noreply.github.com> Co-authored-by: scratchyone <scratchywon@gmail.com> Co-authored-by: Dominic Roy <dominic@sdko.org> Co-authored-by: chukfinley <chuk@chuk.dev> Co-authored-by: Primož Ajdišek <bigpod@bigpod.si> Co-authored-by: benthecarman <benthecarman@live.com> Co-authored-by: NaveDanan <nave0712@gmail.com> Co-authored-by: aaditagrawal <103925638+aaditagrawal@users.noreply.github.com> Co-authored-by: Aditya Garud <153842990+yashranaway@users.noreply.github.com> Co-authored-by: Nick Anisimov <n.anisimov.23@gmail.com> Co-authored-by: MacKinley Smith <smithmackinley@gmail.com> Co-authored-by: Yordis Prieto <yordis.prieto@gmail.com> Co-authored-by: t3-code[bot] <269035359+t3-code[bot]@users.noreply.github.com> Co-authored-by: AKolenda <akole779@mtroyal.ca> Co-authored-by: Guillermo Casanova <75276669+Gigioxx@users.noreply.github.com> Co-authored-by: Otavio Salvador <otavio@ossystems.com.br> Co-authored-by: Shirish Pothi <183252392+shirishpothi@users.noreply.github.com> Co-authored-by: Ishaan Kothari <ishaanko.mail@gmail.com> Co-authored-by: Bob Fowler <bob@rjf.ca> Co-authored-by: Anton Bezdenezhnykh <gamer392@yandex.ru> Co-authored-by: ValeraZSD <48602572+ValeraZSD@users.noreply.github.com> Co-authored-by: Ephraim <ephraim39hr14m@gmail.com> Co-authored-by: Ryan Ilano <ryanilano@users.noreply.github.com> Co-authored-by: Alex <me@pixp.cc> Co-authored-by: maco <gosarmarcel7@gmail.com> Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Tristan Knight <admin@snappeh.com> Co-authored-by: PR Batch Tester <agent@local.test> Co-authored-by: oliver <97427849+flamboh@users.noreply.github.com> Co-authored-by: kamkm <99585688+Kamkmgamer@users.noreply.github.com> Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
95 lines
4.2 KiB
Markdown
95 lines
4.2 KiB
Markdown
# Appearance and themes
|
|
|
|
On web and desktop, open **Settings → Appearance** to choose a theme and follow the system
|
|
appearance or stay in light or dark mode. To use different themes for light and dark mode, select
|
|
the corresponding preview within each theme. Appearance preferences are saved separately on each
|
|
device or browser.
|
|
|
|
On web and desktop, use **Change theme** in the command palette to select a theme without leaving chat.
|
|
Press **Cmd+Option+A** on macOS or **Ctrl+Alt+A** on Windows/Linux to open the theme picker directly.
|
|
Use **Change appearance** in the command palette to choose System, Light, or Dark independently of
|
|
the theme. **Cmd+Option+Shift+A** on macOS or **Ctrl+Alt+Shift+A** on Windows/Linux cycles through
|
|
those modes. Customize these shortcuts under **Settings → Keybindings**.
|
|
|
|
On mobile, open **Settings → Appearance**. Mobile has its own themes and text,
|
|
code, and terminal preferences. It does not follow environment themes or defaults.
|
|
|
|
On Android 12 or newer, choose the **Material You** theme in Appearance to use colors from
|
|
your wallpaper. Selecting another theme replaces those colors. Like other themes, Material You
|
|
can be selected separately for light and dark appearances.
|
|
Android uses **Material You Layout** by default unless you have turned it off in Appearance.
|
|
It changes shapes, spacing, and controls independently
|
|
of the selected theme.
|
|
|
|
## Composer context
|
|
|
|
Git-backed projects show branch and worktree controls below the composer while you create a thread.
|
|
The controls retreat as the composer docks after you send the first message.
|
|
|
|
Turn on **Composer context** to keep those controls visible after the thread starts. This preference
|
|
applies to the web and desktop clients.
|
|
|
|
## Motion
|
|
|
|
The main sidebar, right panel, and terminal drawer open and close immediately by default. Move the
|
|
**Panel animations** slider above 0 ms to add motion, up to 400 ms, unless reduced motion is enabled
|
|
in your operating system. Moving between threads always snaps to the selected thread's panel state
|
|
without replaying its transitions.
|
|
|
|
## Custom themes
|
|
|
|
On web and desktop, choose **Create theme** to adjust a palette, or import a T3 Code or VS Code
|
|
theme. The theme editor's color picker lets you select an area of the app to find the color to
|
|
change. Export your theme as JSON to share it.
|
|
|
|
## Environment themes
|
|
|
|
Environment themes and defaults come from the server serving your web app or the desktop app's
|
|
main local environment. app.t3.codes and additional connections do not use them.
|
|
|
|
Select a published theme in **Settings → Appearance** to follow its palette as the server updates
|
|
it. **Duplicate** makes an independent copy you can edit. A saved custom theme with the same ID
|
|
takes precedence. If the server stops publishing the selected theme, T3 Code falls back to its
|
|
standard theme.
|
|
|
|
Run this on the server to set a default and switch connected clients to it:
|
|
|
|
```bash
|
|
t3 theme set nightfall
|
|
```
|
|
|
|
Clients that are offline apply it when they reconnect. Each client applies the setting once;
|
|
choosing another theme afterward sticks until the next `t3 theme set`. Run the command again to
|
|
reapply it, even if the name is unchanged.
|
|
|
|
`t3 theme clear` removes the default without changing anyone's current theme. `t3 theme show` lists
|
|
the default and published themes.
|
|
|
|
### Publish a theme
|
|
|
|
Save a theme exported from T3 Code into `~/.t3/userdata/themes/` on the server, or the `themes`
|
|
directory under your custom state directory. The filename supplies the theme ID: `nightfall.json`
|
|
can be selected with `t3 theme set nightfall`. Keep the filename stable when updating its colors.
|
|
Do not use `system`, `light`, `dark`, or a built-in theme's ID.
|
|
|
|
For an integration that generates a palette, this shorter format also works:
|
|
|
|
```json
|
|
{
|
|
"name": "Nightfall",
|
|
"appearance": "dark",
|
|
"canvas": "#1a1b26",
|
|
"accent": "#7aa2f7",
|
|
"colors": {
|
|
"terminalSelection": "#292e42",
|
|
"error": "#f7768e"
|
|
}
|
|
}
|
|
```
|
|
|
|
Set `appearance` to `light` or `dark` and supply hex colors for `canvas` and `accent`. T3 Code
|
|
generates the rest. The optional `colors` overrides use the names in the theme editor's advanced
|
|
view.
|
|
|
|
Write updates to a temporary file and rename it into place so clients never read a partial theme.
|
|
Invalid files are not published.
|