Keep conversations, so a useful answer outlives the tab it was asked in
This commit is contained in:
@@ -1645,6 +1645,20 @@
|
||||
AI_MEMORY_FILE="$DATA_DIR/ai_memory.md"
|
||||
AI_MEMORY_MAX_CHARS=4000 # ~1000 tokens — truncated with a notice if exceeded
|
||||
|
||||
# ━━━ AI Stored Conversations ━━━
|
||||
# How many past conversations the AI tab and the Monitor tab's AI row keep. One JSON file per
|
||||
# conversation under DATA_DIR/ai_chats, saved automatically when a turn completes; the oldest
|
||||
# drop off once the count is exceeded.
|
||||
#
|
||||
# A cap rather than a retention age. These are read by picking one out of a short list, and a
|
||||
# list you have to scroll is a list you stop using — the useful window is the handful of things
|
||||
# you were recently working on, which is a count, not a date.
|
||||
#
|
||||
# Not indexed and never retrieved into a prompt on their own. A stored chat only re-enters the
|
||||
# model's context when the operator explicitly reopens it, and it is re-validated per message on
|
||||
# the way in, exactly as live history is.
|
||||
AI_CHAT_HISTORY_MAX=10 # conversations kept — clamped to 1-50
|
||||
|
||||
# ━━━ AI Token Accounting ━━━
|
||||
# One row per completed turn, appended by whichever path ran it — the WebGUI worker and the
|
||||
# ai_query.sh CLI both write here, so the totals are not silently the tab's alone. Format is
|
||||
|
||||
Reference in New Issue
Block a user