lcclaude 1.0.0

package/dist/src/tools/TeamCreateTool/prompt.js

@@ -0,0 +1,113 @@
+export function getPrompt() {
+  return `
+# TeamCreate
+
+## When to Use
+
+Use this tool proactively whenever:
+- The user explicitly asks to use a team, swarm, or group of agents
+- The user mentions wanting agents to work together, coordinate, or collaborate
+- A task is complex enough that it would benefit from parallel work by multiple agents (e.g., building a full-stack feature with frontend and backend work, refactoring a codebase while keeping tests passing, implementing a multi-step project with research, planning, and coding phases)
+
+When in doubt about whether a task warrants a team, prefer spawning a team.
+
+## Choosing Agent Types for Teammates
+
+When spawning teammates via the Agent tool, choose the \`subagent_type\` based on what tools the agent needs for its task. Each agent type has a different set of available tools — match the agent to the work:
+
+- **Read-only agents** (e.g., Explore, Plan) cannot edit or write files. Only assign them research, search, or planning tasks. Never assign them implementation work.
+- **Full-capability agents** (e.g., general-purpose) have access to all tools including file editing, writing, and bash. Use these for tasks that require making changes.
+- **Custom agents** defined in \`.claude/agents/\` may have their own tool restrictions. Check their descriptions to understand what they can and cannot do.
+
+Always review the agent type descriptions and their available tools listed in the Agent tool prompt before selecting a \`subagent_type\` for a teammate.
+
+Create a new team to coordinate multiple agents working on a project. Teams have a 1:1 correspondence with task lists (Team = TaskList).
+
+\`\`\`
+{
+  "team_name": "my-project",
+  "description": "Working on feature X"
+}
+\`\`\`
+
+This creates:
+- A team file at \`~/.claude/teams/{team-name}/config.json\`
+- A corresponding task list directory at \`~/.claude/tasks/{team-name}/\`
+
+## Team Workflow
+
+1. **Create a team** with TeamCreate - this creates both the team and its task list
+2. **Create tasks** using the Task tools (TaskCreate, TaskList, etc.) - they automatically use the team's task list
+3. **Spawn teammates** using the Agent tool with \`team_name\` and \`name\` parameters to create teammates that join the team
+4. **Assign tasks** using TaskUpdate with \`owner\` to give tasks to idle teammates
+5. **Teammates work on assigned tasks** and mark them completed via TaskUpdate
+6. **Teammates go idle between turns** - after each turn, teammates automatically go idle and send a notification. IMPORTANT: Be patient with idle teammates! Don't comment on their idleness until it actually impacts your work.
+7. **Shutdown your team** - when the task is completed, gracefully shut down your teammates via SendMessage with \`message: {type: "shutdown_request"}\`.
+
+## Task Ownership
+
+Tasks are assigned using TaskUpdate with the \`owner\` parameter. Any agent can set or change task ownership via TaskUpdate.
+
+## Automatic Message Delivery
+
+**IMPORTANT**: Messages from teammates are automatically delivered to you. You do NOT need to manually check your inbox.
+
+When you spawn teammates:
+- They will send you messages when they complete tasks or need help
+- These messages appear automatically as new conversation turns (like user messages)
+- If you're busy (mid-turn), messages are queued and delivered when your turn ends
+- The UI shows a brief notification with the sender's name when messages are waiting
+
+Messages will be delivered automatically.
+
+When reporting on teammate messages, you do NOT need to quote the original message—it's already rendered to the user.
+
+## Teammate Idle State
+
+Teammates go idle after every turn—this is completely normal and expected. A teammate going idle immediately after sending you a message does NOT mean they are done or unavailable. Idle simply means they are waiting for input.
+
+- **Idle teammates can receive messages.** Sending a message to an idle teammate wakes them up and they will process it normally.
+- **Idle notifications are automatic.** The system sends an idle notification whenever a teammate's turn ends. You do not need to react to idle notifications unless you want to assign new work or send a follow-up message.
+- **Do not treat idle as an error.** A teammate sending a message and then going idle is the normal flow—they sent their message and are now waiting for a response.
+- **Peer DM visibility.** When a teammate sends a DM to another teammate, a brief summary is included in their idle notification. This gives you visibility into peer collaboration without the full message content. You do not need to respond to these summaries — they are informational.
+
+## Discovering Team Members
+
+Teammates can read the team config file to discover other team members:
+- **Team config location**: \`~/.claude/teams/{team-name}/config.json\`
+
+The config file contains a \`members\` array with each teammate's:
+- \`name\`: Human-readable name (**always use this** for messaging and task assignment)
+- \`agentId\`: Unique identifier (for reference only - do not use for communication)
+- \`agentType\`: Role/type of the agent
+
+**IMPORTANT**: Always refer to teammates by their NAME (e.g., "team-lead", "researcher", "tester"). Names are used for:
+- \`to\` when sending messages
+- Identifying task owners
+
+Example of reading team config:
+\`\`\`
+Use the Read tool to read ~/.claude/teams/{team-name}/config.json
+\`\`\`
+
+## Task List Coordination
+
+Teams share a task list that all teammates can access at \`~/.claude/tasks/{team-name}/\`.
+
+Teammates should:
+1. Check TaskList periodically, **especially after completing each task**, to find available work or see newly unblocked tasks
+2. Claim unassigned, unblocked tasks with TaskUpdate (set \`owner\` to your name). **Prefer tasks in ID order** (lowest ID first) when multiple tasks are available, as earlier tasks often set up context for later ones
+3. Create new tasks with \`TaskCreate\` when identifying additional work
+4. Mark tasks as completed with \`TaskUpdate\` when done, then check TaskList for next work
+5. Coordinate with other teammates by reading the task list status
+6. If all available tasks are blocked, notify the team lead or help resolve blocking tasks
+
+**IMPORTANT notes for communication with your team**:
+- Do not use terminal tools to view your team's activity; always send a message to your teammates (and remember, refer to them by name).
+- Your team cannot hear you if you do not use the SendMessage tool. Always send a message to your teammates if you are responding to them.
+- Do NOT send structured JSON status messages like \`{"type":"idle",...}\` or \`{"type":"task_completed",...}\`. Just communicate in plain text when you need to message teammates.
+- Use TaskUpdate to mark tasks completed.
+- If you are an agent in the team, the system will automatically send idle notifications to the team lead when you stop.
+
+`.trim();
+}

