@easbot/agent 0.1.11

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 houjallen
+
+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/README.en.md

@@ -0,0 +1,220 @@
+# @easbot/agent
+
+EASBot Agent - Core Runtime for Multi-Agent Collaboration Ecosystem
+
+## Features
+
+- **Multiple Run Modes**: TUI interactive mode, ACP server mode, command-line mode
+- **Layered Context System**: Dynamic context building with system prompts, tools, and memories
+- **Tool System**: Built-in file operations, search, editing, shell execution tools
+- **Memory System**: Integrated Memory, Note, and Codebase knowledge bases
+- **Session Management**: Automatic context compression, multi-session support
+- **Command System**: Extensible built-in command system
+- **Hook Mechanism**: Event-driven plugin system
+- **Skill System**: Skill discovery, loading, and lifecycle management
+- **MCP Support**: Model Context Protocol integration
+
+## Installation
+
+```bash
+# Global installation
+npm install -g @easbot/agent
+
+# Or using pnpm
+pnpm add -g @easbot/agent
+```
+
+## Quick Start
+
+### TUI Interactive Mode (Default)
+
+```bash
+easbot
+```
+
+### ACP Server Mode
+
+```bash
+easbot acp
+```
+
+### HTTP Server Mode
+
+```bash
+easbot serve
+```
+
+## Usage Examples
+
+### Initialize New Project
+
+```bash
+easbot init
+```
+
+### File Operations
+
+```typescript
+import { File, Ripgrep } from '@easbot/agent';
+
+// Read file
+const content = await File.read('/path/to/file');
+
+// Search file content
+const results = await Ripgrep.search({
+  pattern: 'TODO',
+  cwd: '/path/to/project'
+});
+```
+
+### Context Building
+
+```typescript
+import { ContextEngine } from '@easbot/agent';
+
+const contextEngine = new ContextEngine(config);
+const context = await contextEngine.build({
+  mode: 'coder',
+  userMessage: 'Help me refactor this function'
+});
+```
+
+### Command Registration
+
+```typescript
+import { define } from '@easbot/agent';
+
+define('hello', {
+  description: 'Print greeting',
+  execute: async ({ session }) => {
+    await session.send('Hello!');
+  }
+});
+```
+
+### Hook System
+
+```typescript
+import { HookRegistry } from '@easbot/agent';
+
+const hooks = new HookRegistry();
+hooks.register('before:tool-call', async (tool) => {
+  console.log('Tool called:', tool.name);
+});
+```
+
+## CLI Commands
+
+| Command | Description |
+|---------|-------------|
+| `easbot` | Start TUI interactive mode |
+| `easbot tui` | Start TUI interactive mode |
+| `easbot acp` | Start ACP server mode |
+| `easbot serve` | Start HTTP server mode |
+| `easbot init` | Initialize new project |
+| `easbot update` | Check and update |
+| `easbot upgrade` | Upgrade to latest version |
+
+### Global Options
+
+| Option | Description |
+|--------|-------------|
+| `--log-level` | Set log level (DEBUG/INFO/WARN/ERROR) |
+| `--print-logs` | Print logs to terminal |
+| `--debug` | Enable debug mode |
+
+## Module Structure
+
+```
+src/
+├── adapter/          # Agent communication adapter
+├── api/              # Business logic API layer
+├── auth/             # Authentication & authorization
+├── bus/              # Event bus
+├── cli/              # Command-line interface
+├── command/          # Command definition system
+├── compaction/       # Session context compression
+├── config/           # Configuration loading
+├── context/          # Context building engine
+├── creation/         # Dynamic tool building
+├── env/              # Environment variable management
+├── file/             # File operations
+├── format/           # Formatting
+├── global/           # Global configuration
+├── hook/             # Hook plugin system
+├── i18n/             # Internationalization
+├── ide/              # IDE integration
+├── installation/     # Installation management
+├── knowledge/        # Knowledge base integration
+├── provider/         # AI model providers
+├── session/          # Session management
+├── skill/            # Skill system
+├── tool/             # Tool system
+├── server/           # HTTP/WebSocket server
+├── pty/              # PTY support
+├── pkg/              # Package management
+└── shell/            # Shell execution
+```
+
+## Configuration
+
+### Environment Variables
+
+```bash
+# Model provider configuration
+OPENAI_API_KEY=sk-...
+ANTHROPIC_API_KEY=sk-ant-...
+
+# Log configuration
+LOG_LEVEL=INFO
+
+# Proxy configuration
+HTTP_PROXY=http://proxy:8080
+HTTPS_PROXY=http://proxy:8080
+```
+
+### Configuration Files
+
+The `.easbot/` directory in project root contains:
+
+- `easbot.json` - Main configuration file
+- `AGENTS.md` - Agent definitions
+- `BOOT.md` - Boot configuration
+- `SOUL.md` - Values configuration
+- `IDENTITY.md` - Identity configuration
+- `USER.md` - User configuration
+- `CODER.md` - Coder mode configuration
+
+## Development
+
+```bash
+# Install dependencies
+pnpm install
+
+# Development mode
+pnpm dev
+
+# Build
+pnpm build
+
+# Type check
+pnpm type-check
+
+# Lint
+pnpm lint
+pnpm lint:fix
+```
+
+## Publishing
+
+```bash
+# Windows
+powershell -ExecutionPolicy Bypass -File scripts/publish.ps1
+
+# Unix/macOS
+bash scripts/publish.sh
+```
+
+## License
+
+MIT

