foliko 1.1.88 → 1.1.89

package/.env.example

@@ -1,56 +1,56 @@
-# ========== AI Configuration ==========
-# 最大输出 tokens（影响 AI 回复长度）
-MAX_OUTPUT_TOKENS=8192
-# AI Provider: minimax, deepseek, openai, anthropic 等
-FOLIKO_PROVIDER=minimax
-
-# AI Model（如果未设置，使用 provider 默认值）
-# MiniMax: MiniMax-M2.7
-# DeepSeek: deepseek-chat, deepseek-coder 等
-FOLIKO_MODEL=MiniMax-M2.7
-
-# API Base URL（如果未设置，使用 provider 默认值）
-# MiniMax: https://api.minimaxi.com/v1
-# DeepSeek: https://api.deepseek.com/v1
-FOLIKO_BASE_URL=https://api.minimaxi.com/v1
-
-# API Key（通用，如果未设置则尝试 provider 专用 key）
-FOLIKO_API_KEY=sk-your-api-key
-
-# Provider 专用 API Key（可选，如果 FOLIKO_API_KEY 未设置则使用这些）
-DEEPSEEK_API_KEY=sk-your-deepseek-api-key
-MINIMAX_API_KEY=sk-your-minimax-api-key
-
-# ========== Email Configuration ==========
-# SMTP Settings (for sending emails)
-SMTP_HOST=smtp.gmail.com
-SMTP_PORT=587
-SMTP_SECURE=false
-SMTP_USER=your-email@gmail.com
-SMTP_PASS=your-app-password
-
-# IMAP Settings (for reading emails)
-IMAP_HOST=imap.gmail.com
-IMAP_PORT=993
-IMAP_USER=your-email@gmail.com
-IMAP_PASS=your-app-password
-
-# Default sender email address
-FROM_EMAIL=your-email@gmail.com
-
-# ========== Telegram Bot (optional) ==========
-TELEGRAM_BOT_TOKEN=your-telegram-bot-token
-
-# ========== Feishu Bot (optional) ==========
-FEISHU_APP_ID=cli_xxxxxxxxxxx
-FEISHU_APP_SECRET=app_secret
-
-# ========== Web Server (optional) ==========
-# Web 服务端口，默认 8088
-WEB_PORT=3000
-
-# Web 服务主机，默认 127.0.0.1
-WEB_HOST=127.0.0.1
-
-# 公网访问的 base URL（用于生成 webhook URL 等），不设置则使用 host:port，最好部署在docker中可以暴露自定义域名
-WEB_BASE_URL=https://your-domain.com
+# ========== AI Configuration ==========
+# 最大输出 tokens（影响 AI 回复长度）
+MAX_OUTPUT_TOKENS=8192
+# AI Provider: minimax, deepseek, openai, anthropic 等
+FOLIKO_PROVIDER=minimax
+
+# AI Model（如果未设置，使用 provider 默认值）
+# MiniMax: MiniMax-M2.7
+# DeepSeek: deepseek-chat, deepseek-coder 等
+FOLIKO_MODEL=MiniMax-M2.7
+
+# API Base URL（如果未设置，使用 provider 默认值）
+# MiniMax: https://api.minimaxi.com/v1
+# DeepSeek: https://api.deepseek.com/v1
+FOLIKO_BASE_URL=https://api.minimaxi.com/v1
+
+# API Key（通用，如果未设置则尝试 provider 专用 key）
+FOLIKO_API_KEY=sk-your-api-key
+
+# Provider 专用 API Key（可选，如果 FOLIKO_API_KEY 未设置则使用这些）
+DEEPSEEK_API_KEY=sk-your-deepseek-api-key
+MINIMAX_API_KEY=sk-your-minimax-api-key
+
+# ========== Email Configuration ==========
+# SMTP Settings (for sending emails)
+SMTP_HOST=smtp.gmail.com
+SMTP_PORT=587
+SMTP_SECURE=false
+SMTP_USER=your-email@gmail.com
+SMTP_PASS=your-app-password
+
+# IMAP Settings (for reading emails)
+IMAP_HOST=imap.gmail.com
+IMAP_PORT=993
+IMAP_USER=your-email@gmail.com
+IMAP_PASS=your-app-password
+
+# Default sender email address
+FROM_EMAIL=your-email@gmail.com
+
+# ========== Telegram Bot (optional) ==========
+TELEGRAM_BOT_TOKEN=your-telegram-bot-token
+
+# ========== Feishu Bot (optional) ==========
+FEISHU_APP_ID=cli_xxxxxxxxxxx
+FEISHU_APP_SECRET=app_secret
+
+# ========== Web Server (optional) ==========
+# Web 服务端口，默认 8088
+WEB_PORT=3000
+
+# Web 服务主机，默认 127.0.0.1
+WEB_HOST=127.0.0.1
+
+# 公网访问的 base URL（用于生成 webhook URL 等），不设置则使用 host:port，最好部署在docker中可以暴露自定义域名
+WEB_BASE_URL=https://your-domain.com

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "foliko",
-  "version": "1.1.88",
+  "version": "1.1.89",
   "description": "简约的插件化 Agent 框架",
   "main": "src/index.js",
   "type": "commonjs",