package/dist/src/tools/TeamDeleteTool/TeamDeleteTool.js

@@ -0,0 +1,96 @@
+import { z } from "zod/v4";
+import { logEvent } from "../../services/analytics/index.js";
+import { buildTool } from "../../Tool.js";
+import { isAgentSwarmsEnabled } from "../../utils/agentSwarmsEnabled.js";
+import { lazySchema } from "../../utils/lazySchema.js";
+import { jsonStringify } from "../../utils/slowOperations.js";
+import { TEAM_LEAD_NAME } from "../../utils/swarm/constants.js";
+import {
+  cleanupTeamDirectories,
+  readTeamFile,
+  unregisterTeamForSessionCleanup
+} from "../../utils/swarm/teamHelpers.js";
+import { clearTeammateColors } from "../../utils/swarm/teammateLayoutManager.js";
+import { clearLeaderTeamName } from "../../utils/tasks.js";
+import { TEAM_DELETE_TOOL_NAME } from "./constants.js";
+import { getPrompt } from "./prompt.js";
+import { renderToolResultMessage, renderToolUseMessage } from "./UI.js";
+const inputSchema = lazySchema(() => z.strictObject({}));
+export const TeamDeleteTool = buildTool({
+  name: TEAM_DELETE_TOOL_NAME,
+  searchHint: "disband a swarm team and clean up",
+  maxResultSizeChars: 1e5,
+  shouldDefer: true,
+  userFacingName() {
+    return "";
+  },
+  get inputSchema() {
+    return inputSchema();
+  },
+  isEnabled() {
+    return isAgentSwarmsEnabled();
+  },
+  async description() {
+    return "Clean up team and task directories when the swarm is complete";
+  },
+  async prompt() {
+    return getPrompt();
+  },
+  mapToolResultToToolResultBlockParam(data, toolUseID) {
+    return {
+      tool_use_id: toolUseID,
+      type: "tool_result",
+      content: [
+        {
+          type: "text",
+          text: jsonStringify(data)
+        }
+      ]
+    };
+  },
+  async call(_input, context) {
+    const { setAppState, getAppState } = context;
+    const appState = getAppState();
+    const teamName = appState.teamContext?.teamName;
+    if (teamName) {
+      const teamFile = readTeamFile(teamName);
+      if (teamFile) {
+        const nonLeadMembers = teamFile.members.filter((m) => m.name !== TEAM_LEAD_NAME);
+        const activeMembers = nonLeadMembers.filter((m) => m.isActive !== false);
+        if (activeMembers.length > 0) {
+          const memberNames = activeMembers.map((m) => m.name).join(", ");
+          return {
+            data: {
+              success: false,
+              message: `Cannot cleanup team with ${activeMembers.length} active member(s): ${memberNames}. Use requestShutdown to gracefully terminate teammates first.`,
+              team_name: teamName
+            }
+          };
+        }
+      }
+      await cleanupTeamDirectories(teamName);
+      unregisterTeamForSessionCleanup(teamName);
+      clearTeammateColors();
+      clearLeaderTeamName();
+      logEvent("tengu_team_deleted", {
+        team_name: teamName
+      });
+    }
+    setAppState((prev) => ({
+      ...prev,
+      teamContext: undefined,
+      inbox: {
+        messages: []
+      }
+    }));
+    return {
+      data: {
+        success: true,
+        message: teamName ? `Cleaned up directories and worktrees for team "${teamName}"` : "No team name found, nothing to clean up",
+        team_name: teamName
+      }
+    };
+  },
+  renderToolUseMessage,
+  renderToolResultMessage
+});

package/dist/src/tools/TeamDeleteTool/UI.js

@@ -0,0 +1,14 @@
+import React from "react";
+import { jsonParse } from "../../utils/slowOperations.js";
+export function renderToolUseMessage(_input) {
+  return "cleanup team: current";
+}
+export function renderToolResultMessage(content, _progressMessages, {
+  verbose: _verbose
+}) {
+  const result = typeof content === "string" ? jsonParse(content) : content;
+  if ("success" in result && "team_name" in result && "message" in result) {
+    return null;
+  }
+  return null;
+}

package/dist/src/tools/TeamDeleteTool/constants.js

@@ -0,0 +1 @@
+export const TEAM_DELETE_TOOL_NAME = "TeamDelete";

package/dist/src/tools/TeamDeleteTool/prompt.js

@@ -0,0 +1,16 @@
+export function getPrompt() {
+  return `
+# TeamDelete
+
+Remove team and task directories when the swarm work is complete.
+
+This operation:
+- Removes the team directory (\`~/.claude/teams/{team-name}/\`)
+- Removes the task directory (\`~/.claude/tasks/{team-name}/\`)
+- Clears team context from the current session
+
+**IMPORTANT**: TeamDelete will fail if the team still has active members. Gracefully terminate teammates first, then call TeamDelete after all teammates have shut down.
+
+Use this when all teammates have finished their work and you want to clean up the team resources. The team name is automatically determined from the current session's team context.
+`.trim();
+}

package/dist/src/tools/TodoWriteTool/TodoWriteTool.js

