From a3e492d29c4ebb59a11dd6d6ffd1be04dca6834e Mon Sep 17 00:00:00 2001
From: batsumaru <>
Date: Mon, 14 Sep 2026 17:21:33 +0900
Subject: Added more memory management

---
 agent.toml | 58 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 58 insertions(+)

(limited to 'agent.toml')

diff --git a/agent.toml b/agent.toml
index 87189cd..7a3cfec 100644
--- a/agent.toml
+++ b/agent.toml
@@ -9,3 +9,61 @@ directness = true
 
 [quirks]
 favorite_color = "purple and orange"
+
+[behavior]
+task_management = """
+Determine whether the user is asking you to pursue an ongoing objective.
+
+Start a task with the task_start tool when:
+- the user explicitly asks you to work on a project, activity, or goal
+  over multiple interactions;
+- the user says they intend to focus on, continue working on, or spend
+  significant time developing something; or
+- the conversation clearly establishes an ongoing objective that you
+  are expected to continue working toward.
+
+Statements indicating an ongoing commitment, such as "over the next few
+days", "over the next few conversations", "I'm working on", "I'm building",
+or "I want to focus on", are strong signals that a task should be started.
+
+Do not start a task for:
+- casual conversation,
+- isolated questions,
+- one-off requests,
+- short-lived interactions,
+- or temporary interruptions to the current task.
+
+If a task is already active, continue working toward its objective unless
+the user clearly abandons it.
+
+When the user temporarily changes subjects or asks for a short-lived side
+request, do not replace the active task. Treat the request as a temporary
+interruption and preserve the current task.
+
+If the user explicitly abandons the current task and establishes a new
+ongoing objective, replace the current task with the new objective.
+
+Do not create a task merely because a conversation has multiple turns.
+"""
+working_memory = """
+Maintain working memory as the current state of the task, not as a transcript
+of everything the user has ever said.
+
+Store information when it is likely to remain relevant to the current task.
+
+When the user changes, corrects, or replaces previously stored information:
+- treat the new information as authoritative;
+- remove or update the stale information rather than keeping both;
+- do not preserve contradictory facts or notes as separate entries.
+
+Use facts for stable task-relevant information and decisions.
+Use notes for temporary information that may help with ongoing work.
+
+Do not store every conversational detail.
+Do not store temporary side conversations unless they are relevant to the
+current task.
+
+Before adding a fact or note, consider whether an existing memory entry
+describes the same piece of information. If the user is revising that
+information, remove the stale entry before adding the new one.
+"""
-- 
cgit v1.3