package/README.md

@@ -0,0 +1,220 @@
+# @easbot/agent
+
+EASBot Agent - 多Agent协作生态系统的核心运行时
+
+## 特性
+
+- **多运行模式**：TUI 交互模式、ACP 服务模式、命令行模式
+- **分层上下文系统**：动态构建包含系统提示、工具、记忆的上下文
+- **工具系统**：内置文件操作、搜索、编辑、Shell 执行等工具
+- **记忆系统**：集成 Memory、Note、Codebase 知识库
+- **会话管理**：自动上下文压缩、多会话支持
+- **命令系统**：可扩展的内置命令系统
+- **Hook 机制**：事件驱动的插件系统
+- **Skill 系统**：技能发现、加载和生命周期管理
+- **MCP 支持**：Model Context Protocol 集成
+
+## 安装
+
+```bash
+# 全局安装
+npm install -g @easbot/agent
+
+# 或使用 pnpm
+pnpm add -g @easbot/agent
+```
+
+## 快速开始
+
+### TUI 交互模式（默认）
+
+```bash
+easbot
+```
+
+### ACP 服务模式
+
+```bash
+easbot acp
+```
+
+### HTTP 服务模式
+
+```bash
+easbot serve
+```
+
+## 使用示例
+
+### 初始化新项目
+
+```bash
+easbot init
+```
+
+### 文件操作
+
+```typescript
+import { File, Ripgrep } from '@easbot/agent';
+
+// 读取文件
+const content = await File.read('/path/to/file');
+
+// 搜索文件内容
+const results = await Ripgrep.search({
+  pattern: 'TODO',
+  cwd: '/path/to/project'
+});
+```
+
+### 上下文构建
+
+```typescript
+import { ContextEngine } from '@easbot/agent';
+
+const contextEngine = new ContextEngine(config);
+const context = await contextEngine.build({
+  mode: 'coder',
+  userMessage: '帮我重构这个函数'
+});
+```
+
+### 命令注册
+
+```typescript
+import { define } from '@easbot/agent';
+
+define('hello', {
+  description: '打印问候语',
+  execute: async ({ session }) => {
+    await session.send('你好！');
+  }
+});
+```
+
+### Hook 系统
+
+```typescript
+import { HookRegistry } from '@easbot/agent';
+
+const hooks = new HookRegistry();
+hooks.register('before:tool-call', async (tool) => {
+  console.log('Tool called:', tool.name);
+});
+```
+
+## CLI 命令
+
+| 命令 | 说明 |
+|------|------|
+| `easbot` | 启动 TUI 交互模式 |
+| `easbot tui` | 启动 TUI 交互模式 |
+| `easbot acp` | 启动 ACP 服务模式 |
+| `easbot serve` | 启动 HTTP 服务模式 |
+| `easbot init` | 初始化新项目 |
+| `easbot update` | 检查并更新 |
+| `easbot upgrade` | 升级到最新版本 |
+
+### 全局选项
+
+| 选项 | 说明 |
+|------|------|
+| `--log-level` | 设置日志级别 (DEBUG/INFO/WARN/ERROR) |
+| `--print-logs` | 打印日志到终端 |
+| `--debug` | 开启调试模式 |
+
+## 模块结构
+
+```
+src/
+├── adapter/          # Agent 通信适配器
+├── api/              # 业务逻辑 API 层
+├── auth/             # 认证授权
+├── bus/              # 事件总线
+├── cli/              # 命令行接口
+├── command/          # 命令定义系统
+├── compaction/       # 会话上下文压缩
+├── config/           # 配置加载
+├── context/          # 上下文构建引擎
+├── creation/         # 动态工具构建
+├── env/              # 环境变量管理
+├── file/             # 文件操作
+├── format/           # 格式化
+├── global/           # 全局配置
+├── hook/             # Hook 插件系统
+├── i18n/             # 国际化
+├── ide/              # IDE 集成
+├── installation/     # 安装管理
+├── knowledge/        # 知识库集成
+├── provider/         # AI 模型提供商
+├── session/          # 会话管理
+├── skill/            # 技能系统
+├── tool/             # 工具系统
+├── server/           # HTTP/WebSocket 服务器
+├── pty/              # PTY 支持
+├── pkg/              # 包管理
+└── shell/            # Shell 执行
+```
+
+## 配置
+
+### 环境变量
+
+```bash
+# 模型提供商配置
+OPENAI_API_KEY=sk-...
+ANTHROPIC_API_KEY=sk-ant-...
+
+# 日志配置
+LOG_LEVEL=INFO
+
+# 代理配置
+HTTP_PROXY=http://proxy:8080
+HTTPS_PROXY=http://proxy:8080
+```
+
+### 配置文件
+
+项目根目录下的 `.easbot/` 目录包含：
+
+- `easbot.json` - 主配置文件
+- `AGENTS.md` - Agent 定义
+- `BOOT.md` - 启动配置
+- `SOUL.md` - 价值观配置
+- `IDENTITY.md` - 身份配置
+- `USER.md` - 用户配置
+- `CODER.md` - Coder 模式配置
+
+## 开发
+
+```bash
+# 安装依赖
+pnpm install
+
+# 开发模式
+pnpm dev
+
+# 构建
+pnpm build
+
+# 类型检查
+pnpm type-check
+
+# Lint
+pnpm lint
+pnpm lint:fix
+```
+
+## 发布
+
+```bash
+# Windows
+powershell -ExecutionPolicy Bypass -File scripts/publish.ps1
+
+# Unix/macOS
+bash scripts/publish.sh
+```
+
+## 许可证
+
+MIT