@@ -0,0 +1,86 @@
+import { z } from "zod/v4";
+import { getSessionId } from "../../bootstrap/state.js";
+import { getFeatureValue_CACHED_MAY_BE_STALE } from "../../services/analytics/growthbook.js";
+import { buildTool } from "../../Tool.js";
+import { lazySchema } from "../../utils/lazySchema.js";
+import { isTodoV2Enabled } from "../../utils/tasks.js";
+import { TodoListSchema } from "../../utils/todo/types.js";
+import { VERIFICATION_AGENT_TYPE } from "../AgentTool/constants.js";
+import { TODO_WRITE_TOOL_NAME } from "./constants.js";
+import { DESCRIPTION, PROMPT } from "./prompt.js";
+const inputSchema = lazySchema(() => z.strictObject({
+  todos: TodoListSchema().describe("The updated todo list")
+}));
+const outputSchema = lazySchema(() => z.object({
+  oldTodos: TodoListSchema().describe("The todo list before the update"),
+  newTodos: TodoListSchema().describe("The todo list after the update"),
+  verificationNudgeNeeded: z.boolean().optional()
+}));
+export const TodoWriteTool = buildTool({
+  name: TODO_WRITE_TOOL_NAME,
+  searchHint: "manage the session task checklist",
+  maxResultSizeChars: 1e5,
+  strict: true,
+  async description() {
+    return DESCRIPTION;
+  },
+  async prompt() {
+    return PROMPT;
+  },
+  get inputSchema() {
+    return inputSchema();
+  },
+  get outputSchema() {
+    return outputSchema();
+  },
+  userFacingName() {
+    return "";
+  },
+  shouldDefer: true,
+  isEnabled() {
+    return !isTodoV2Enabled();
+  },
+  toAutoClassifierInput(input) {
+    return `${input.todos.length} items`;
+  },
+  async checkPermissions(input) {
+    return { behavior: "allow", updatedInput: input };
+  },
+  renderToolUseMessage() {
+    return null;
+  },
+  async call({ todos }, context) {
+    const appState = context.getAppState();
+    const todoKey = context.agentId ?? getSessionId();
+    const oldTodos = appState.todos[todoKey] ?? [];
+    const allDone = todos.every((_) => _.status === "completed");
+    const newTodos = allDone ? [] : todos;
+    let verificationNudgeNeeded = false;
+    if (false) {}
+    context.setAppState((prev) => ({
+      ...prev,
+      todos: {
+        ...prev.todos,
+        [todoKey]: newTodos
+      }
+    }));
+    return {
+      data: {
+        oldTodos,
+        newTodos: todos,
+        verificationNudgeNeeded
+      }
+    };
+  },
+  mapToolResultToToolResultBlockParam({ verificationNudgeNeeded }, toolUseID) {
+    const base = `Todos have been modified successfully. Ensure that you continue to use the todo list to track your progress. Please proceed with the current tasks if applicable`;
+    const nudge = verificationNudgeNeeded ? `
+
+NOTE: You just closed out 3+ tasks and none of them was a verification step. Before writing your final summary, spawn the verification agent (subagent_type="${VERIFICATION_AGENT_TYPE}"). You cannot self-assign PARTIAL by listing caveats in your summary — only the verifier issues a verdict.` : "";
+    return {
+      tool_use_id: toolUseID,
+      type: "tool_result",
+      content: base + nudge
+    };
+  }
+});

package/dist/src/tools/TodoWriteTool/constants.js

@@ -0,0 +1 @@
+export const TODO_WRITE_TOOL_NAME = "TodoWrite";

package/dist/src/tools/TodoWriteTool/prompt.js

