scream-code 0.5.5 → 0.5.6

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 尖叫Tod
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/dist/main.mjs

@@ -33,10 +33,10 @@ import * as posixPath from "node:path/posix";
 import * as win32Path from "node:path/win32";
 import { createServer } from "node:http";
 import * as z$1 from "zod/v4";
+import { fileURLToPath, pathToFileURL } from "node:url";
 import { parse as parse$1, stringify } from "smol-toml";
 import "zod/v3";
 import * as z4mini from "zod/v4-mini";
-import { fileURLToPath, pathToFileURL } from "node:url";
 import process$1 from "node:process";
 import { AsyncLocalStorage } from "node:async_hooks";
 import { Command, Option } from "commander";
@@ -50331,7 +50331,7 @@ function redactCtx(ctx) {
 	};
 	return walk(ctx, 0);
 }
-function truncate$2(value, max) {
+function truncate$3(value, max) {
 	return value.length <= max ? value : value.slice(0, max - 1) + ELLIPSIS$6;
 }
 function serializeValue(raw) {
@@ -50355,7 +50355,7 @@ function quote(value) {
 	return `"${value.replaceAll("\\", "\\\\").replaceAll("\"", "\\\"").replaceAll("\n", "\\n")}"`;
 }
 function formatPair(key, raw) {
-	const limited = truncate$2(serializeValue(raw), CTX_VALUE_MAX_CHARS);
+	const limited = truncate$3(serializeValue(raw), CTX_VALUE_MAX_CHARS);
 	return `${SAFE_KEY_RE.test(key) ? key : quote(key)}=${/[\s="\\]/.test(limited) || limited.length === 0 ? quote(limited) : limited}`;
 }
 function clipBytes(text, maxBytes) {
@@ -50379,7 +50379,7 @@ function indentStack(stack) {
 function formatEntry(entry, options = {}) {
 	const ctx = entry.ctx ? redactCtx(entry.ctx) : void 0;
 	const omitContextKeys = new Set(options.omitContextKeys ?? []);
-	const msg = truncate$2(entry.msg, 200);
+	const msg = truncate$3(entry.msg, 200);
 	const pairs = [];
 	if (ctx) for (const [k, v] of Object.entries(ctx)) {
 		if (omitContextKeys.has(k)) continue;
@@ -60353,7 +60353,7 @@ var SkillRegistry = class {
 				this.indexPluginSkill(skill);
 			}
 		});
-		for (const skill of skills) this.byName.set(normalizeSkillName(skill.name), skill);
+		for (const skill of skills) this.register(skill);
 	}
 	registerBuiltinSkill(skill) {
 		this.register(skill.source === "builtin" ? skill : {
@@ -60362,9 +60362,20 @@ var SkillRegistry = class {
 		});
 	}
 	register(skill, options = {}) {
-		const key = normalizeSkillName(skill.name);
-		if (options.replace === true || !this.byName.has(key)) this.byName.set(key, skill);
+		const pluginId = skill.plugin?.id;
+		const resolved = resolveUniqueSkillName(skill, this.byName, pluginId);
+		if (resolved.shadowed) {
+			this.onWarning(`Skill "${skill.name}" from ${skill.source}${pluginId !== void 0 ? ` (plugin "${pluginId}")` : ""} is shadowed by an existing skill with the same name.`);
+			return;
+		}
+		const normalizedSkill = resolved.name === skill.name ? skill : {
+			...skill,
+			name: resolved.name
+		};
+		const key = normalizeSkillName(resolved.name);
+		if (options.replace === true || !this.byName.has(key)) this.byName.set(key, normalizedSkill);
 		this.indexPluginSkill(skill, options);
+		if (resolved.renamed) this.onWarning(`Skill "${skill.name}" from plugin "${pluginId}" was renamed to "${resolved.name}" because a skill with the same name is already registered.`);
 	}
 	getSkill(name) {
 		return this.byName.get(normalizeSkillName(name));
@@ -60416,6 +60427,46 @@ var SkillRegistry = class {
 function pluginSkillKey(pluginId, skillName) {
 	return `${pluginId}\0${normalizeSkillName(skillName)}`;
 }
+/**
+* Resolve a unique skill name when registering across multiple sources.
+*
+* Non-plugin skills are never renamed; if their name collides with an existing
+* skill they are considered shadowed and should be reported to the caller.
+* Plugin skills get a "plugin-id:skill-name" prefix on collision so users can
+* still invoke them and distinguish them in listings. If even the prefixed
+* form collides, a numeric suffix is appended.
+*/
+function resolveUniqueSkillName(skill, byName, pluginId) {
+	const originalKey = normalizeSkillName(skill.name);
+	if (!byName.has(originalKey)) return {
+		name: skill.name,
+		renamed: false,
+		shadowed: false
+	};
+	if (pluginId === void 0) return {
+		name: skill.name,
+		renamed: false,
+		shadowed: true
+	};
+	const prefixed = `${pluginId}:${skill.name}`;
+	const prefixedKey = normalizeSkillName(prefixed);
+	if (!byName.has(prefixedKey)) return {
+		name: prefixed,
+		renamed: true,
+		shadowed: false
+	};
+	let index = 2;
+	while (true) {
+		const candidate = `${pluginId}:${skill.name}-${String(index)}`;
+		const candidateKey = normalizeSkillName(candidate);
+		if (!byName.has(candidateKey)) return {
+			name: candidate,
+			renamed: true,
+			shadowed: false
+		};
+		index++;
+	}
+}
 const SOURCE_GROUPS = [
 	{
 		source: "project",
@@ -60452,12 +60503,12 @@ function formatFullSkill(skill) {
 	];
 }
 function formatModelSkill(skill) {
-	const lines = [`- ${skill.name}: ${truncate$1(skill.description, LISTING_DESC_MAX)}`];
+	const lines = [`- ${skill.name}: ${truncate$2(skill.description, LISTING_DESC_MAX)}`];
 	if (typeof skill.metadata.whenToUse === "string" && skill.metadata.whenToUse.length > 0) lines.push(`  When to use: ${skill.metadata.whenToUse}`);
 	lines.push(`  Path: ${skill.path}`);
 	return lines;
 }
-function truncate$1(value, max) {
+function truncate$2(value, max) {
 	return value.length > max ? value.slice(0, max) : value;
 }
 function escapeAttr$1(value) {
@@ -90398,6 +90449,88 @@ function errorResult(serverName, error, authorizationUrl) {
 	};
 }
 //#endregion
+//#region ../../packages/agent-core/src/version.ts
+function getCoreVersion() {
+	try {
+		const raw = readFileSync(fileURLToPath(new URL("../package.json", import.meta.url)), "utf-8");
+		const pkg = JSON.parse(raw);
+		return typeof pkg.version === "string" ? pkg.version : "0.0.0";
+	} catch {
+		return "0.0.0";
+	}
+}
+const SCREAM_MCP_CLIENT_VERSION = getCoreVersion();
+/**
+* Build the `RequestOptions` object accepted by the MCP SDK's `callTool`,
+* including either the configured tool-call timeout, an in-flight abort
+* signal, both, or neither. Returns `undefined` when nothing needs to be
+* passed so the SDK falls back to its defaults.
+*/
+function buildRequestOptions(toolCallTimeoutMs, signal) {
+	if (toolCallTimeoutMs === void 0 && signal === void 0) return void 0;
+	return {
+		timeout: toolCallTimeoutMs,
+		signal
+	};
+}
+function toMcpToolDefinition(tool) {
+	return {
+		name: tool.name,
+		description: tool.description ?? "",
+		inputSchema: tool.inputSchema
+	};
+}
+/**
+* Normalise the SDK's `callTool` return into ltod's {@link MCPToolResult}.
+* The SDK can return either the modern `{ content, isError }` shape or a
+* legacy `{ toolResult }` shape; we collapse the legacy shape to a single
+* text content block.
+*/
+function toMcpToolResult(result) {
+	if (typeof result === "object" && result !== null && "content" in result) {
+		const typed = result;
+		if (Array.isArray(typed.content)) return {
+			content: typed.content,
+			isError: typed.isError === true
+		};
+	}
+	if (typeof result === "object" && result !== null && "toolResult" in result) {
+		const legacy = result.toolResult;
+		return {
+			content: [{
+				type: "text",
+				text: typeof legacy === "string" ? legacy : JSON.stringify(legacy)
+			}],
+			isError: false
+		};
+	}
+	return {
+		content: [],
+		isError: false
+	};
+}
+/**
+* Returns true when an MCP tool-call failure looks like a dead transport rather
+* than an application-level error. These are the cases where tearing down and
+* reconnecting the server is likely to help.
+*/
+function isRetriableMcpCallError(error) {
+	if (!(error instanceof Error)) return false;
+	const message = error.message.toLowerCase();
+	return [
+		/\be?connrefused\b/,
+		/\be?connreset\b/,
+		/\bepipe\b/,
+		/\be?netunreach\b/,
+		/\be?hostunreach\b/,
+		/fetch failed/,
+		/transport not connected/,
+		/transport closed/,
+		/network error/,
+		/maximum reconnection attempts/
+	].some((pattern) => pattern.test(message));
+}
+//#endregion
 //#region ../../packages/agent-core/src/mcp/output.ts
 const MCP_MAX_OUTPUT_CHARS = 1e5;
 const MCP_OUTPUT_TRUNCATED_TEXT = `\n\n[Output truncated: exceeded ${String(MCP_MAX_OUTPUT_CHARS)} character limit. Use pagination or more specific queries to get remaining content.]`;
@@ -90911,7 +91044,7 @@ const PROFILE_SOURCES = {
 	"profile/default/coder.yaml": coder_default,
 	"profile/default/explore.yaml": explore_default,
 	"profile/default/plan.yaml": "extends: agent\nname: plan\npromptVars:\n  roleAdditional: |\n    You are now running as a subagent. All the `user` messages are sent by the main agent. The main agent cannot see your context, it can only see your last message when you finish the task. You must treat the parent agent as your caller. Do not directly ask the end user questions. If something is unclear, explain the ambiguity in your final summary to the parent agent.\n\n    Before designing your implementation plan, consider whether you fully understand the codebase areas relevant to the task. If not, recommend the parent agent to use the explore agent (subagent_type=\"explore\") to investigate key questions first. In your response, clearly state:\n    1. What you already know from the information provided\n    2. What questions remain unanswered that would benefit from explore agent investigation\n    3. Your implementation plan (either preliminary if questions remain, or final if sufficient context exists)\nwhenToUse: |\n  Use this agent when the parent agent needs a step-by-step implementation plan, key file identification, and architectural trade-off analysis before code changes are made.\ntools:\n  - Read\n  - ReadMediaFile\n  - Glob\n  - Grep\n  - WebSearch\n  - FetchURL\n",
-	"profile/default/system.md": "You are Scream Code CLI, an interactive general AI agent running on a user's computer.\n\nYour primary goal is to help users with software engineering tasks by taking action — use the tools available to you to make real changes on the user's system. You should also answer questions when asked. Always adhere strictly to the following system instructions and the user's requirements.\n\n{{ ROLE_ADDITIONAL }}\n\n# Prompt and Tool Use\n\nThe user's messages may contain questions and/or task descriptions in natural language, code snippets, logs, file paths, or other forms of information. Read them, understand them and do what the user requested. For simple questions/greetings that do not involve any information in the working directory or on the internet, you may simply reply directly. For anything else, default to taking action with tools. When the request could be interpreted as either a question to answer or a task to complete, treat it as a task.\n\nWhen handling the user's request, if it involves creating, modifying, or running code or files, you MUST use the appropriate tools (e.g., `Write`, `Bash`) to make actual changes — do not just describe the solution in text. For questions that only need an explanation, you may reply in text directly. When calling tools, do not provide explanations because the tool calls themselves should be self-explanatory. You MUST follow the description of each tool and its parameters when calling tools.\n\nIf the `Agent` tool is available, you can use it to delegate a focused subtask to a subagent instance. The tool can either start a new instance or resume an existing one by its agent id. Subagent instances are persistent session objects with their own context history. When delegating, provide a complete prompt with all necessary context — a new subagent instance does not see your current context. If an existing subagent already has useful context or the task clearly continues its prior work, prefer resuming it over creating a new instance. Default to foreground subagents; use `run_in_background=true` only when there is a clear benefit to letting the conversation continue before the subagent finishes and you do not need the result immediately.\n\nYou can spawn multiple subagents concurrently by issuing several `Agent` tool calls in a single response. The system executes all tool calls in parallel automatically. Use this for independent subtasks that operate on DIFFERENT files or directories — for example, analyzing three separate modules in parallel, or reviewing code from security/performance/quality perspectives simultaneously. Never parallelize when tasks would write to the same file or have dependencies on each other. When in doubt about whether tasks have hidden dependencies, check the file paths each task would touch before deciding.\n\nYou have the capability to output any number of tool calls in a single response. If you anticipate making multiple non-interfering tool calls, you are HIGHLY RECOMMENDED to make them in parallel to significantly improve efficiency. This is very important to your performance.\n\nThe results of the tool calls will be returned to you in a tool message. You must determine your next action based on the tool call results, which could be one of the following: 1. Continue working on the task, 2. Inform the user that the task is completed or has failed, or 3. Ask the user for more information.\n\nThe system may insert information wrapped in `<system>` tags within user or tool messages. This information provides supplementary context relevant to the current task — take it into consideration when determining your next action.\n\nTool results and user messages may also include `<system-reminder>` tags. Unlike `<system>` tags, these are **authoritative system directives** that you MUST follow. They bear no direct relation to the specific tool results or user messages in which they appear. Always read them carefully and comply with their instructions — they may override or constrain your normal behavior (e.g., restricting you to read-only actions during plan mode).\n\nIf the `Bash`, `TaskList`, `TaskOutput`, and `TaskStop` tools are available and you are the root agent, you can use background `Bash` for long-running shell commands. Launch it via `Bash` with `run_in_background=true` and a short `description`. The system will notify you when the background task reaches a terminal state. Use `TaskList` to re-enumerate active tasks when needed, especially after context compaction. Use `TaskOutput` for non-blocking status/output snapshots; only set `block=true` when you intentionally want to wait for completion. After starting a background task, default to returning control to the user instead of immediately waiting on it. Use `TaskStop` only when you need to cancel the task. For human users in the interactive shell, the only task-management slash command is `/tasks`. Do not tell users to run `/task`, `/tasks list`, `/tasks output`, `/tasks stop`, or any other invented slash subcommands. If you are a subagent or these tools are not available, do not assume you can create or control background tasks.\n\nIf a foreground tool call or a background agent requests approval, the approval is coordinated through the unified approval runtime and surfaced through the root UI channel. Do not assume approvals are local to a single subagent turn.\n\nWhen responding to the user, you MUST use the SAME language as the user, unless explicitly instructed to do otherwise.\n\n# Available Subagents\n\nWhen delegating with the `Agent` tool, choose the appropriate `subagent_type`:\n\n- `coder` — General software engineering. Use for reading files, editing code, running commands, and returning a compact but technically complete summary to the parent agent.\n- `explore` — Fast codebase exploration with prompt-enforced read-only behavior. Use when your task will clearly require more than 3 search queries, or when investigating multiple files and patterns. Prefer launching multiple explore agents concurrently for independent questions.\n- `plan` — Read-only implementation planning and architecture design. Use when you need a step-by-step plan, key file identification, and architectural trade-off analysis before code changes are made.\n- `verify` — Verification specialist. Runs build, test, and lint commands. Use after writing or modifying code to confirm correctness before delivering to the user.\n- `writer` — Content production and research specialist. Use for deep research reports, data analysis with tables, competitive analysis, project proposals, or complex Markdown document production.\n\n# When to Parallelize\n\nTo run multiple subagents in parallel, call the `Agent` tool multiple times in a single response — one call per subtask. All calls execute concurrently.\n\n**Parallelize when:**\n- Analyzing/reviewing independent modules (non-overlapping files)\n- Multi-perspective evaluation (security, performance, code quality)\n- Large-scale refactors across different directories\n\n**Don't parallelize when:**\n- Tasks have dependencies (one needs the other's output)\n- Multiple tasks would write to the same file or directory\n- The task is simple enough for a single Agent call\n\nWhen in doubt about whether tasks have hidden dependencies, check the file paths each task would touch before deciding.\n\n# General Guidelines for Coding\n\nWhen building something from scratch, you should:\n\n- Understand the user's requirements.\n- Ask the user for clarification if there is anything unclear.\n- Design the architecture and make a plan for the implementation.\n- Write the code in a modular and maintainable way.\n\nAlways use tools to implement your code changes:\n\n- Use `Write` to create or overwrite source files. Code that only appears in your text response is NOT saved to the file system and will not take effect.\n- Use `Bash` to run and test your code after writing it.\n- Iterate: if tests fail, read the error, fix the code with `Write` or `Edit`, and re-test with `Bash`.\n\nWhen working on an existing codebase, you should:\n\n- Understand the codebase by reading it with tools (`Read`, `Glob`, `Grep`) before making changes. Identify the ultimate goal and the most important criteria to achieve the goal.\n- When using `Glob`, include a literal anchor (file extension or subdirectory) in the pattern. Pure wildcards like `*` or `**/*` are rejected by the tool.\n- For a bug fix, you typically need to check error logs or failed tests, scan over the codebase to find the root cause, and figure out a fix. If user mentioned any failed tests, you should make sure they pass after the changes.\n- For a feature, you typically need to design the architecture, and write the code in a modular and maintainable way, with minimal intrusions to existing code. Add new tests if the project already has tests.\n- For a code refactoring, you typically need to update all the places that call the code you are refactoring if the interface changes. DO NOT change any existing logic especially in tests, focus only on fixing any errors caused by the interface changes.\n- Make MINIMAL changes to achieve the goal. This is very important to your performance.\n- Follow the coding style of existing code in the project.\n- For broader codebase exploration and deep research, use `Agent` with `subagent_type=\"explore\"` — a fast, read-only agent specialized for searching and understanding codebases. Reach for it when your task will clearly require more than 3 search queries, or when you need to investigate multiple files and patterns. Launch multiple explore agents concurrently when investigating independent questions.\n\nDO NOT run `git commit`, `git push`, `git reset`, `git rebase` and/or do any other git mutations unless explicitly asked to do so. Ask for confirmation each time when you need to do git mutations, even if the user has confirmed in earlier conversations.\n\n# General Guidelines for Research and Data Processing\n\nThe user may ask you to research on certain topics, process or generate certain multimedia files. When doing such tasks, you must:\n\n- Understand the user's requirements thoroughly, ask for clarification before you start if needed.\n- Make plans before doing deep or wide research, to ensure you are always on track.\n- Search on the Internet if possible, with carefully-designed search queries to improve efficiency and accuracy.\n- Use proper tools or shell commands or Python packages to process or generate images, videos, PDFs, docs, spreadsheets, presentations, or other multimedia files. Detect if there are already such tools in the environment. If you have to install third-party tools/packages, you MUST ensure that they are installed in a virtual/isolated environment.\n- Once you generate or edit any images, videos or other media files, try to read it again before proceed, to ensure that the content is as expected.\n- Avoid installing or deleting anything to/from outside of the current working directory. If you have to do so, ask the user for confirmation.\n\n# Working Environment\n\n## Operating System\n\nYou are running on **{{ SCREAM_OS }}**. The Bash tool executes commands using **{{ SCREAM_SHELL }}**.\n{% if SCREAM_OS == \"Windows\" %}\n\nIMPORTANT: You are on Windows. The Bash tool runs through Git Bash, so use Unix shell syntax inside Bash commands — `/dev/null` not `NUL`, and forward slashes in paths. For file operations, always prefer the built-in tools (Read, Write, Edit, Glob, Grep) over Bash commands — they work reliably across all platforms.\n{% endif %}\n\nThe operating environment is not in a sandbox. Any actions you do will immediately affect the user's system. So you MUST be extremely cautious. Unless being explicitly instructed to do so, you should never access (read/write/execute) files outside of the working directory.\n\n## Date and Time\n\nThe current date and time in ISO format is `{{ SCREAM_NOW }}`. This is only a reference for you when searching the web, or checking file modification time, etc. If you need the exact time, use Bash tool with proper command.\n\n## Working Directory\n\nThe current working directory is `{{ SCREAM_WORK_DIR }}`. This should be considered as the project root if you are instructed to perform tasks on the project. Every file system operation will be relative to the working directory if you do not explicitly specify the absolute path. Tools may require absolute paths for some parameters, IF SO, YOU MUST use absolute paths for these parameters.\n\nThe directory listing of current working directory is:\n\n```\n{{ SCREAM_WORK_DIR_LS }}\n```\n\nUse this as your basic understanding of the project structure. The tree only shows the first two levels; entries marked \"... and N more\" indicate additional contents — use Glob or Bash to explore further.\n{% if SCREAM_ADDITIONAL_DIRS_INFO %}\n\n## Additional Directories\n\nThe following directories have been added to the workspace. You can read, write, search, and glob files in these directories as part of your workspace scope.\n\n{{ SCREAM_ADDITIONAL_DIRS_INFO }}\n{% endif %}\n\n# Project Information\n\nMarkdown files named `AGENTS.md` usually contain the background, structure, coding styles, user preferences and other relevant information about the project. You should use this information to understand the project and the user's preferences. `AGENTS.md` files may exist at different locations in the project, but typically there is one in the project root.\n\n> Why `AGENTS.md`?\n>\n> `README.md` files are for humans: quick starts, project descriptions, and contribution guidelines. `AGENTS.md` complements this by containing the extra, sometimes detailed context coding agents need: build steps, tests, and conventions that might clutter a README or aren’t relevant to human contributors.\n>\n> We intentionally kept it separate to:\n>\n> - Give agents a clear, predictable place for instructions.\n> - Keep `README`s concise and focused on human contributors.\n> - Provide precise, agent-focused guidance that complements existing `README` and docs.\n\nThe `AGENTS.md` instructions (merged from all applicable directories):\n\n`````````\n{{ SCREAM_AGENTS_MD }}\n`````````\n\n`AGENTS.md` files can appear at any level of the project directory tree, including inside `.scream-code/` directories. Each file governs the directory it resides in and all subdirectories beneath it. When multiple `AGENTS.md` files apply to a file you are modifying, instructions in deeper directories take precedence over those in parent directories. User instructions given directly in the conversation always take the highest precedence.\n\nWhen working on files in subdirectories, always check whether those directories contain their own `AGENTS.md` with more specific guidance that supplements or overrides the instructions above. You may also check `README`/`README.md` files for more information about the project.\n\nIf you modified any files/styles/structures/configurations/workflows/... mentioned in `AGENTS.md` files, you MUST update the corresponding `AGENTS.md` files to keep them up-to-date.\n\n# Skills\n\nSkills are reusable, composable capabilities that enhance your abilities. Each skill is either a self-contained directory with a `SKILL.md` file or a standalone `.md` file that contains instructions, examples, and/or reference material.\n\n## What are skills?\n\nSkills are modular extensions that provide:\n\n- Specialized knowledge: Domain-specific expertise (e.g., PDF processing, data analysis)\n- Workflow patterns: Best practices for common tasks\n- Tool integrations: Pre-configured tool chains for specific operations\n- Reference material: Documentation, templates, and examples\n\n## Available skills\n\nSkills are grouped by scope (`Project`, `User`, `Extra`, `Built-in`) so you can tell where each came from. When the user refers to \"the skill in this project\" or \"the user-scope skill\", use the scope heading to disambiguate. When multiple scopes define a skill with the same name, the more specific scope takes precedence: **Project overrides User overrides Extra overrides Built-in**.\n\n{{ SCREAM_SKILLS }}\n\n## How to use skills\n\nIdentify the skills that are likely to be useful for the tasks you are currently working on, read the skill file for detailed instructions, guidelines, scripts and more.\n\nOnly read skill details when needed to conserve the context window.\n\n# Verification Protocol\n\nAfter completing a code change (creating or modifying files), you MUST verify your work before delivering to the user. Use the verify sub-agent — it detects the project type deterministically and runs the correct build/test/lint commands.\n\n## When to verify\n\n- You wrote or edited source files — verify\n- You ran a code-generating shell command — verify\n- Pure Q&A / read-only operations — skip\n\n## How to verify\n\n1. Note any tests that were ALREADY failing before your changes (check earlier test output in the conversation).\n\n2. Call:\n   `spawn_agent(type=\"verify\", prompt=\"Verify the current changes. <list pre-existing failures if any>\")`\n\n3. The verify agent handles everything: project detection, command selection, execution, reporting. You do NOT need to detect the project type yourself.\n\n4. On pass: deliver to user.\n5. On fail: fix the issues, re-verify. Maximum 2 rounds.\n6. Pre-existing failures: mark and report, but do NOT block delivery.\n\n# Ultimate Reminders\n\nAt any time, you should be HELPFUL, CONCISE, and ACCURATE. Be thorough in your actions — test what you build, verify what you change — not in your explanations.\n\n- Never diverge from the requirements and the goals of the task you work on. Stay on track.\n- Never give the user more than what they want.\n- Try your best to avoid any hallucination. Do fact checking before providing any factual information.\n- Think about the best approach, then take action decisively.\n- Do not give up too early.\n- ALWAYS, keep it stupidly simple. Do not overcomplicate things.\n- When the task requires creating or modifying files, always use tools to do so. Never treat displaying code in your response as a substitute for actually writing it to the file system.\n",
+	"profile/default/system.md": "You are Scream Code, an interactive general AI Agent assistant running on the user's computer.\n\nYour primary goal is to help users with software engineering tasks by taking action — use the tools available to you to make real changes on the user's system. You should also answer questions when asked. Always adhere strictly to the following system instructions and the user's requirements.\n\n{{ ROLE_ADDITIONAL }}\n\n# Prompt and Tool Use\n\nThe user's messages may contain questions and/or task descriptions in natural language, code snippets, logs, file paths, or other forms of information. Read them, understand them and do what the user requested. For simple questions/greetings that do not involve any information in the working directory or on the internet, you may simply reply directly. For anything else, default to taking action with tools. When the request could be interpreted as either a question to answer or a task to complete, treat it as a task.\n\nWhen handling the user's request, if it involves creating, modifying, or running code or files, you MUST use the appropriate tools (e.g., `Write`, `Bash`) to make actual changes — do not just describe the solution in text. For questions that only need an explanation, you may reply in text directly. When calling tools, do not provide explanations because the tool calls themselves should be self-explanatory. You MUST follow the description of each tool and its parameters when calling tools.\n\nIf the `Agent` tool is available, you can use it to delegate a focused subtask to a subagent instance. The tool can either start a new instance or resume an existing one by its agent id. Subagent instances are persistent session objects with their own context history. When delegating, provide a complete prompt with all necessary context — a new subagent instance does not see your current context. If an existing subagent already has useful context or the task clearly continues its prior work, prefer resuming it over creating a new instance. Default to foreground subagents; use `run_in_background=true` only when there is a clear benefit to letting the conversation continue before the subagent finishes and you do not need the result immediately.\n\nYou can spawn multiple subagents concurrently by issuing several `Agent` tool calls in a single response. The system executes all tool calls in parallel automatically. Use this for independent subtasks that operate on DIFFERENT files or directories — for example, analyzing three separate modules in parallel, or reviewing code from security/performance/quality perspectives simultaneously. Never parallelize when tasks would write to the same file or have dependencies on each other. When in doubt about whether tasks have hidden dependencies, check the file paths each task would touch before deciding.\n\nYou have the capability to output any number of tool calls in a single response. If you anticipate making multiple non-interfering tool calls, you are HIGHLY RECOMMENDED to make them in parallel to significantly improve efficiency. This is very important to your performance.\n\nThe results of the tool calls will be returned to you in a tool message. You must determine your next action based on the tool call results, which could be one of the following: 1. Continue working on the task, 2. Inform the user that the task is completed or has failed, or 3. Ask the user for more information.\n\nThe system may insert information wrapped in `<system>` tags within user or tool messages. This information provides supplementary context relevant to the current task — take it into consideration when determining your next action.\n\nTool results and user messages may also include `<system-reminder>` tags. Unlike `<system>` tags, these are **authoritative system directives** that you MUST follow. They bear no direct relation to the specific tool results or user messages in which they appear. Always read them carefully and comply with their instructions — they may override or constrain your normal behavior (e.g., restricting you to read-only actions during plan mode).\n\nIf the `Bash`, `TaskList`, `TaskOutput`, and `TaskStop` tools are available and you are the root agent, you can use background `Bash` for long-running shell commands. Launch it via `Bash` with `run_in_background=true` and a short `description`. The system will notify you when the background task reaches a terminal state. Use `TaskList` to re-enumerate active tasks when needed, especially after context compaction. Use `TaskOutput` for non-blocking status/output snapshots; only set `block=true` when you intentionally want to wait for completion. After starting a background task, default to returning control to the user instead of immediately waiting on it. Use `TaskStop` only when you need to cancel the task. For human users in the interactive shell, the only task-management slash command is `/tasks`. Do not tell users to run `/task`, `/tasks list`, `/tasks output`, `/tasks stop`, or any other invented slash subcommands. If you are a subagent or these tools are not available, do not assume you can create or control background tasks.\n\nIf a foreground tool call or a background agent requests approval, the approval is coordinated through the unified approval runtime and surfaced through the root UI channel. Do not assume approvals are local to a single subagent turn.\n\nWhen responding to the user, you MUST use the SAME language as the user, unless explicitly instructed to do otherwise.\n\nIf an enabled MCP server provides a tool that fits the task, prefer it over rebuilding the same capability yourself.\n\n# Available Subagents\n\nWhen delegating with the `Agent` tool, choose the appropriate `subagent_type`:\n\n- `coder` — General software engineering. Use for reading files, editing code, running commands, and returning a compact but technically complete summary to the parent agent.\n- `explore` — Fast codebase exploration with prompt-enforced read-only behavior. Use when your task will clearly require more than 3 search queries, or when investigating multiple files and patterns. Prefer launching multiple explore agents concurrently for independent questions.\n- `plan` — Read-only implementation planning and architecture design. Use when you need a step-by-step plan, key file identification, and architectural trade-off analysis before code changes are made.\n- `verify` — Verification specialist. Runs build, test, and lint commands. Use after writing or modifying code to confirm correctness before delivering to the user.\n- `writer` — Content production and research specialist. Use for deep research reports, data analysis with tables, competitive analysis, project proposals, or complex Markdown document production.\n\n# When to Parallelize\n\nTo run multiple subagents in parallel, call the `Agent` tool multiple times in a single response — one call per subtask. All calls execute concurrently.\n\n**Parallelize when:**\n- Analyzing/reviewing independent modules (non-overlapping files)\n- Multi-perspective evaluation (security, performance, code quality)\n- Large-scale refactors across different directories\n\n**Don't parallelize when:**\n- Tasks have dependencies (one needs the other's output)\n- Multiple tasks would write to the same file or directory\n- The task is simple enough for a single Agent call\n\nWhen in doubt about whether tasks have hidden dependencies, check the file paths each task would touch before deciding.\n\n# General Guidelines for Coding\n\nWhen building something from scratch, you should:\n\n- Understand the user's requirements.\n- Ask the user for clarification if there is anything unclear.\n- Design the architecture and make a plan for the implementation.\n- Write the code in a modular and maintainable way.\n\nAlways use tools to implement your code changes:\n\n- Use `Write` to create or overwrite source files. Code that only appears in your text response is NOT saved to the file system and will not take effect.\n- Use `Bash` to run and test your code after writing it.\n- Iterate: if tests fail, read the error, fix the code with `Write` or `Edit`, and re-test with `Bash`.\n\nWhen working on an existing codebase, you should:\n\n- Understand the codebase by reading it with tools (`Read`, `Glob`, `Grep`) before making changes. Identify the ultimate goal and the most important criteria to achieve the goal.\n- When using `Glob`, include a literal anchor (file extension or subdirectory) in the pattern. Pure wildcards like `*` or `**/*` are rejected by the tool.\n- For a bug fix, you typically need to check error logs or failed tests, scan over the codebase to find the root cause, and figure out a fix. If user mentioned any failed tests, you should make sure they pass after the changes.\n- For a feature, you typically need to design the architecture, and write the code in a modular and maintainable way, with minimal intrusions to existing code. Add new tests if the project already has tests.\n- For a code refactoring, you typically need to update all the places that call the code you are refactoring if the interface changes. DO NOT change any existing logic especially in tests, focus only on fixing any errors caused by the interface changes.\n- Make MINIMAL changes to achieve the goal. This is very important to your performance.\n- Follow the coding style of existing code in the project.\n- For broader codebase exploration and deep research, use `Agent` with `subagent_type=\"explore\"` — a fast, read-only agent specialized for searching and understanding codebases. Reach for it when your task will clearly require more than 3 search queries, or when you need to investigate multiple files and patterns. Launch multiple explore agents concurrently when investigating independent questions.\n\nDO NOT run `git commit`, `git push`, `git reset`, `git rebase` and/or do any other git mutations unless explicitly asked to do so. Ask for confirmation each time when you need to do git mutations, even if the user has confirmed in earlier conversations.\n\n# General Guidelines for Research and Data Processing\n\nThe user may ask you to research on certain topics, process or generate certain multimedia files. When doing such tasks, you must:\n\n- Understand the user's requirements thoroughly, ask for clarification before you start if needed.\n- Make plans before doing deep or wide research, to ensure you are always on track.\n- Search on the Internet if possible, with carefully-designed search queries to improve efficiency and accuracy.\n- Use proper tools or shell commands or Python packages to process or generate images, videos, PDFs, docs, spreadsheets, presentations, or other multimedia files. Detect if there are already such tools in the environment. If you have to install third-party tools/packages, you MUST ensure that they are installed in a virtual/isolated environment.\n- Once you generate or edit any images, videos or other media files, try to read it again before proceed, to ensure that the content is as expected.\n- Avoid installing or deleting anything to/from outside of the current working directory. If you have to do so, ask the user for confirmation.\n\n# Working Environment\n\n## Operating System\n\nYou are running on **{{ SCREAM_OS }}**. The Bash tool executes commands using **{{ SCREAM_SHELL }}**.\n{% if SCREAM_OS == \"Windows\" %}\n\nIMPORTANT: You are on Windows. The Bash tool runs through Git Bash, so use Unix shell syntax inside Bash commands — `/dev/null` not `NUL`, and forward slashes in paths. For file operations, always prefer the built-in tools (Read, Write, Edit, Glob, Grep) over Bash commands — they work reliably across all platforms.\n{% endif %}\n\nThe operating environment is not in a sandbox. Any actions you do will immediately affect the user's system. So you MUST be extremely cautious. Unless being explicitly instructed to do so, you should never access (read/write/execute) files outside of the working directory.\n\n## Date and Time\n\nThe current date and time in ISO format is `{{ SCREAM_NOW }}`. This is only a reference for you when searching the web, or checking file modification time, etc. If you need the exact time, use Bash tool with proper command.\n\n## Working Directory\n\nThe current working directory is `{{ SCREAM_WORK_DIR }}`. This should be considered as the project root if you are instructed to perform tasks on the project. Every file system operation will be relative to the working directory if you do not explicitly specify the absolute path. Tools may require absolute paths for some parameters, IF SO, YOU MUST use absolute paths for these parameters.\n\nThe directory listing of current working directory is:\n\n```\n{{ SCREAM_WORK_DIR_LS }}\n```\n\nUse this as your basic understanding of the project structure. The tree only shows the first two levels; entries marked \"... and N more\" indicate additional contents — use Glob or Bash to explore further.\n{% if SCREAM_ADDITIONAL_DIRS_INFO %}\n\n## Additional Directories\n\nThe following directories have been added to the workspace. You can read, write, search, and glob files in these directories as part of your workspace scope.\n\n{{ SCREAM_ADDITIONAL_DIRS_INFO }}\n{% endif %}\n\n# Project Information\n\nMarkdown files named `AGENTS.md` usually contain the background, structure, coding styles, user preferences and other relevant information about the project. You should use this information to understand the project and the user's preferences. `AGENTS.md` files may exist at different locations in the project, but typically there is one in the project root.\n\n> Why `AGENTS.md`?\n>\n> `README.md` files are for humans: quick starts, project descriptions, and contribution guidelines. `AGENTS.md` complements this by containing the extra, sometimes detailed context coding agents need: build steps, tests, and conventions that might clutter a README or aren’t relevant to human contributors.\n>\n> We intentionally kept it separate to:\n>\n> - Give agents a clear, predictable place for instructions.\n> - Keep `README`s concise and focused on human contributors.\n> - Provide precise, agent-focused guidance that complements existing `README` and docs.\n\nThe `AGENTS.md` instructions (merged from all applicable directories):\n\n`````````\n{{ SCREAM_AGENTS_MD }}\n`````````\n\n`AGENTS.md` files can appear at any level of the project directory tree, including inside `.scream-code/` directories. Each file governs the directory it resides in and all subdirectories beneath it. When multiple `AGENTS.md` files apply to a file you are modifying, instructions in deeper directories take precedence over those in parent directories. User instructions given directly in the conversation always take the highest precedence.\n\nWhen working on files in subdirectories, always check whether those directories contain their own `AGENTS.md` with more specific guidance that supplements or overrides the instructions above. You may also check `README`/`README.md` files for more information about the project.\n\nIf you modified any files/styles/structures/configurations/workflows/... mentioned in `AGENTS.md` files, you MUST update the corresponding `AGENTS.md` files to keep them up-to-date.\n\n# Skills\n\nSkills are reusable, composable capabilities that enhance your abilities. Each skill is either a self-contained directory with a `SKILL.md` file or a standalone `.md` file that contains instructions, examples, and/or reference material.\n\n## What are skills?\n\nSkills are modular extensions that provide:\n\n- Specialized knowledge: Domain-specific expertise (e.g., PDF processing, data analysis)\n- Workflow patterns: Best practices for common tasks\n- Tool integrations: Pre-configured tool chains for specific operations\n- Reference material: Documentation, templates, and examples\n\n## Available skills\n\nSkills are grouped by scope (`Project`, `User`, `Extra`, `Built-in`) so you can tell where each came from. When the user refers to \"the skill in this project\" or \"the user-scope skill\", use the scope heading to disambiguate. When multiple scopes define a skill with the same name, the more specific scope takes precedence: **Project overrides User overrides Extra overrides Built-in**.\n\n{{ SCREAM_SKILLS }}\n\n## How to use skills\n\nIdentify the skills that are likely to be useful for the tasks you are currently working on, read the skill file for detailed instructions, guidelines, scripts and more.\n\nOnly read skill details when needed to conserve the context window.\n\nWhen a task matches an available skill, invoke it via the `Skill` tool before writing your own plan.\n\n# Verification Protocol\n\nAfter completing a code change (creating or modifying files), you MUST verify your work before delivering to the user. Use the verify sub-agent — it detects the project type deterministically and runs the correct build/test/lint commands.\n\n## When to verify\n\n- You wrote or edited source files — verify\n- You ran a code-generating shell command — verify\n- Pure Q&A / read-only operations — skip\n\n## How to verify\n\n1. Note any tests that were ALREADY failing before your changes (check earlier test output in the conversation).\n\n2. Call:\n   `spawn_agent(type=\"verify\", prompt=\"Verify the current changes. <list pre-existing failures if any>\")`\n\n3. The verify agent handles everything: project detection, command selection, execution, reporting. You do NOT need to detect the project type yourself.\n\n4. On pass: deliver to user.\n5. On fail: fix the issues, re-verify. Maximum 2 rounds.\n6. Pre-existing failures: mark and report, but do NOT block delivery.\n\n# Ultimate Reminders\n\nAt any time, you should be HELPFUL, CONCISE, and ACCURATE. Be thorough in your actions — test what you build, verify what you change — not in your explanations.\n\n- Never diverge from the requirements and the goals of the task you work on. Stay on track.\n- Never give the user more than what they want.\n- Try your best to avoid any hallucination. Do fact checking before providing any factual information.\n- Think about the best approach, then take action decisively.\n- Do not give up too early.\n- ALWAYS, keep it stupidly simple. Do not overcomplicate things.\n- When the task requires creating or modifying files, always use tools to do so. Never treat displaying code in your response as a substitute for actually writing it to the file system.\n- Never access files outside the working directory. Do not run `git commit`, `git push`, `git reset`, `git rebase`, or publish operations unless explicitly asked.\n",
 	"profile/default/verify.yaml": "extends: agent\nname: verify\npromptVars:\n  roleAdditional: |\n    You are now running as a sub-agent. All `user` messages are sent by the main agent.\n    You are the Verify sub-agent. Your sole responsibility is to detect the project\n    type and run verification commands. Do NOT try to fix anything.\n\n    # Phase 1: Detect project type (deterministic lookup — no guessing)\n\n    Use `Read` to check for these files in order (first match wins).\n    Read the file content, then look up the exact commands from this table:\n\n    ## package.json exists — read it and check dependencies/devDependencies:\n\n    | Condition | Type | Build | Test | Lint |\n    |-----------|------|-------|------|------|\n    | `dependencies.next` or `devDependencies.next` | Next.js | `npx next build` | `npm test` (if script exists) | `npx next lint` |\n    | `dependencies.react-scripts` | CRA | `npx react-scripts build` | `npm test` (if exists) | `npm run lint` (if exists) |\n    | `devDependencies.vite` or `dependencies.vite` | Vite | `npx vite build` | `npx vitest run` (if script exists) | `npm run lint` (if exists) |\n    | `devDependencies.@sveltejs/kit` | SvelteKit | `npx vite build` | `npm test` (if exists) | `npm run lint` (if exists) |\n    | `dependencies.astro` | Astro | `npx astro build` | `npm test` (if exists) | `npm run lint` (if exists) |\n    | none of the above | Node.js | `npm run build` (if script exists) | `npm test` (if script exists) | `npm run lint` (if script exists) |\n\n    Check `scripts` in package.json for `test`, `lint`, `build` — only include commands whose scripts actually exist. Look for alternatives: `test:ci`, `test:unit`, `typecheck`, `check`, `format:check`.\n\n    ## Other ecosystems:\n\n    | File | Type | Build | Test | Lint |\n    |------|------|-------|------|------|\n    | `requirements.txt` or `pyproject.toml` | Python | — | `python -m pytest` (if tests/ dir exists) or `python -m unittest` | `ruff check .` |\n    | `go.mod` | Go | `go build ./...` | `go test ./...` | `go vet ./...` |\n    | `Cargo.toml` | Rust | `cargo build` | `cargo test` | `cargo clippy` |\n    | `pom.xml` | Maven | `mvn package -q` | `mvn test` | — |\n    | `build.gradle` or `build.gradle.kts` | Gradle | `./gradlew build` (or `gradle build`) | `./gradlew test` (or `gradle test`) | — |\n    | `Makefile` | Make | `make build` (if target exists) | `make test` (if target exists) | `make check` or `make lint` (if target exists) |\n\n    ## Fallback:\n    If none of the above match, report: \"No supported project type detected.\" and stop.\n\n    # Phase 2: Run commands\n\n    Run each command in order: build → test → lint.\n    For Python/Go/Rust, skip build if the command is not available.\n    Capture stdout and stderr for each. Time each command.\n\n    # Phase 3: Report\n\n    Use this exact format (each command gets ONE line):\n\n    ## Verify Report\n\n    **Project:** <detected type>\n\n    ✅ build: passed (<N>s)\n    ❌ test: <N> failed, <M> passed (<N>s)\n       FAIL <file> > <test name>\n       <error message>\n    ⚠️ lint: <N> warnings, no errors (<N>s)\n\n    If all pass:\n    **Result:** ✅ All checks passed.\n\n    If any fail:\n    **Result:** ❌ <N> check(s) failed. See details above.\n\n    # Rules\n\n    - Do NOT try to fix anything. Report only.\n    - Do NOT ask questions. Run and report.\n    - Skip commands whose scripts/tools don't exist — mark as \"⏭️ skipped: not configured\".\n    - If the SAME test was already failing before this change (the parent agent will tell you), mark it \"⏭️ pre-existing\" not \"❌\".\n\nwhenToUse: |\n  Verification specialist. Detects project type deterministically and runs\n  build, test, and lint commands. Use after writing or modifying code to\n  confirm correctness before delivering to the user.\ntools:\n  - Bash\n  - Read\n  - Glob\n  - Grep\n",
 	"profile/default/writer.yaml": "extends: agent\nname: writer\npromptVars:\n  roleAdditional: |\n    You are now running as a subagent. All the `user` messages are sent by the main agent. The main agent cannot see your context, it can only see your last message when you finish the task. You must treat the parent agent as your caller. Do not directly ask the end user questions. If something is unclear, explain the ambiguity in your final summary to the parent agent.\n\n    You are a content production and research specialist. Your output is not merely text — it is structured, evidence-based analysis presented in Markdown. Every piece of content you produce must demonstrate depth, traceability, and intellectual honesty.\n\n    ## Core Methodology: Three-Layer Deep Analysis\n\n    Before you write a single paragraph, you must perform a three-layer analysis of the request. This is your most important responsibility. Surface-level writing is not acceptable.\n\n    **Layer 1 — The Ask:** What did the user explicitly request? What is the surface-level topic, format, and scope?\n\n    **Layer 2 — The Purpose:** Why does the user want this? What decision will this content inform? What outcome are they trying to achieve? If the request is a report, who is the audience and what do they need to decide? If it is an analysis, what hypothesis is being tested?\n\n    **Layer 3 — The Origin:** How did this purpose come to be? What is the broader context, market force, organizational pressure, or personal motivation that created this need? What would happen if this need were left unaddressed?\n\n    Your final output must reflect all three layers. The content should not just describe — it should explain, contextualize, and anticipate. The reader should finish reading and think, \"This person truly understands why I needed this.\"\n\n    ## Your Strengths\n\n    - **Multi-dimensional analysis**: You do not settle for a single angle. You examine topics through multiple lenses — economic, technical, social, temporal, competitive — and synthesize them into a coherent narrative.\n    - **Evidence-based writing**: Every significant claim has a source. You prefer primary sources and data over secondary opinion. You cite sources inline or in a dedicated Evidence section.\n    - **Objective rigor**: You distinguish fact from inference and inference from speculation. You present counter-arguments. You flag uncertainty explicitly rather than hiding it behind confident language.\n    - **Table precision**: When data is involved, you present it in clean, accurate Markdown tables. You verify column alignment, unit consistency, and mathematical correctness before outputting.\n\n    ## Guidelines\n\n    ### Deep Analysis\n    - Start every substantial piece with a \"Why This Matters\" section that captures your three-layer analysis.\n    - Do not merely list facts. Explain the relationships between them. Cause and effect, trade-offs, second-order consequences.\n    - When comparing options, use a structured comparison table that covers all relevant dimensions, not just the obvious ones.\n    - Anticipate the reader's next three questions and address them proactively.\n\n    ### Sources and Evidence\n    - For data claims, cite the source. Prefer: `SearchWeb`, `FetchURL`, or files provided by the caller.\n    - If you cannot verify a claim, say so explicitly: \"This figure could not be independently verified.\"\n    - Distinguish between \"confirmed\" (you checked it), \"reported\" (a source claims it), and \"estimated\" (your inference).\n    - Include an Evidence section in your output listing sources and verification methods.\n\n    ### Objectivity\n    - Present both supporting and contradicting evidence.\n    - Avoid adjectives that imply certainty without proof: \"obviously\", \"undoubtedly\", \"inevitably\".\n    - Use probabilistic language when appropriate: \"based on current data, the most likely outcome is...\"\n    - Separate \"what is\" (fact) from \"what it means\" (interpretation) from \"what should be done\" (recommendation).\n\n    ### Markdown Tables (Mandatory for Data)\n    - All tables use standard Markdown pipe syntax.\n    - Headers are bold and semantically clear.\n    - Numbers are right-aligned; text is left-aligned; status/tags are centered.\n    - Every table has a descriptive caption above it (e.g., \"Table 1: Q1-Q4 Revenue by Region\").\n    - Keep columns ≤ 8. If more are needed, split into related tables.\n    - Verify arithmetic: totals, percentages, and growth rates must be correct.\n    - Use consistent units within a column.\n\n    ### Content Structure\n    - Use clear heading hierarchies (`#`, `##`, `###`).\n    - Each major section begins with a concise summary of what the section covers.\n    - Each major section ends with a \"So What\" takeaway that connects the facts back to the reader's purpose.\n    - Complex comparisons always use tables. Narrative descriptions of tabular data are insufficient.\n\n    ## Output Format\n\n    Your final response must include:\n\n    ```markdown\n    ## SUMMARY\n    A concise executive summary capturing the three-layer analysis and key conclusions.\n\n    ## WHY THIS MATTERS\n    The three-layer deep analysis (Ask → Purpose → Origin) that frames everything below.\n\n    ## [Main Content Sections]\n    The body of the analysis, report, or document.\n\n    ## EVIDENCE\n    - Source A: description and verification method\n    - Source B: description and verification method\n\n    ## RISKS & LIMITATIONS\n    What is uncertain, unverified, or context-dependent in this analysis.\n    ```\n\n    ## Important Reminders\n\n    - Your only output is Markdown content. You do not generate .docx, .pdf, or any other format.\n    - If the caller asks for a specific file format, output Markdown and note that format conversion is the caller's responsibility.\n    - If the user provides a template or sample file, Read it first and match its depth, tone, and structure.\n    - After writing, verify: logical self-consistency, source accuracy, table arithmetic, and structural completeness.\n    - Never fabricate data. If data is missing, say so and explain the impact of the gap.\nwhenToUse: |\n  Use this agent when the task involves producing substantial written content that requires depth: research reports, competitive analysis, data-driven documents, strategic proposals, or any work where understanding the \"why\" behind the request is as important as the \"what.\" This agent excels at multi-dimensional analysis, evidence-based reasoning, and structured Markdown output with precise tables.\ntools:\n  - Bash\n  - Read\n  - ReadMediaFile\n  - Glob\n  - Grep\n  - Write\n  - Edit\n  - WebSearch\n  - FetchURL\n  - mcp__*\n"
 };
@@ -91126,6 +91259,7 @@ var ToolManager = class {
 			parameters,
 			resolveExecution: (args) => {
 				return {
+					description,
 					approvalRule: name,
 					execute: async (context) => {
 						return this.agent.rpc.toolCall({
@@ -91148,7 +91282,7 @@ var ToolManager = class {
 		this.userTools.delete(name);
 		this.enabledTools.delete(name);
 	}
-	registerMcpServer(serverName, client, tools, enabledTools) {
+	registerMcpServer(serverName, client, tools, enabledTools, options) {
 		this.unregisterMcpServer(serverName);
 		const qualifiedNames = [];
 		const collisions = [];
@@ -91187,9 +91321,41 @@ var ToolManager = class {
 				parameters: tool.parameters,
 				resolveExecution: (args) => {
 					return {
+						description: tool.description,
 						approvalRule: qualified,
 						execute: async (context) => {
-							return mcpResultToExecutableOutput(await client.callTool(tool.name, args ?? {}, context.signal), qualified);
+							const runCall = async (targetClient) => {
+								return mcpResultToExecutableOutput(await targetClient.callTool(tool.name, args ?? {}, context.signal), qualified);
+							};
+							try {
+								return await runCall(client);
+							} catch (error) {
+								const mcp = options?.mcp;
+								if (mcp === void 0 || context.signal.aborted || !(isRetriableMcpCallError(error) || mcp.get(serverName)?.status !== "connected")) return {
+									isError: true,
+									output: `MCP tool "${tool.name}" failed: ` + (error instanceof Error ? error.message : String(error))
+								};
+								try {
+									await mcp.reconnect(serverName);
+								} catch {}
+								if (context.signal.aborted) return {
+									isError: true,
+									output: `MCP tool "${tool.name}" aborted during reconnect.`
+								};
+								const resolved = mcp.resolved(serverName);
+								if (resolved === void 0) return {
+									isError: true,
+									output: `MCP tool "${tool.name}" failed: ` + (error instanceof Error ? error.message : String(error))
+								};
+								try {
+									return await runCall(resolved.client);
+								} catch (retryError) {
+									return {
+										isError: true,
+										output: `MCP tool "${tool.name}" failed after reconnect: ` + (retryError instanceof Error ? retryError.message : String(retryError))
+									};
+								}
+							}
 						}
 					};
 				}
@@ -91266,7 +91432,7 @@ var ToolManager = class {
 	registerConnectedMcpServer(mcp, entry) {
 		const resolved = mcp.resolved(entry.name);
 		if (resolved === void 0) return;
-		const result = this.registerMcpServer(entry.name, resolved.client, resolved.tools, resolved.enabledNames);
+		const result = this.registerMcpServer(entry.name, resolved.client, resolved.tools, resolved.enabledNames, { mcp });
 		this.emitMcpToolCollisions(entry.name, result.collisions);
 		this.agent.emitEvent({
 			type: "tool.list.updated",
@@ -96068,67 +96234,6 @@ var StreamableHTTPClientTransport = class {
 	}
 };
 //#endregion
-//#region ../../packages/agent-core/src/version.ts
-function getCoreVersion() {
-	try {
-		const raw = readFileSync(fileURLToPath(new URL("../package.json", import.meta.url)), "utf-8");
-		const pkg = JSON.parse(raw);
-		return typeof pkg.version === "string" ? pkg.version : "0.0.0";
-	} catch {
-		return "0.0.0";
-	}
-}
-const SCREAM_MCP_CLIENT_VERSION = getCoreVersion();
-/**
-* Build the `RequestOptions` object accepted by the MCP SDK's `callTool`,
-* including either the configured tool-call timeout, an in-flight abort
-* signal, both, or neither. Returns `undefined` when nothing needs to be
-* passed so the SDK falls back to its defaults.
-*/
-function buildRequestOptions(toolCallTimeoutMs, signal) {
-	if (toolCallTimeoutMs === void 0 && signal === void 0) return void 0;
-	return {
-		timeout: toolCallTimeoutMs,
-		signal
-	};
-}
-function toMcpToolDefinition(tool) {
-	return {
-		name: tool.name,
-		description: tool.description ?? "",
-		inputSchema: tool.inputSchema
-	};
-}
-/**
-* Normalise the SDK's `callTool` return into ltod's {@link MCPToolResult}.
-* The SDK can return either the modern `{ content, isError }` shape or a
-* legacy `{ toolResult }` shape; we collapse the legacy shape to a single
-* text content block.
-*/
-function toMcpToolResult(result) {
-	if (typeof result === "object" && result !== null && "content" in result) {
-		const typed = result;
-		if (Array.isArray(typed.content)) return {
-			content: typed.content,
-			isError: typed.isError === true
-		};
-	}
-	if (typeof result === "object" && result !== null && "toolResult" in result) {
-		const legacy = result.toolResult;
-		return {
-			content: [{
-				type: "text",
-				text: typeof legacy === "string" ? legacy : JSON.stringify(legacy)
-			}],
-			isError: false
-		};
-	}
-	return {
-		content: [],
-		isError: false
-	};
-}
-//#endregion
 //#region ../../packages/agent-core/src/mcp/client-http.ts
 /**
 * Wraps the SDK streamable-HTTP transport as a ltod {@link MCPClient}.
@@ -99273,6 +99378,7 @@ async function copyPluginToManagedRoot(screamHomeDir, id, sourceRoot) {
 async function recordFrom(input) {
 	const { parsed } = input;
 	const hasError = parsed.diagnostics.some((d) => d.severity === "error");
+	const skills = hasError || parsed.manifest === void 0 ? [] : await discoverPluginSkills(input.id, parsed.manifest);
 	return {
 		id: input.id,
 		root: input.root,
@@ -99284,7 +99390,8 @@ async function recordFrom(input) {
 		originalSource: input.originalSource,
 		capabilities: input.capabilities,
 		github: input.github,
-		skillCount: await countDiscoveredPluginSkills(input.id, parsed.manifest),
+		skills,
+		skillCount: skills.length,
 		manifest: parsed.manifest,
 		manifestKind: parsed.manifestKind,
 		manifestPath: parsed.manifestPath,
@@ -99301,6 +99408,7 @@ function recordToSummary(record) {
 		enabled: record.enabled,
 		state: record.state,
 		skillCount: record.skillCount,
+		skills: record.skills,
 		mcpServerCount: Object.keys(record.manifest?.mcpServers ?? {}).length,
 		enabledMcpServerCount: pluginMcpServersInfo(record).filter((server) => server.enabled).length,
 		hasErrors: record.diagnostics.some((d) => d.severity === "error"),
@@ -99309,7 +99417,7 @@ function recordToSummary(record) {
 		github: record.github
 	};
 }
-async function countDiscoveredPluginSkills(pluginId, manifest) {
+async function discoverPluginSkills(pluginId, manifest) {
 	const roots = (manifest?.skills ?? []).map((dir) => ({
 		path: dir,
 		source: "extra",
@@ -99318,8 +99426,11 @@ async function countDiscoveredPluginSkills(pluginId, manifest) {
 			instructions: manifest?.skillInstructions
 		}
 	}));
-	if (roots.length === 0) return 0;
-	return (await discoverSkills({ roots })).length;
+	if (roots.length === 0) return [];
+	return (await discoverSkills({ roots })).map((skill) => ({
+		name: skill.name,
+		description: skill.description
+	}));
 }
 function recordToInfo(record) {
 	return {
@@ -122377,6 +122488,14 @@ const HUE_STOPS = 24;
 const SUB_STEPS = 5;
 const BREATHE_STEPS = HUE_STOPS * SUB_STEPS;
 const BREATHE_INTERVAL_MS = 40;
+const WELCOME_TIPS = [
+	"/config  配置模型",
+	"/sessions  恢复历史会话",
+	"/  输入后打开快捷菜单"
+];
+const WELCOME_SESSION_SLOTS = 3;
+const LEFT_COLUMN_WIDTH = 22;
+const MIN_BOX_WIDTH = 50;
 const LOGO_FRAMES = [
 	["██▄▄▄██", "▐█▄▀▄█▌"],
 	["██▄▄▄██", "▐▄▄▀▄▄▌"],
@@ -122443,11 +122562,6 @@ function rgbToHex(r, g, b) {
 	const c = (v) => Math.round(Math.max(0, Math.min(255, v))).toString(16).padStart(2, "0");
 	return `#${c(r)}${c(g)}${c(b)}`;
 }
-/**
-* Build a full-hue-wheel palette anchored at the primary-green hue.
-* At frame 0 (and BREATHE_STEPS) the colour is pure primary; in between
-* it sweeps through all 24 hue stops with smooth sub-step interpolation.
-*/
 function buildBreathingPalette(primaryHex, hueStops, subSteps) {
 	const [r, g, b] = hexToRgb$1(primaryHex);
 	const [baseHue] = rgbToHsl(r, g, b);
@@ -122459,6 +122573,25 @@ function buildBreathingPalette(primaryHex, hueStops, subSteps) {
 	}
 	return palette;
 }
+function formatTimeAgo(timestamp) {
+	const seconds = Math.floor((Date.now() - timestamp) / 1e3);
+	if (seconds < 60) return "刚刚";
+	const minutes = Math.floor(seconds / 60);
+	if (minutes < 60) return `${minutes}分钟前`;
+	const hours = Math.floor(minutes / 60);
+	if (hours < 24) return `${hours}小时前`;
+	return `${Math.floor(hours / 24)}天前`;
+}
+function padSpaces(n) {
+	return " ".repeat(Math.max(0, n));
+}
+function centerText(text, width) {
+	const visLen = visibleWidth(text);
+	if (visLen >= width) return truncateToWidth(text, width, "…");
+	const leftPad = Math.floor((width - visLen) / 2);
+	const rightPad = width - visLen - leftPad;
+	return " ".repeat(leftPad) + text + " ".repeat(rightPad);
+}
 var WelcomeComponent = class {
 	state;
 	colors;
@@ -122466,11 +122599,13 @@ var WelcomeComponent = class {
 	breatheFrame = 0;
 	breatheTimer = null;
 	breathePalette;
+	recentSessions;
 	borderTitle = null;
-	constructor(state, colors, ui) {
+	constructor(state, colors, ui, recentSessions = []) {
 		this.state = state;
 		this.colors = colors;
 		this.ui = ui;
+		this.recentSessions = recentSessions;
 		this.breathePalette = buildBreathingPalette(colors.primary, HUE_STOPS, SUB_STEPS);
 		this.startBreathing();
 	}
@@ -122493,56 +122628,103 @@ var WelcomeComponent = class {
 	invalidate() {}
 	render(width) {
 		const breatheColor = this.breathePalette[this.breatheFrame] ?? this.colors.primary;
-		const logoColor = (s) => chalk.hex(breatheColor)(s);
+		const boxColor = chalk.hex(breatheColor);
 		const dim = chalk.hex(this.colors.textDim);
-		const labelStyle = chalk.bold.hex(this.colors.textDim);
-		const innerWidth = Math.max(10, width - 4);
+		const muted = chalk.hex(this.colors.textMuted);
+		const titleColor = chalk.bold.hex(breatheColor);
+		const boxWidth = Math.max(MIN_BOX_WIDTH, width);
+		const innerWidth = boxWidth - 2;
+		const showRightColumn = innerWidth >= 55;
+		const leftCol = showRightColumn ? LEFT_COLUMN_WIDTH : innerWidth;
+		const rightCol = showRightColumn ? Math.max(10, innerWidth - leftCol - 1) : 0;
 		const isLoggedOut = !this.state.model;
-		const frame = LOGO_FRAMES[this.breatheTimer !== null ? Math.floor(this.breatheFrame / 24) % LOGO_FRAMES.length : 0];
-		const logo = [logoColor(frame[0]), logoColor(frame[1])];
 		const activeModel = this.state.availableModels[this.state.model];
-		const modelValue = isLoggedOut ? chalk.hex(this.colors.warning)("未设置，运行 /config") : activeModel?.displayName ?? activeModel?.model ?? this.state.model;
+		const modelValue = isLoggedOut ? chalk.hex(this.colors.warning)("未设置") : activeModel?.displayName ?? activeModel?.model ?? this.state.model;
 		let versionValue;
-		if (this.state.hasNewVersion && this.state.latestVersion !== null) versionValue = chalk.hex(this.colors.warning)(this.state.version) + "  " + chalk.hex(this.colors.textDim)("有新版本（" + this.state.latestVersion + "）");
+		if (this.state.hasNewVersion && this.state.latestVersion !== null) versionValue = chalk.hex(this.colors.warning)(this.state.version) + " " + dim("(" + this.state.latestVersion + ")");
 		else versionValue = this.state.version;
-		const hintText = isLoggedOut ? "运行 /config 开始配置" : "发送 / 进入快捷菜单，/exit 保存并退出";
-		const contentLines = [
-			...logo,
+		const frame = LOGO_FRAMES[this.breatheTimer !== null ? Math.floor(this.breatheFrame / 24) % LOGO_FRAMES.length : 0];
+		const logo = [boxColor(frame[0]), boxColor(frame[1])];
+		const tipLines = [];
+		for (const tip of WELCOME_TIPS) tipLines.push(` ${dim("•")} ${muted(tip)}`);
+		const sessionLines = [];
+		const sessions = this.recentSessions.slice(0, WELCOME_SESSION_SLOTS);
+		if (sessions.length === 0) sessionLines.push(` ${dim("•")} ${muted("无最近会话")}`);
+		else for (const session of sessions) {
+			const name = session.title ?? session.id;
+			const timeAgo = formatTimeAgo(session.updatedAt);
+			sessionLines.push(` ${dim("•")} ${muted(name)} ${dim(`(${timeAgo})`)}`);
+		}
+		let leftRows;
+		let rightRows = [];
+		let separatorRow = -1;
+		if (showRightColumn) {
+			rightRows = [
+				` ${titleColor("Tips")}`,
+				...tipLines,
+				boxColor("─".repeat(rightCol)),
+				` ${titleColor("最近会话")}`,
+				...sessionLines
+			];
+			separatorRow = 1 + tipLines.length;
+			const leftContent = [
+				"",
+				centerText(logo[0], leftCol),
+				centerText(logo[1], leftCol),
+				"",
+				centerText(dim(versionValue), leftCol),
+				centerText(dim(modelValue), leftCol)
+			];
+			const topPad = Math.max(0, Math.floor((rightRows.length - leftContent.length) / 2));
+			const bottomPad = Math.max(0, rightRows.length - leftContent.length - topPad);
+			leftRows = [
+				...Array(topPad).fill(""),
+				...leftContent,
+				...Array(bottomPad).fill("")
+			];
+		} else leftRows = [
 			"",
-			labelStyle("版本：") + " " + versionValue,
-			labelStyle("模型：") + " " + modelValue,
-			labelStyle("目录：") + " " + this.state.workDir,
+			centerText(logo[0], leftCol),
+			centerText(logo[1], leftCol),
 			"",
-			dim(hintText)
+			centerText(dim(versionValue), leftCol),
+			centerText(dim(modelValue), leftCol),
+			""
 		];
 		const borderTitle = this.borderTitle ?? "";
-		const contentWidth = width - 2;
+		const contentWidth = boxWidth - 2;
 		let topBorder;
 		if (borderTitle) {
-			const centerPos = Math.floor(contentWidth / 2);
+			const titleVis = visibleWidth(borderTitle);
+			const textPad = Math.floor((leftCol - titleVis) / 2);
+			const leftDash = Math.max(0, textPad - 2);
 			const titleText = `─ ${borderTitle} ─`;
-			const titleStart = centerPos - Math.floor(visibleWidth(titleText) / 2);
-			const leftDash = Math.max(0, titleStart);
-			const rightDash = Math.max(0, contentWidth - leftDash - visibleWidth(titleText));
-			topBorder = logoColor("╭" + "─".repeat(leftDash) + titleText + "─".repeat(rightDash) + "╮");
-		} else topBorder = logoColor("╭" + "─".repeat(contentWidth) + "╮");
-		const lines = [
-			"",
-			topBorder,
-			logoColor("│") + " ".repeat(width - 2) + logoColor("│")
-		];
-		for (const content of contentLines) {
-			const truncated = truncateToWidth(content, innerWidth, "…");
-			const vis = visibleWidth(truncated);
-			const centerPad = Math.floor((width - 1 - vis) / 2);
-			const rightPad = width - 2 - vis - centerPad;
-			lines.push(logoColor("│") + " ".repeat(centerPad) + truncated + " ".repeat(rightPad) + logoColor("│"));
-		}
-		lines.push(logoColor("│") + " ".repeat(width - 2) + logoColor("│"));
-		lines.push(logoColor("╰" + "─".repeat(width - 2) + "╯"));
+			const titleBlockVis = titleVis + 4;
+			const rightDash = Math.max(0, contentWidth - leftDash - titleBlockVis);
+			topBorder = boxColor("╭" + "─".repeat(leftDash) + titleText + "─".repeat(rightDash) + "╮");
+		} else topBorder = boxColor("╭" + "─".repeat(contentWidth) + "╮");
+		const lines = [""];
+		const boxOffset = "";
+		lines.push(boxOffset + topBorder);
+		const totalRows = Math.max(leftRows.length, rightRows.length);
+		for (let i = 0; i < totalRows; i++) {
+			const left = this.#fitToWidth(leftRows[i] ?? "", leftCol);
+			if (showRightColumn) {
+				const right = this.#fitToWidth(rightRows[i] ?? "", rightCol);
+				const sep = i === separatorRow ? boxColor("├") : boxColor("│");
+				lines.push(boxOffset + boxColor("│") + left + sep + right + boxColor("│"));
+			} else lines.push(boxOffset + boxColor("│") + left + boxColor("│"));
+		}
+		if (showRightColumn) lines.push(boxOffset + boxColor("╰" + "─".repeat(leftCol) + "┴" + "─".repeat(rightCol) + "╯"));
+		else lines.push(boxOffset + boxColor("╰" + "─".repeat(leftCol) + "╯"));
 		lines.push("");
 		return lines;
 	}
+	#fitToWidth(str, width) {
+		const visLen = visibleWidth(str);
+		if (visLen > width) return truncateToWidth(str, width, "…");
+		return str + padSpaces(width - visLen);
+	}
 };
 //#endregion
 //#region src/tui/components/messages/agent-group.ts
@@ -124851,6 +125033,8 @@ var ToolCallComponent = class ToolCallComponent extends Container {
 			});
 			for (const line of lines) this.addChild(new Text(line, 2, 0));
 		}
+		const description = str(this.toolCall.description);
+		if (this.expanded && description.length > 0) this.addChild(new Text(chalk.dim(description), 2, 0));
 	}
 	/**
 	* Live-rendering during the `tool.call.delta` streaming window.
@@ -126624,15 +126808,11 @@ function buildOptions(marketplace, installed) {
 			label: "── 已安装 ──",
 			description: void 0
 		});
-		for (const p of installed) {
-			const enabledTag = p.enabled ? "✓ 已启用" : "✗ 已禁用";
-			const meta = [p.version ? `v${p.version}` : "", enabledTag].filter(Boolean).join("  ");
-			options.push({
-				value: `uninstall:${p.id}`,
-				label: p.displayName,
-				description: `${meta}  [${p.skillCount} skills]`
-			});
-		}
+		for (const p of installed) options.push({
+			value: `uninstall:${p.id}`,
+			label: p.displayName,
+			description: formatInstalledPluginDescription(p)
+		});
 	}
 	if (options.length === 0) options.push({
 		value: "__empty__",
@@ -126674,6 +126854,20 @@ async function confirmUninstall(host, label) {
 		host.mountEditorReplacement(picker);
 	});
 }
+const SKILL_DESC_MAX = 40;
+const SKILLS_PREVIEW_COUNT = 3;
+function formatInstalledPluginDescription(p) {
+	const enabledTag = p.enabled ? "✓ 已启用" : "✗ 已禁用";
+	const meta = [p.version ? `v${p.version}` : "", enabledTag].filter(Boolean).join("  ");
+	const skillDescriptions = p.skills.slice(0, SKILLS_PREVIEW_COUNT).map((s) => `${s.name}: ${truncate$1(s.description, SKILL_DESC_MAX)}`);
+	const remaining = p.skillCount - SKILLS_PREVIEW_COUNT;
+	const descriptionParts = [`${meta}  [${p.skillCount} skills]`, ...skillDescriptions];
+	if (remaining > 0) descriptionParts.push(`…等 ${remaining} 个 skill`);
+	return descriptionParts.join("  ·  ");
+}
+function truncate$1(value, max) {
+	return value.length > max ? `${value.slice(0, max)}…` : value;
+}
 //#endregion
 //#region src/tui/commands/btw.ts
 /**
@@ -132444,10 +132638,7 @@ var FooterComponent = class {
 		if (state.wolfpackMode) left.push(chalk.hex(colors.primary).bold("wolfpack"));
 		if (state.goalActive) left.push(chalk.hex(colors.primary).bold("goal"));
 		const model = shortenModel(modelDisplayName(state));
-		if (model) {
-			const thinkingLabel = state.thinking ? " 思考中" : "";
-			left.push(chalk.hex(colors.text)(`${model}${thinkingLabel}`));
-		}
+		if (model) left.push(chalk.hex(colors.text)(model));
 		if (this.backgroundBashTaskCount > 0) {
 			const noun = this.backgroundBashTaskCount === 1 ? "个任务" : "个任务";
 			left.push(chalk.hex(colors.primary)(`[${String(this.backgroundBashTaskCount)}${noun} 运行中]`));
@@ -132696,6 +132887,8 @@ var CustomEditor = class extends Editor {
 	resetFirstInputGate() {
 		this.firstInputFired = false;
 	}
+	/** Whether the active model has thinking enabled. When true, a small "think" label is embedded in the top-right of the input box border. */
+	thinking = false;
 	consumingPaste = false;
 	consumeBuffer = "";
 	/**
@@ -132754,7 +132947,10 @@ var CustomEditor = class extends Editor {
 			const withPrompt = injectPromptSymbol(firstContent);
 			if (withPrompt !== void 0) lines[firstContentIdx] = withPrompt;
 		}
-		return wrapWithSideBorders(lines, (s) => this.borderColor(s));
+		const paint = this.borderColor ?? ((s) => s);
+		const wrapped = wrapWithSideBorders(lines, paint);
+		if (this.thinking) injectThinkLabel(wrapped, width, paint);
+		return wrapped;
 	}
 	handleInput(data) {
 		const normalized = normalizeCapsLockedCtrl(data);
@@ -132912,6 +133108,23 @@ function wrapWithSideBorders(lines, paint) {
 		return head + line.slice(1, -1) + tail;
 	});
 }
+const THINK_LABEL = " Think ";
+const THINK_LABEL_MIN_WIDTH = 14;
+/**
+* Embed a small "think" label into the top-right corner of the input box
+* border, mirroring the welcome panel's top-left border title style.
+* The label only appears when the active model has thinking enabled.
+*/
+function injectThinkLabel(lines, width, paint) {
+	if (width < THINK_LABEL_MIN_WIDTH) return;
+	const topIdx = lines.findIndex((line) => line.includes("╭"));
+	if (topIdx === -1) return;
+	const labelBlock = `─${THINK_LABEL}─`;
+	const labelVis = visibleWidth(labelBlock);
+	const leftDashCount = width - 2 - labelVis;
+	if (leftDashCount < 1) return;
+	lines[topIdx] = paint("╭" + "─".repeat(leftDashCount) + labelBlock + "╮");
+}
 //#endregion
 //#region src/tui/utils/terminal-state.ts
 function createTerminalState() {
@@ -132946,6 +133159,7 @@ function createTUIState(options) {
 	const queueContainer = new GutterContainer(1, 1);
 	const editorContainer = new GutterContainer(1, 1);
 	const editor = new CustomEditor(ui, theme.colors);
+	editor.thinking = initialAppState.thinking;
 	return {
 		ui,
 		terminal,
@@ -133928,7 +134142,6 @@ var SessionManager = class {
 			this.host.showError("历史回放期间无法启动新会话。");
 			return;
 		}
-		await this.extractMemoriesBeforeSwitch();
 		let session;
 		try {
 			session = await this.createSessionFromCurrentState();
@@ -133986,20 +134199,6 @@ var SessionManager = class {
 		this.host.updateQueueDisplay();
 		this.host.stopMemoryIdleTimer();
 	}
-	async extractMemoriesBeforeSwitch() {
-		const session = this.host.session;
-		if (session === void 0) return;
-		if (this.host.state.appState.streamingPhase !== "idle") return;
-		this.host.state.footer.setTransientHint("正在整理会话记忆...");
-		this.host.state.ui.requestRender();
-		try {
-			await Promise.race([session.extractMemoriesOnExit(), new Promise((resolve) => setTimeout(resolve, 3e4))]);
-			this.host.showStatus("已沉淀关键信息至记忆备忘录");
-		} catch {} finally {
-			this.host.state.footer.setTransientHint(null);
-			this.host.state.ui.requestRender();
-		}
-	}
 	requireSession() {
 		if (this.host.session === void 0) throw new Error(NO_ACTIVE_SESSION_MESSAGE);
 		return this.host.session;
@@ -135911,7 +136110,8 @@ function createInitialAppState(input) {
 		goalActive: false,
 		goalContinuationCount: 0,
 		ccConnectActive: false,
-		wolfpackMode: false
+		wolfpackMode: false,
+		recentSessions: []
 	};
 }
 var ScreamTUI = class ScreamTUI {
@@ -136048,6 +136248,16 @@ var ScreamTUI = class ScreamTUI {
 	}
 	async initMainTui() {
 		const shouldReplayHistory = await this.init();
+		try {
+			const sessions = await this.harness.listSessions({ workDir: this.state.appState.workDir });
+			this.state.appState.recentSessions = sessions.slice(0, 3).map((s) => ({
+				id: s.id,
+				title: s.title,
+				updatedAt: s.updatedAt
+			}));
+		} catch {
+			this.state.appState.recentSessions = [];
+		}
 		this.mountFooter();
 		this.renderWelcome();
 		setExperimentalFlags(await this.harness.getExperimentalFlags());
@@ -136139,7 +136349,7 @@ var ScreamTUI = class ScreamTUI {
 			this.ccConnectPollTimer = void 0;
 		}
 	}
-	static MEMORY_IDLE_MS = 600 * 1e3;
+	static MEMORY_IDLE_MS = 900 * 1e3;
 	static MEMORY_EXTRACT_COOLDOWN_MS = 600 * 1e3;
 	startMemoryIdleTimer() {
 		this.stopMemoryIdleTimer();
@@ -136471,6 +136681,7 @@ var ScreamTUI = class ScreamTUI {
 		const busyChanged = "streamingPhase" in patch || "isCompacting" in patch;
 		Object.assign(this.state.appState, patch);
 		if ("planMode" in patch) this.updateEditorBorderHighlight();
+		if ("thinking" in patch) this.state.editor.thinking = patch.thinking ?? false;
 		if ("streamingPhase" in patch && patch.streamingPhase !== "idle") this.welcomeComponent?.stopBreathing();
 		this.state.footer.setState(this.state.appState);
 		this.updateActivityPane();
@@ -136613,7 +136824,7 @@ var ScreamTUI = class ScreamTUI {
 	}
 	renderWelcome() {
 		this.welcomeComponent?.stopBreathing();
-		const welcome = new WelcomeComponent(this.state.appState, this.state.theme.colors, this.state.ui);
+		const welcome = new WelcomeComponent(this.state.appState, this.state.theme.colors, this.state.ui, this.state.appState.recentSessions);
 		welcome.borderTitle = "Scream Code";
 		this.welcomeComponent = welcome;
 		if (this.state.editor.hasFirstInputFired()) welcome.stopBreathing();

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "scream-code",
-  "version": "0.5.5",
-  "description": "The Starting Point for Next-Gen Agents",
+  "version": "0.5.6",
+  "description": "A terminal-native AI agent for builders",
   "license": "MIT",
   "author": "ScreamCli",
   "homepage": "https://github.com/LIUTod/scream-code/tree/main/apps/scream-code#readme",
@@ -42,20 +42,6 @@
     "access": "public",
     "provenance": true
   },
-  "scripts": {
-    "build": "tsdown",
-    "dev": "node scripts/dev.mjs",
-    "dev:cli-only": "tsx --import ../../build/register-raw-text-loader.mjs ./src/main.ts",
-    "dev:prod": "node dist/main.mjs",
-    "clean": "rm -rf dist",
-    "typecheck": "tsc -p tsconfig.json --noEmit",
-    "test": "pnpm -w run build:packages && vitest run",
-    "e2e": "pnpm -w run build:packages && SCREAM_E2E=1 vitest run test/e2e",
-    "e2e:real": "pnpm -w run build:packages && SCREAM_E2E_REAL=1 vitest run test/e2e/real-llm-smoke.e2e.test.ts",
-    "preinstall": "node -e \"console.log('\\n📦 正在安装 scream-code，请稍候...\\n')\"",
-    "postinstall": "node scripts/postinstall.mjs",
-    "smoke": "node dist/main.mjs --version"
-  },
   "dependencies": {
     "@earendil-works/pi-tui": "^0.78.1",
     "@mariozechner/clipboard": "^0.3.2",
@@ -68,16 +54,30 @@
   },
   "devDependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
-    "@scream-cli/agent-core": "workspace:^",
-    "@scream-cli/config": "workspace:^",
-    "@scream-cli/migration-legacy": "workspace:^",
-    "@scream-cli/scream-code-sdk": "workspace:^",
-    "@scream-cli/scream-telemetry": "workspace:^",
-    "@scream-code/memory": "workspace:*",
     "@types/semver": "^7.7.0",
-    "tsx": "^4.21.0"
+    "tsx": "^4.21.0",
+    "@scream-cli/migration-legacy": "^0.5.6",
+    "@scream-cli/agent-core": "^0.5.6",
+    "@scream-cli/scream-telemetry": "^0.5.6",
+    "@scream-cli/config": "^0.5.6",
+    "@scream-code/memory": "0.5.6",
+    "@scream-cli/scream-code-sdk": "^0.5.6"
   },
   "engines": {
     "node": ">=22.19.0"
+  },
+  "scripts": {
+    "build": "tsdown",
+    "dev": "node scripts/dev.mjs",
+    "dev:cli-only": "tsx --import ../../build/register-raw-text-loader.mjs ./src/main.ts",
+    "dev:prod": "node dist/main.mjs",
+    "clean": "rm -rf dist",
+    "typecheck": "tsc -p tsconfig.json --noEmit",
+    "test": "pnpm -w run build:packages && vitest run",
+    "e2e": "pnpm -w run build:packages && SCREAM_E2E=1 vitest run test/e2e",
+    "e2e:real": "pnpm -w run build:packages && SCREAM_E2E_REAL=1 vitest run test/e2e/real-llm-smoke.e2e.test.ts",
+    "preinstall": "node -e \"console.log('\\n📦 正在安装 scream-code，请稍候...\\n')\"",
+    "postinstall": "node scripts/postinstall.mjs",
+    "smoke": "node dist/main.mjs --version"
   }
-}
+}