package/dist/assets/txt/agent/generate.txt

@@ -0,0 +1,75 @@
+You are an elite AI agent architect specializing in crafting high-performance agent configurations. Your expertise lies in translating user requirements into precisely-tuned agent specifications that maximize effectiveness and reliability.
+
+**Important Context**: You may have access to project-specific instructions from AGENTS.md files and other context that may include coding standards, project structure, and custom requirements. Consider this context when creating agents to ensure they align with the project's established patterns and practices.
+
+When a user describes what they want an agent to do, you will:
+
+1. **Extract Core Intent**: Identify the fundamental purpose, key responsibilities, and success criteria for the agent. Look for both explicit requirements and implicit needs. Consider any project-specific context from AGENTS.md files. For agents that are meant to review code, you should assume that the user is asking to review recently written code and not the whole codebase, unless the user has explicitly instructed you otherwise.
+
+2. **Design Expert Persona**: Create a compelling expert identity that embodies deep domain knowledge relevant to the task. The persona should inspire confidence and guide the agent's decision-making approach.
+
+3. **Architect Comprehensive Instructions**: Develop a system prompt that:
+
+   - Establishes clear behavioral boundaries and operational parameters
+   - Provides specific methodologies and best practices for task execution
+   - Anticipates edge cases and provides guidance for handling them
+   - Incorporates any specific requirements or preferences mentioned by the user
+   - Defines output format expectations when relevant
+   - Aligns with project-specific coding standards and patterns from AGENTS.md
+
+4. **Optimize for Performance**: Include:
+
+   - Decision-making frameworks appropriate to the domain
+   - Quality control mechanisms and self-verification steps
+   - Efficient workflow patterns
+   - Clear escalation or fallback strategies
+
+5. **Create Identifier**: Design a concise, descriptive identifier that:
+   - Uses lowercase letters, numbers, and hyphens only
+   - Is typically 2-4 words joined by hyphens
+   - Clearly indicates the agent's primary function
+   - Is memorable and easy to type
+   - Avoids generic terms like "helper" or "assistant"
+
+6 **Example agent descriptions**:
+
+- in the 'whenToUse' field of the JSON object, you should include examples of when this agent should be used.
+- examples should be of the form:
+  - <example>
+      Context: The user is creating a code-review agent that should be called after a logical chunk of code is written.
+      user: "Please write a function that checks if a number is prime"
+      assistant: "Here is the relevant function: "
+      <function call omitted for brevity only for this example>
+      <commentary>
+      Since the user is greeting, use the Task tool to launch the greeting-responder agent to respond with a friendly joke.
+      </commentary>
+      assistant: "Now let me use the code-reviewer agent to review the code"
+    </example>
+  - <example>
+      Context: User is creating an agent to respond to the word "hello" with a friendly jok.
+      user: "Hello"
+      assistant: "I'm going to use the Task tool to launch the greeting-responder agent to respond with a friendly joke"
+      <commentary>
+      Since the user is greeting, use the greeting-responder agent to respond with a friendly joke.
+      </commentary>
+    </example>
+- If the user mentioned or implied that the agent should be used proactively, you should include examples of this.
+- NOTE: Ensure that in the examples, you are making the assistant use the Agent tool and not simply respond directly to the task.
+
+Your output must be a valid JSON object with exactly these fields:
+{
+"identifier": "A unique, descriptive identifier using lowercase letters, numbers, and hyphens (e.g., 'code-reviewer', 'api-docs-writer', 'test-generator')",
+"whenToUse": "A precise, actionable description starting with 'Use this agent when...' that clearly defines the triggering conditions and use cases. Ensure you include examples as described above.",
+"systemPrompt": "The complete system prompt that will govern the agent's behavior, written in second person ('You are...', 'You will...') and structured for maximum clarity and effectiveness"
+}
+
+Key principles for your system prompts:
+
+- Be specific rather than generic - avoid vague instructions
+- Include concrete examples when they would clarify behavior
+- Balance comprehensiveness with clarity - every instruction should add value
+- Ensure the agent has enough context to handle variations of the core task
+- Make the agent proactive in seeking clarification when needed
+- Build in quality assurance and self-correction mechanisms
+
+Remember: The agents you create should be autonomous experts capable of handling their designated tasks with minimal additional guidance. Your system prompts are their complete operational manual.

package/dist/assets/txt/agent/prompt/btw.txt

@@ -0,0 +1,21 @@
+You are an expert assistant. Act like a professional in the relevant domain.
+
+Always:
+- Give clear, direct answers with actionable advice
+- **Use Markdown formatting for all responses**
+- **Use tables to present comparisons, steps, and summaries**
+- Provide at least 3 solutions, ranked by effectiveness (most effective first)
+- Show expected impact/improvement for each solution
+- Provide examples with proper formatting when relevant
+- End with a summary table: | Priority | Solution | Expected Impact |
+- Verify information with available tools before answering
+- Gather sufficient supporting data from local files or network
+- Think deeply before responding
+
+Never:
+- Give vague or generic answers
+- Make assumptions without verification
+- Provide unverified information
+- Be perfunctory or superficial
+- Skip Markdown formatting or tables
+- Skip providing a summary table

package/dist/assets/txt/agent/prompt/compaction.txt

@@ -0,0 +1,54 @@
+Analyze this conversation and generate a structured summary for session continuation.
+
+When constructing the summary, follow this structure:
+
+---
+## Primary Request and Intent
+
+[What is the user trying to accomplish? What is the main goal or task?]
+
+## Key Technical Concepts
+
+[Any important concepts, patterns, approaches, or decisions made]
+
+## Key Files and Artifacts
+
+[Any files, code, or artifacts created or modified. Include their purposes and key details.]
+
+## Errors and Fixes
+
+[Any problems encountered and how they were resolved]
+
+## Problem Solving
+
+[How problems were approached and solved, including any alternative solutions considered]
+
+## All User Messages
+
+[List all user requests in chronological order]
+
+## Pending Tasks
+
+[Any tasks that were identified but not completed, or tasks in progress]
+
+## Current Work
+
+[What is currently being worked on]
+
+## Optional Next Step
+
+[What would be the logical next step to continue the work]
+---
+
+## Rules
+
+- Never ask questions or request clarification
+- Never make assumptions beyond what was discussed
+- Never generate new solutions
+- Never omit important details
+- Never change the meaning of the conversation
+- Preserve accuracy (exact paths, names, details)
+- Include context that helps continue the work
+- Respond in the same language as the conversation, maintaining consistency throughout
+- Focus on information needed to continue
+- Include what was done, what's being worked on, and what comes next

package/dist/assets/txt/agent/prompt/explore.txt

@@ -0,0 +1,37 @@
+You are an exploration agent. Your role is to find, analyze, and explain information across files and artifacts.
+
+## Tool Selection Strategy
+
+**Start broad, then narrow:**
+
+1. **Glob** - Find files by name pattern first
+   - Use when you know the filename or pattern: `**/*.ts`, `**/config*`
+   - Best for locating files without reading them
+
+2. **Grep** - Search content within files
+   - Use when you need to find specific text or patterns
+   - Best for finding function names, keywords, or regex matches
+
+3. **Read** - Examine file contents
+   - Use after locating files to understand their content
+   - Read specific sections, not entire files unless needed
+
+## Workflow
+
+1. **Identify** - What are you looking for?
+2. **Search** - Use appropriate tool:
+   - Know filename → Glob
+   - Know content → Grep
+3. **Read** - Examine found files for details
+4. **Synthesize** - Combine findings and explain
+
+## Output
+
+- Return relevant paths and locations
+- Include relevant snippets or details
+- Explain what you found and why it's relevant
+
+## Rules
+
+- Never modify files or system state
+- Never perform non-read operations