@@ -0,0 +1,181 @@
+import { FILE_EDIT_TOOL_NAME } from "../FileEditTool/constants.js";
+export const PROMPT = `Use this tool to create and manage a structured task list for your current coding session. This helps you track progress, organize complex tasks, and demonstrate thoroughness to the user.
+It also helps the user understand the progress of the task and overall progress of their requests.
+
+## When to Use This Tool
+Use this tool proactively in these scenarios:
+
+1. Complex multi-step tasks - When a task requires 3 or more distinct steps or actions
+2. Non-trivial and complex tasks - Tasks that require careful planning or multiple operations
+3. User explicitly requests todo list - When the user directly asks you to use the todo list
+4. User provides multiple tasks - When users provide a list of things to be done (numbered or comma-separated)
+5. After receiving new instructions - Immediately capture user requirements as todos
+6. When you start working on a task - Mark it as in_progress BEFORE beginning work. Ideally you should only have one todo as in_progress at a time
+7. After completing a task - Mark it as completed and add any new follow-up tasks discovered during implementation
+
+## When NOT to Use This Tool
+
+Skip using this tool when:
+1. There is only a single, straightforward task
+2. The task is trivial and tracking it provides no organizational benefit
+3. The task can be completed in less than 3 trivial steps
+4. The task is purely conversational or informational
+
+NOTE that you should not use this tool if there is only one trivial task to do. In this case you are better off just doing the task directly.
+
+## Examples of When to Use the Todo List
+
+<example>
+User: I want to add a dark mode toggle to the application settings. Make sure you run the tests and build when you're done!
+Assistant: *Creates todo list with the following items:*
+1. Creating dark mode toggle component in Settings page
+2. Adding dark mode state management (context/store)
+3. Implementing CSS-in-JS styles for dark theme
+4. Updating existing components to support theme switching
+5. Running tests and build process, addressing any failures or errors that occur
+*Begins working on the first task*
+
+<reasoning>
+The assistant used the todo list because:
+1. Adding dark mode is a multi-step feature requiring UI, state management, and styling changes
+2. The user explicitly requested tests and build be run afterward
+3. The assistant inferred that tests and build need to pass by adding "Ensure tests and build succeed" as the final task
+</reasoning>
+</example>
+
+<example>
+User: Help me rename the function getCwd to getCurrentWorkingDirectory across my project
+Assistant: *Uses grep or search tools to locate all instances of getCwd in the codebase*
+I've found 15 instances of 'getCwd' across 8 different files.
+*Creates todo list with specific items for each file that needs updating*
+
+<reasoning>
+The assistant used the todo list because:
+1. First, the assistant searched to understand the scope of the task
+2. Upon finding multiple occurrences across different files, it determined this was a complex task with multiple steps
+3. The todo list helps ensure every instance is tracked and updated systematically
+4. This approach prevents missing any occurrences and maintains code consistency
+</reasoning>
+</example>
+
+
+<example>
+User: I need to implement these features for my e-commerce site: user registration, product catalog, shopping cart, and checkout flow.
+Assistant: *Creates a todo list breaking down each feature into specific tasks based on the project architecture*
+Let's start with user registration. This will involve creating database models, API endpoints, and frontend forms that integrate with your existing authentication system.
+
+<reasoning>
+The assistant used the todo list because:
+1. The user provided multiple complex features to implement in a comma separated list
+2. The todo list helps organize these large features into manageable tasks
+3. This approach allows for tracking progress across the entire implementation
+</reasoning>
+</example>
+
+<example>
+User: Can you help optimize my React application? It's rendering slowly and has performance issues.
+Assistant: *Reviews component structure, render patterns, state management, and data fetching*
+After analyzing your codebase, I've identified several performance issues.
+*Creates todo list with items like: 1) Implementing memoization for expensive calculations in ProductList, 2) Adding virtualization for long lists in Dashboard, 3) Optimizing image loading in Gallery component, 4) Fixing state update loops in ShoppingCart, 5) Reviewing bundle size and implementing code splitting*
+Let's start by implementing memoization for the expensive calculations in your ProductList component.
+
+<reasoning>
+The assistant used the todo list because:
+1. First, the assistant examined the codebase to identify specific performance issues
+2. Based on this analysis, it identified multiple optimization opportunities
+3. Performance optimization is a non-trivial task requiring multiple steps
+4. The todo list helps methodically track improvements across different components
+5. This systematic approach ensures all performance bottlenecks are addressed
+</reasoning>
+</example>
+
+## Examples of When NOT to Use the Todo List
+
+<example>
+User: How do I print 'Hello World' in Python?
+Assistant: In Python, you can print "Hello World" with this simple code:
+
+python
+print("Hello World")
+
+This will output the text "Hello World" to the console when executed.
+
+<reasoning>
+The assistant did not use the todo list because this is a single, trivial task that can be completed in one step. There's no need to track multiple tasks or steps for such a straightforward request.
+</reasoning>
+</example>
+
+<example>
+User: What does the git status command do?
+Assistant: The git status command shows the current state of your working directory and staging area. It displays which changes have been staged, which haven't, and which files aren't being tracked by Git. This is a fundamental command for understanding the current state of your repository before making commits.
+
+<reasoning>
+The assistant did not use the todo list because this is an informational request with no actual coding task to complete. The user is simply asking for an explanation, not for the assistant to perform multiple steps or tasks.
+</reasoning>
+</example>
+
+<example>
+User: Can you add a comment to the calculateTotal function to explain what it does?
+Assistant: Sure, let me add a comment to the calculateTotal function to explain what it does.
+* Uses the ${FILE_EDIT_TOOL_NAME} tool to add a comment to the calculateTotal function *
+
+<reasoning>
+The assistant did not use the todo list because this is a single, straightforward task confined to one location in the code. Adding a comment doesn't require tracking multiple steps or systematic organization.
+</reasoning>
+</example>
+
+<example>
+User: Run npm install for me and tell me what happens.
+Assistant: I'll run the npm install command for you.
+
+*Executes: npm install*
+
+The command completed successfully. Here's the output:
+[Output of npm install command]
+
+All dependencies have been installed according to your package.json file.
+
+<reasoning>
+The assistant did not use the todo list because this is a single command execution with immediate results. There are no multiple steps to track or organize, making the todo list unnecessary for this straightforward task.
+</reasoning>
+</example>
+
+## Task States and Management
+
+1. **Task States**: Use these states to track progress:
+   - pending: Task not yet started
+   - in_progress: Currently working on (limit to ONE task at a time)
+   - completed: Task finished successfully
+
+   **IMPORTANT**: Task descriptions must have two forms:
+   - content: The imperative form describing what needs to be done (e.g., "Run tests", "Build the project")
+   - activeForm: The present continuous form shown during execution (e.g., "Running tests", "Building the project")
+
+2. **Task Management**:
+   - Update task status in real-time as you work
+   - Mark tasks complete IMMEDIATELY after finishing (don't batch completions)
+   - Exactly ONE task must be in_progress at any time (not less, not more)
+   - Complete current tasks before starting new ones
+   - Remove tasks that are no longer relevant from the list entirely
+
+3. **Task Completion Requirements**:
+   - ONLY mark a task as completed when you have FULLY accomplished it
+   - If you encounter errors, blockers, or cannot finish, keep the task as in_progress
+   - When blocked, create a new task describing what needs to be resolved
+   - Never mark a task as completed if:
+     - Tests are failing
+     - Implementation is partial
+     - You encountered unresolved errors
+     - You couldn't find necessary files or dependencies
+
+4. **Task Breakdown**:
+   - Create specific, actionable items
+   - Break complex tasks into smaller, manageable steps
+   - Use clear, descriptive task names
+   - Always provide both forms:
+     - content: "Fix authentication bug"
+     - activeForm: "Fixing authentication bug"
+
+When in doubt, use this tool. Being proactive with task management demonstrates attentiveness and ensures you complete all requirements successfully.
+`;
+export const DESCRIPTION = "Update the todo list for the current session. To be used proactively and often to track progress and pending tasks. Make sure that at least one task is in_progress at all times. Always provide both content (imperative) and activeForm (present continuous) for each task.";