@@ -81,7 +81,7 @@
     "node-schedule": "^2.1.1",
     "node-telegram-bot-api": "^0.67.0",
     "nodemailer": "^6.10.0",
-    "pino": "^10.3.1",
+    "pino": "7",
     "pino-pretty": "^13.1.3",
     "qrcode-terminal": "^0.12.0",
     "remove-markdown": "^0.6.3",

package/skills/find-skills/SKILL.md

@@ -1,133 +1,133 @@
----
-name: find-skills
-description: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
----
-
-# Find Skills
-
-This skill helps you discover and install skills from the open agent skills ecosystem.
-
-## When to Use This Skill
-
-Use this skill when the user:
-
-- Asks "how do I do X" where X might be a common task with an existing skill
-- Says "find a skill for X" or "is there a skill for X"
-- Asks "can you do X" where X is a specialized capability
-- Expresses interest in extending agent capabilities
-- Wants to search for tools, templates, or workflows
-- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
-
-## What is the Skills CLI?
-
-The Skills CLI (`npx skills`) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.
-
-**Key commands:**
-
-- `npx skills find [query]` - Search for skills interactively or by keyword
-- `npx skills add <package>` - Install a skill from GitHub or other sources
-- `npx skills check` - Check for skill updates
-- `npx skills update` - Update all installed skills
-
-**Browse skills at:** https://skills.sh/
-
-## How to Help Users Find Skills
-
-### Step 1: Understand What They Need
-
-When a user asks for help with something, identify:
-
-1. The domain (e.g., React, testing, design, deployment)
-2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
-3. Whether this is a common enough task that a skill likely exists
-
-### Step 2: Search for Skills
-
-Run the find command with a relevant query:
-
-```bash
-npx skills find [query]
-```
-
-For example:
-
-- User asks "how do I make my React app faster?" → `npx skills find react performance`
-- User asks "can you help me with PR reviews?" → `npx skills find pr review`
-- User asks "I need to create a changelog" → `npx skills find changelog`
-
-The command will return results like:
-
-```
-Install with npx skills add <owner/repo@skill>
-
-vercel-labs/agent-skills@vercel-react-best-practices
-└ https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
-```
-
-### Step 3: Present Options to the User
-
-When you find relevant skills, present them to the user with:
-
-1. The skill name and what it does
-2. The install command they can run
-3. A link to learn more at skills.sh
-
-Example response:
-
-```
-I found a skill that might help! The "vercel-react-best-practices" skill provides
-React and Next.js performance optimization guidelines from Vercel Engineering.
-
-To install it:
-npx skills add vercel-labs/agent-skills@vercel-react-best-practices
-
-Learn more: https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
-```
-
-### Step 4: Offer to Install
-
-If the user wants to proceed, you can install the skill for them:
-
-```bash
-npx skills add <owner/repo@skill> -g -y
-```
-
-The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.
-
-## Common Skill Categories
-
-When searching, consider these common categories:
-
-| Category        | Example Queries                          |
-| --------------- | ---------------------------------------- |
-| Web Development | react, nextjs, typescript, css, tailwind |
-| Testing         | testing, jest, playwright, e2e           |
-| DevOps          | deploy, docker, kubernetes, ci-cd        |
-| Documentation   | docs, readme, changelog, api-docs        |
-| Code Quality    | review, lint, refactor, best-practices   |
-| Design          | ui, ux, design-system, accessibility     |
-| Productivity    | workflow, automation, git                |
-
-## Tips for Effective Searches
-
-1. **Use specific keywords**: "react testing" is better than just "testing"
-2. **Try alternative terms**: If "deploy" doesn't work, try "deployment" or "ci-cd"
-3. **Check popular sources**: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`
-
-## When No Skills Are Found
-
-If no relevant skills exist:
-
-1. Acknowledge that no existing skill was found
-2. Offer to help with the task directly using your general capabilities
-3. Suggest the user could create their own skill with `npx skills init`
-
-Example:
-
-```
-I searched for skills related to "xyz" but didn't find any matches.
-I can still help you with this task directly! Would you like me to proceed?
-
-If this is something you do often, you could create your own skill:
-npx skills init my-xyz-skill
-```
+---
+name: find-skills
+description: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
+---
+
+# Find Skills
+
+This skill helps you discover and install skills from the open agent skills ecosystem.
+
+## When to Use This Skill
+
+Use this skill when the user:
+
+- Asks "how do I do X" where X might be a common task with an existing skill
+- Says "find a skill for X" or "is there a skill for X"
+- Asks "can you do X" where X is a specialized capability
+- Expresses interest in extending agent capabilities
+- Wants to search for tools, templates, or workflows
+- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
+
+## What is the Skills CLI?
+
+The Skills CLI (`npx skills`) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.
+
+**Key commands:**
+
+- `npx skills find [query]` - Search for skills interactively or by keyword
+- `npx skills add <package>` - Install a skill from GitHub or other sources
+- `npx skills check` - Check for skill updates
+- `npx skills update` - Update all installed skills
+
+**Browse skills at:** https://skills.sh/
+
+## How to Help Users Find Skills
+
+### Step 1: Understand What They Need
+
+When a user asks for help with something, identify:
+
+1. The domain (e.g., React, testing, design, deployment)
+2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
+3. Whether this is a common enough task that a skill likely exists
+
+### Step 2: Search for Skills
+
+Run the find command with a relevant query:
+
+```bash
+npx skills find [query]
+```
+
+For example:
+
+- User asks "how do I make my React app faster?" → `npx skills find react performance`
+- User asks "can you help me with PR reviews?" → `npx skills find pr review`
+- User asks "I need to create a changelog" → `npx skills find changelog`
+
+The command will return results like:
+
+```
+Install with npx skills add <owner/repo@skill>
+
+vercel-labs/agent-skills@vercel-react-best-practices
+└ https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
+```
+
+### Step 3: Present Options to the User
+
+When you find relevant skills, present them to the user with:
+
+1. The skill name and what it does
+2. The install command they can run
+3. A link to learn more at skills.sh
+
+Example response:
+
+```
+I found a skill that might help! The "vercel-react-best-practices" skill provides
+React and Next.js performance optimization guidelines from Vercel Engineering.
+
+To install it:
+npx skills add vercel-labs/agent-skills@vercel-react-best-practices
+
+Learn more: https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
+```
+
+### Step 4: Offer to Install
+
+If the user wants to proceed, you can install the skill for them:
+
+```bash
+npx skills add <owner/repo@skill> -g -y
+```
+
+The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.
+
+## Common Skill Categories
+
+When searching, consider these common categories:
+
+| Category        | Example Queries                          |
+| --------------- | ---------------------------------------- |
+| Web Development | react, nextjs, typescript, css, tailwind |
+| Testing         | testing, jest, playwright, e2e           |
+| DevOps          | deploy, docker, kubernetes, ci-cd        |
+| Documentation   | docs, readme, changelog, api-docs        |
+| Code Quality    | review, lint, refactor, best-practices   |
+| Design          | ui, ux, design-system, accessibility     |
+| Productivity    | workflow, automation, git                |
+
+## Tips for Effective Searches
+
+1. **Use specific keywords**: "react testing" is better than just "testing"
+2. **Try alternative terms**: If "deploy" doesn't work, try "deployment" or "ci-cd"
+3. **Check popular sources**: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`
+
+## When No Skills Are Found
+
+If no relevant skills exist:
+
+1. Acknowledge that no existing skill was found
+2. Offer to help with the task directly using your general capabilities
+3. Suggest the user could create their own skill with `npx skills init`
+
+Example:
+
+```
+I searched for skills related to "xyz" but didn't find any matches.
+I can still help you with this task directly! Would you like me to proceed?
+
+If this is something you do often, you could create your own skill:
+npx skills init my-xyz-skill
+```

