Skip to content

Chat memory on the phone, compress long chats at 70% by default - #231

Merged
danielehrhardt merged 2 commits into
mainfrom
feat/compress-mobile
Oct 23, 2026
Merged

danielehrhardt merged 2 commits into
mainfrom
feat/compress-mobile

Conversation

@danielehrhardt

Copy link
Copy Markdown
Contributor

Follow-up to #224: chat memory and Compress on the phone, and long chats now compress at 70% by default.

What changes

  • Phone app
    • A memory ring next to the model in the composer. It turns amber or red near the auto point and shows the percent.
    • Tapping it opens a Chat memory sheet: tokens of the window, a bar with the auto point, Compress now (or "after this step" while it works), and a link to the setting.
    • A "This chat is getting long" strip above the composer with Compress and Hide.
    • The compressed divider in the thread ("Chat compressed · 422k → 9k"); the duplicate /compact card is hidden.
    • Settings → AI & Claude → Long chats: compress at 40–80%, when nearly full, or never.
  • Default 70% instead of 50%, still on by default. Migration 101 moves a saved runner section that still has 50 to 70; settings are saved a whole section at a time, so v0.2.24 installs may have it stored.
  • contextGauge / tokensLabel moved to @godmode/shared, used by both apps.

Checks

  • pnpm -r typecheck clean; phone app tsc --noEmit clean.
  • Core: slash-commands (env now 70), mcp, remote-mirror pass.
  • Migration SQL checked on a sample settings table: only runner with 50 changes.

- Phone app: memory ring next to the model opens a Chat memory sheet (tokens, share, auto point, Compress), a strip once the chat gets long, the compressed divider in the thread, and Long chats in Settings > AI & Claude
- Auto-compress default 70% (was 50%); migration 101 moves a runner section saved with 50 to 70
- The gauge (share, tone, auto point) and token labels live in shared for both apps
@danielehrhardt
danielehrhardt merged commit 3b6c312 into main Oct 23, 2026
7 of 8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant