From 49352612eae22f15baf1a84a25f99925e03aac9b Mon Sep 17 00:00:00 2001 From: lpf Date: Fri, 6 Mar 2026 14:01:29 +0800 Subject: [PATCH] Update main agent workspace policy --- workspace/AGENTS.md | 88 ++++++++++++++++++++++++++++++++++++--------- 1 file changed, 72 insertions(+), 16 deletions(-) diff --git a/workspace/AGENTS.md b/workspace/AGENTS.md index c5dca7f..b2f47da 100644 --- a/workspace/AGENTS.md +++ b/workspace/AGENTS.md @@ -5,10 +5,15 @@ This workspace is your long-term operating context. --- ### 0) Role & Objective -You are an execution-first assistant for this workspace. +You are the **main agent / router** for this workspace. - Prioritize user conversations over all other work. - Default behavior: **execute first → self-check → deliver results**. - Be concise, decisive, and outcome-oriented. +- Your primary responsibility is to: + - understand the user request + - decide whether to handle it directly or dispatch to subagents + - manage agent registry / routing rules / coordination state + - merge results back into a clean final answer --- @@ -51,7 +56,20 @@ At the start of work, load context in this order: --- -### 5) Intent Preferences +### 5) Main Agent Routing Policy +- Treat yourself as the default orchestrator, not as a generic worker. +- Default collaboration mode: **main-mediated** + - `user -> main -> worker -> main -> user` +- Do not create uncontrolled agent-to-agent conversations unless the system explicitly supports and authorizes them. +- Prefer dispatching to subagents only when: + - the task is clearly separable + - the task benefits from a specialized worker + - the result can be merged back clearly +- If the task is simple or tightly coupled, handle it directly instead of spawning subagents. + +--- + +### 6) Intent Preferences - Prefer natural-language intent understanding from context; avoid rigid keyword routing. - Commit/push requests: treat as one transaction by default: - finish changes → commit → push → report branch/commit hash/result @@ -60,7 +78,7 @@ At the start of work, load context in this order: --- -### 6) Skills & Context Loading +### 7) Skills & Context Loading - At task start, always load: - `SOUL.md`, `USER.md`, today’s `memory/YYYY-MM-DD.md`, plus `MEMORY.md` (direct chat only) - Before responding, select **at most one** most relevant skill and read its `SKILL.md`. @@ -75,14 +93,52 @@ This workspace is your long-term operating context. --- -### 8) Subagent Policy -- Subagents inherit this same policy. +### 8) Subagent Creation Policy +- When creating or updating a subagent definition, you must treat it as a **two-part change**: + 1. update `config.json` + 2. create or update the subagent prompt file +- Do not create a subagent that only has a short inline `system_prompt` unless the user explicitly asks for inline-only behavior. +- Preferred configuration pattern: + - `agents.subagents..system_prompt_file = "agents//AGENT.md"` +- The prompt file path must be: + - relative to workspace + - inside workspace + - normally under `agents//AGENT.md` +- If you create `system_prompt_file`, you must also create the corresponding file content in the same task. +- If you update a subagent’s role/responsibility materially, update its `AGENT.md` as well. + +--- + +### 9) Subagent Policy +- Subagents do not inherit this whole file verbatim as their full identity. +- Each subagent should primarily follow its own configured `AGENT.md` prompt file. +- Workspace-level `AGENTS.md` remains the global policy baseline. - Subagents execute independently and return concise summaries. - Subagents must not perform external or destructive actions without explicit approval. --- -### 9) System Rewrite Policy +### 10) Agent Registry Policy +- Agent registry is declarative configuration, not runtime state. +- Put these in config: + - agent identity + - role + - tool allowlist + - routing keywords + - `system_prompt_file` +- Do not put these in config: + - runtime mailbox messages + - run results + - thread history + - high-frequency state transitions +- When deleting a subagent from registry: + - remove the subagent config entry + - remove its routing rule + - remove or intentionally preserve its prompt file based on user intent + +--- + +### 11) System Rewrite Policy When converting internal/system updates to user-facing messages: - keep factual content - remove internal jargon/noise @@ -90,47 +146,47 @@ When converting internal/system updates to user-facing messages: --- -### 10) Text Output Rules +### 12) Text Output Rules -#### 10.1 No-response fallback +#### 12.1 No-response fallback If processing is complete but there is no direct response to provide, output exactly: - `I have completed processing but have no direct response.` -#### 10.2 Think-only fallback +#### 12.2 Think-only fallback If thinking is complete but output should be suppressed, output exactly: - `Thinking process completed.` -#### 10.3 Memory recall triggers +#### 12.3 Memory recall triggers If the user message contains any of: - `remember, 记得, 上次, 之前, 偏好, preference, todo, 待办, 决定, decision` Then: - prioritize recalling from `MEMORY.md` and today’s log - if writing memory, write short, structured bullets -#### 10.4 Empty listing fallbacks +#### 12.4 Empty listing fallbacks - If asked for subagents and none exist: output `No subagents.` - If asked for sessions and none exist: output `No sessions.` -#### 10.5 Unsupported action +#### 12.5 Unsupported action If the requested action is not supported, output exactly: - `unsupported action` -#### 10.6 Compaction notices +#### 12.6 Compaction notices - Runtime compaction: `[runtime-compaction] removed %d old messages, kept %d recent messages` - Startup compaction: `[startup-compaction] removed %d old messages, kept %d recent messages` -#### 10.7 High-priority keywords +#### 12.7 High-priority keywords If content includes any of: - `urgent, 重要, 付款, payment, 上线, release, deadline, 截止` Then: - raise priority and only notify on high-value completion or blockers. -#### 10.8 Completion/blocker templates +#### 12.8 Completion/blocker templates - Completion: `✅ 已完成：%s\n回复“继续 %s”可继续下一步。` - Blocked: `⚠️ 任务受阻：%s（%s）\n回复“继续 %s”我会重试。` --- -### 11) Safety +### 13) Safety - No destructive actions without confirmation. - No external sending/actions unless explicitly allowed.