package/src/core/agent-chat.js

@@ -475,7 +475,7 @@ class AgentChatHandler extends EventEmitter {
       if (!this._aiClient) {
         throw new Error('AI client not configured.');
       }
-      this._validateToolCalls(messages);
+
       const systemPrompt = framework.getSystemPrompt();
       //await fs.promises.writeFile(`.${sessionId}_systemPrompt.md`, systemPrompt); // 调试用：保存系统提示词
       const tools = this._getAITools(aiTool);
@@ -580,7 +580,7 @@ class AgentChatHandler extends EventEmitter {
           usage: usageData,
         });
       }
-      this._validateToolCalls(messages);
+
       // yield usage 数据，让 UI 层能直接获取
       yield {
         type: 'usage',
@@ -658,7 +658,7 @@ class AgentChatHandler extends EventEmitter {
       if (this._thinkingMode) {
         delete apiOptions.temperature;
       }
-      this._validateToolCalls(messages);
+
       const agent = new ToolLoopAgent({
         model: this._aiClient,
         instructions: systemPrompt,
@@ -699,7 +699,7 @@ class AgentChatHandler extends EventEmitter {
       messages.push(...result.response.messages);
       const userMsg = messages[messages.length - result.response.messages.length - 1];
       this.emit('message', { content: result.text, sessionId: sessionId, userMessage: userMsg });
-      this._validateToolCalls(messages);
+
       return {
         success: true,
         message: cleanResponse(result.text || ''),

package/website_v2/styles/animations.css

@@ -1,8 +1,8 @@
-/* Foliko v2 - Animations */
-    @keyframes fadeInUp { from { opacity: 0; transform: translateY(30px); } to { opacity: 1; transform: translateY(0); } }
-    @keyframes fadeIn { from { opacity: 0; } to { opacity: 1; } }
-    @keyframes glow { 0%, 100% { opacity: 0.4; transform: translateX(-50%) scale(1); } 50% { opacity: 0.7; transform: translateX(-50%) scale(1.1); } }
-    @keyframes pulse { 0%, 100% { opacity: 1; transform: scale(1); } 50% { opacity: 0.5; transform: scale(1.2); } }
-    .reveal { opacity: 0; transform: translateY(30px); transition: all 0.6s cubic-bezier(0.4, 0, 0.2, 1); }
-    .reveal.visible { opacity: 1; transform: translateY(0); }
+/* Foliko v2 - Animations */
+    @keyframes fadeInUp { from { opacity: 0; transform: translateY(30px); } to { opacity: 1; transform: translateY(0); } }
+    @keyframes fadeIn { from { opacity: 0; } to { opacity: 1; } }
+    @keyframes glow { 0%, 100% { opacity: 0.4; transform: translateX(-50%) scale(1); } 50% { opacity: 0.7; transform: translateX(-50%) scale(1.1); } }
+    @keyframes pulse { 0%, 100% { opacity: 1; transform: scale(1); } 50% { opacity: 0.5; transform: scale(1.2); } }
+    .reveal { opacity: 0; transform: translateY(30px); transition: all 0.6s cubic-bezier(0.4, 0, 0.2, 1); }
+    .reveal.visible { opacity: 1; transform: translateY(0); }