Skip to content

fix: add MESSAGE_TTL_SECONDS=0 to prevent message expiry#350

Open
zts212653 wants to merge 1 commit intomainfrom
fix/env-message-ttl
Open

fix: add MESSAGE_TTL_SECONDS=0 to prevent message expiry#350
zts212653 wants to merge 1 commit intomainfrom
fix/env-message-ttl

Conversation

@zts212653
Copy link
Copy Markdown
Owner

Summary

  • Add MESSAGE_TTL_SECONDS=0 to .env.example so users get permanent message storage by default
  • Default Redis message TTL is 7 days — many users report messages "disappearing" because of this silent expiry
  • Users who copy .env.example will now get the recommended setting automatically

Context

Multiple community reports of "Redis messages lost" — root cause is the 7-day default TTL in RedisMessageStore. This is a documentation/config fix; code already supports MESSAGE_TTL_SECONDS=0 correctly (maps to ttlSeconds = null = no expiry).

Closes #343 (partial — auto-summary removal will come in next sync)

Test plan

  • Copy fresh .env.example.env, start with Redis → verify messages persist beyond 7 days
  • Existing users: add MESSAGE_TTL_SECONDS=0 to .env → verify no regression

[宪宪/Opus-46🐾]

🤖 Generated with Claude Code

Default Redis message TTL is 7 days — many users report "messages disappeared"
because they don't know about this silent expiry. Setting MESSAGE_TTL_SECONDS=0
in the example ensures users who copy .env.example get permanent storage.

Closes #343

[宪宪/Opus-46🐾]

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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