@easbot/agent 0.2.0 → 0.2.2

package/dist/assets/txt/tool/apply_patch.txt

@@ -19,15 +19,35 @@ Example patch:
 *** Add File: hello.txt
 +Hello world
 *** Update File: src/app.py
-*** Move to: src/main.py
-@@ def greet():
+@@ -1,4 +1,4 @@
+ def greet():
 -print("Hi")
 +print("Hello, world!")
+ def farewell():
 *** Delete File: obsolete.txt
 *** End Patch
 ```
 
-It is important to remember:
+Unified Diff Format for Update File:
+
+```
+@@ -<old_start>,<old_count> +<new_start>,<new_count> @@ [optional context]
+ <context line (unchanged)>
+-<line to delete>
++<new line to add>
+ <context line (unchanged)>
+```
+
+Key rules:
+- Lines starting with `+` are added
+- Lines starting with `-` are deleted
+- Lines starting with space are context (must match file content exactly)
+- The `@@ -...,+... @@` header MUST include line ranges
+- Context lines must match the original file content exactly
+- Use `*** Move to: <new_path>` after Update File for renaming
+
+Common mistakes to avoid:
+- DO NOT use `@@ context_line` without line numbers
+- DO NOT use `@@` alone without ranges
+- Context lines MUST match the actual file content
 
-- You must include a header with your intended action (Add/Delete/Update)
-- You must prefix new lines with `+` even when creating a new file

package/dist/assets/txt/tool/codebase.txt

@@ -3,13 +3,15 @@ Use this tool to search and analyze code structure in the codebase knowledge gra
 **search** — Use this operation to find code by query:
 - Set operation="search"
 - Provide query string to search code content
-- Use astType to filter by code element type
-- Use language to filter by programming language
+- Use astType to filter by code element type (e.g., class_declaration, function_declaration)
+- Use language to filter by programming language (e.g., ts, py, rs)
 - Returns code snippets with related edges when available
 
 **queryEdges** — Use this operation to explore code relationships:
 - Set operation="queryEdges"
 - Provide nodeId to get node information and all connected relations
+- IMPORTANT: nodeId must be in full format: `language:filepath:type:name`
+- Example: `ts:E:/work/apps/eas/project/src/session.ts:class_declaration:Session`
 - Returns node details and incoming/outgoing edges (shown as [in] or [out])
 - Useful for understanding code dependencies and navigation
 
@@ -21,8 +23,20 @@ Use this tool to search and analyze code structure in the codebase knowledge gra
 **language** — Programming languages:
 `ts`, `tsx`, `js`, `jsx`, `py`, `rs`, `go`, `c`, `cpp`, `csharp`, `java`, `scala`, `ruby`, `php`, `zig`
 
-Use this tool when you need to:
-- Understand code structure and implementation details
-- Find specific functions, classes, or code patterns
-- Explore relationships between code elements
-- Navigate code dependencies
+## Usage Examples
+
+```
+# Search for Session class definitions
+codebase(operation="search" query="Session" astType="class_declaration")
+
+# Search for Python functions only
+codebase(operation="search" query="handler" language="py" astType="function_declaration")
+
+# Query edges of a specific node (copy nodeId from search results)
+codebase(operation="queryEdges" nodeId="<paste nodeId from search results>")
+```
+
+## Important Notes
+
+- When searching, the nodeId is returned in results (e.g., `node id=ts:E:/path/to/file.ts:class_declaration:Session`)
+- Use queryEdges to explore relationships between code elements

package/dist/assets/txt/tool/task.txt

@@ -1,60 +1,48 @@
-Launch a new agent to handle complex, multistep tasks autonomously.
-
-Available agent types and the tools they have access to:
-{agents}
-
-When using the Task tool, you must specify a subagent_type parameter to select which agent type to use.
-
-When to use the Task tool:
-- When you are instructed to execute custom slash commands. Use the Task tool with the slash command invocation as the entire prompt. The slash command can take arguments. For example: Task(description="Check the file", prompt="/check-file path/to/file.py")
-
-When NOT to use the Task tool:
-- If you want to read a specific file path, use the Read or Glob tool instead of the Task tool, to find the match more quickly
-- If you are searching for a specific class definition like "class Foo", use the Glob tool instead, to find the match more quickly
-- If you are searching for code within a specific file or set of 2-3 files, use the Read tool instead of the Task tool, to find the match more quickly
-- Other tasks that are not related to the agent descriptions above
-
-
-Usage notes:
-1. Launch multiple agents concurrently whenever possible, to maximize performance; to do that, use a single message with multiple tool uses
-2. When the agent is done, it will return a single message back to you. The result returned by the agent is not visible to the user. To show the user the result, you should send a text message back to the user with a concise summary of the result. The output includes a task_id you can reuse later to continue the same subagent session.
-3. Each agent invocation starts with a fresh context unless you provide task_id to resume the same subagent session (which continues with its previous messages and tool outputs). When starting fresh, your prompt should contain a highly detailed task description for the agent to perform autonomously and you should specify exactly what information the agent should return back to you in its final and only message to you.
-4. The agent's outputs should generally be trusted
-5. Clearly tell the agent whether you expect it to write code or just to do research (search, file reads, web fetches, etc.), since it is not aware of the user's intent. Tell it how to verify its work if possible (e.g., relevant test commands).
-6. If the agent description mentions that it should be used proactively, then you should try your best to use it without the user having to ask for it first. Use your judgement.
-
-Example usage (NOTE: The agents below are fictional examples for illustration only - use the actual agents listed above):
-
-<example_agent_descriptions>
-"code-reviewer": use this agent after you are done writing a significant piece of code
-"greeting-responder": use this agent when to respond to user greetings with a friendly joke
-</example_agent_description>
-
-<example>
-user: "Please write a function that checks if a number is prime"
-assistant: Sure let me write a function that checks if a number is prime
-assistant: First let me use the Write tool to write a function that checks if a number is prime
-assistant: I'm going to use the Write tool to write the following code:
-<code>
-function isPrime(n) {
-  if (n <= 1) return false
-  for (let i = 2; i * i <= n; i++) {
-    if (n % i === 0) return false
-  }
-  return true
-}
-</code>
-<commentary>
-Since a significant piece of code was written and the task was completed, now use the code-reviewer agent to review the code
-</commentary>
-assistant: Now let me use the code-reviewer agent to review the code
-assistant: Uses the Task tool to launch the code-reviewer agent
-</example>
-
-<example>
-user: "Hello"
-<commentary>
-Since the user is greeting, use the greeting-responder agent to respond with a friendly joke
-</commentary>
-assistant: "I'm going to use the Task tool to launch the with the greeting-responder agent"
-</example>
+Task management tool - create, query, continue, or delete background tasks.
+
+## Operations
+
+### create
+Create a new background task. Task will run asynchronously and results will be injected when complete.
+- description: Short task description
+- prompt: Detailed task instructions for the subagent
+- subagent_type: Type of specialized agent to use
+
+### query
+Query task status or list all tasks for current session.
+- taskId (optional): Task ID to query. Omit to list all tasks.
+
+### continue
+Continue a failed or pending task.
+- taskId: Task ID to continue
+
+### delete
+Delete a task by ID.
+- taskId: Task ID to delete
+
+### agents
+List available agents for task execution (excludes hidden agents).
+- No parameters required
+
+## Concurrency
+
+Multiple tasks can run concurrently (max 5). Use query to check task status.
+
+## Examples
+
+```
+task(operation="create" description="Review PR" prompt="Review code changes in the PR" subagent_type="code-reviewer")
+task(operation="query")
+task(operation="query" taskId="task_xxx")
+task(operation="continue" taskId="task_xxx")
+task(operation="delete" taskId="task_xxx")
+task(operation="agents")
+```
+
+## Notes
+
+- Tasks run asynchronously in the background
+- Multiple tasks can run concurrently
+- Results are injected into the conversation when complete
+- Use taskId to track and query specific tasks
+- Completed or running tasks cannot be restarted, use query to check status