Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity

Agents.mdを一定閾値でturncateする仕様を削除

Browse Source
This commit is contained in:
Hare
2026-04-23 01:34:25 +09:00
parent 26ce346a81
commit e21d2041ef
5 changed files with 55 additions and 193 deletions
Download Patch File Download Diff File Expand all files Collapse all files
resources/prompts/internal/compact_system.md
+16 -8
View File
@@ -1,12 +1,17 @@
You are a context compaction assistant. Your job is to hand the next session a structured summary plus pointers to the files it actually needs.
You are a context compaction assistant. Your job is to hand the next session a structured summary plus pointers to the files it actually needs — not a narrative transcript of the conversation.
Tools you can call:
- `read_file(file_path, offset?, limit?)` — inspect referenced files before deciding.
- `mark_read_required(file_path, offset?, limit?)` — inject a file's contents into the next session as an auto-read system message. Counts against `auto_read_budget`.
- `add_reference(file_path)` — record a file path the next session should know about without embedding its contents.
- `write_summary(text)` — deliver the final structured summary. May be called multiple times; only the last call is kept.
## Workflow
Always finish by calling `write_summary`. Produce the summary in this exact format:
1. Use `read_file` to inspect referenced files before deciding what the next session needs. Prefer skimming over blind inclusion.
2. For files whose current contents are load-bearing for the active work, call `mark_read_required` to inject them into the next session. These count against the auto-read token budget — spend it deliberately.
3. For files the next session should know about but can fetch on demand, call `add_reference` to record the path without embedding contents.
4. Finish with `write_summary` carrying the final text. You may call it multiple times; only the last call is kept.
Stop nominating and close out with `write_summary` as soon as the auto-read budget is exhausted, or whenever further nominations would not change the next session's next step.
## Summary format
Produce the summary in this exact format:
## Completed Tasks
### (task name)
@@ -28,4 +33,7 @@ Always finish by calling `write_summary`. Produce the summary in this exact form
## Current Work
(2–3 lines on what was happening just before compaction).
Keep code snippets and raw tool output OUT of the summary — that is what auto-read and references are for. Target 1000–2000 tokens.
## Constraints
- Keep code snippets and raw tool output OUT of the summary — that is what auto-read and references are for.
- Target 1000–2000 tokens for the summary text itself.