agentic-flow 1.9.0 → 1.9.2

package/agentic-flow/AGENT-BOOSTER-STATUS.md

@@ -1,292 +0,0 @@
-# Agent Booster Integration Status
-
-## Executive Summary
-
-**Status**: ⚠️ **Partially Integrated** - Works via MCP Server, Not CLI
-
-Agent Booster is successfully integrated into agentic-flow@1.4.2's **MCP server** (for Claude Desktop/Cursor), but is **NOT** accessible via the CLI `--agent` mode.
-
-## What Works ✅
-
-### 1. MCP Server Integration (Claude Desktop/Cursor)
-
-**Confirmed via MCP Protocol Test:**
-```bash
-node /tmp/node_modules/agentic-flow/dist/mcp/standalone-stdio.js
-```
-
-**Output:**
-```
-✅ Registered 10 tools (7 agentic-flow + 3 agent-booster):
-   • agent_booster_edit_file (352x faster code editing) ⚡ NEW
-   • agent_booster_batch_edit (multi-file refactoring) ⚡ NEW
-   • agent_booster_parse_markdown (LLM output parsing) ⚡ NEW
-```
-
-**How Users Access:**
-1. Configure Claude Desktop `claude_desktop_config.json`:
-   ```json
-   {
-     "mcpServers": {
-       "agentic-flow": {
-         "command": "npx",
-         "args": ["-y", "agentic-flow", "mcp"]
-       }
-     }
-   }
-   ```
-
-2. Tools appear in Claude Desktop automatically
-
-3. Use tools naturally in conversation:
-   ```
-   User: "Use agent_booster_edit_file to convert var to const in src/utils.js"
-   Claude: [calls MCP tool with exact code replacement]
-   ```
-
-**Performance:**
-- Exact code replacements: 9-15ms (vs 6,738ms with LLM)
-- Cost: $0.00 (vs ~$0.001 per LLM edit)
-- Confidence threshold: ≥70% to apply, <70% falls back to LLM
-
-### 2. Standalone CLI
-
-**agent-booster@0.1.1 works with correct JSON input:**
-```bash
-echo '{"code":"var x = 1;","edit":"const x = 1;"}' | npx agent-booster apply --language javascript
-# Output: {"success":true,"confidence":0.571,"latency":11,"strategy":"insert_after"}
-```
-
-## What Doesn't Work ❌
-
-### 1. CLI `--agent` Mode
-
-**Test Results (from user):**
-```bash
-npx agentic-flow@1.4.2 --agent coder --task "convert var to const in test.js"
-```
-
-**Behavior:**
-- ❌ Uses standard LLM Edit tool (NOT Agent Booster)
-- ❌ Takes 26 seconds (standard speed, not 57x faster)
-- ❌ No Agent Booster MCP tools visible in this mode
-- ✅ BUT: Still works correctly using LLM (100% success rate)
-
-**Why:**
-The `--agent` mode bypasses MCP tools entirely. Agent Booster tools are only available via the MCP server protocol.
-
-### 2. Vague Instructions
-
-Agent Booster correctly rejects vague instructions (this is **by design**):
-
-```bash
-# ❌ Vague instruction (rejected)
-echo '{"code":"var x = 1;","edit":"convert to const"}' | npx agent-booster apply
-# Result: Low confidence or error
-
-# ✅ Exact code (accepted)
-echo '{"code":"var x = 1;","edit":"const x = 1;"}' | npx agent-booster apply
-# Result: Success with 57% confidence
-```
-
-## Architecture
-
-### Tool Availability Matrix
-
-| Mode | Agent Booster Available? | Performance | Use Case |
-|------|-------------------------|-------------|----------|
-| **MCP Server** (Claude Desktop/Cursor) | ✅ Yes (3 tools) | 728x faster | IDE integration, exact edits |
-| **CLI `--agent` mode** | ❌ No | Standard LLM speed | Direct CLI usage, complex tasks |
-| **Standalone CLI** | ✅ Yes (direct) | 728x faster | Scripting, automation |
-
-### Why This Design?
-
-1. **MCP Server** = Tool-based interface for IDEs
-   - Agent Booster is a "tool" that Claude can call
-   - Works with exact code replacements
-   - Automatic LLM fallback for low confidence
-
-2. **CLI `--agent` mode** = Direct agent execution
-   - No MCP protocol involved
-   - Uses standard LLM edits
-   - Better for complex reasoning tasks
-
-3. **Standalone CLI** = Direct pattern matching
-   - No LLM involved at all
-   - Pure WASM execution
-   - For automation/scripting
-
-## User Guidance
-
-### When to Use Each Mode
-
-**Use MCP Server (Claude Desktop/Cursor):**
-- ✅ IDE-based development
-- ✅ Exact code replacements with fallback
-- ✅ Want 728x faster edits for mechanical changes
-- ✅ Mixed workflow (some exact edits, some reasoning)
-
-**Use CLI `--agent` mode:**
-- ✅ Terminal/script-based workflows
-- ✅ Complex refactoring requiring reasoning
-- ✅ Vague instructions ("improve", "add feature")
-- ✅ Don't need MCP integration
-
-**Use Standalone agent-booster CLI:**
-- ✅ Automation scripts
-- ✅ CI/CD pipelines
-- ✅ Exact code replacements only
-- ✅ No LLM needed at all
-
-## Performance Claims
-
-### Original Claims vs Reality
-
-| Claim | Reality | Status |
-|-------|---------|--------|
-| 57x-728x faster | ✅ True for MCP tools (9-15ms vs 6.7s) | ✅ Verified |
-| $0 cost | ✅ True for exact replacements | ✅ Verified |
-| Works in CLI | ⚠️ Only via MCP server, not `--agent` mode | ⚠️ Partial |
-| 3 MCP tools | ✅ All present in MCP server | ✅ Verified |
-
-### Corrected Claims
-
-**For MCP Server Users (Claude Desktop/Cursor):**
-- ✅ 728x faster for exact code replacements (9ms vs 6.7s)
-- ✅ $0 cost for mechanical edits
-- ✅ Automatic LLM fallback for complex tasks
-- ✅ 3 working MCP tools
-
-**For CLI Users (`--agent` mode):**
-- ❌ Agent Booster NOT available
-- ✅ Standard LLM performance (26s for var→const)
-- ✅ 100% success rate with LLM reasoning
-- ✅ Better for complex tasks anyway
-
-## Configuration
-
-### Claude Desktop Setup
-
-1. **Install agentic-flow:**
-   ```bash
-   npm install -g agentic-flow@1.4.2
-   ```
-
-2. **Configure MCP server** (`~/Library/Application Support/Claude/claude_desktop_config.json`):
-   ```json
-   {
-     "mcpServers": {
-       "agentic-flow": {
-         "command": "npx",
-         "args": ["-y", "agentic-flow", "mcp"]
-       }
-     }
-   }
-   ```
-
-3. **Restart Claude Desktop**
-
-4. **Verify tools:**
-   - Open Claude Desktop
-   - Look for hammer icon (tools available)
-   - Type: "What MCP tools are available?"
-   - Should see: agent_booster_edit_file, agent_booster_batch_edit, agent_booster_parse_markdown
-
-### Usage Examples
-
-**Example 1: Simple var → const**
-```
-User: Use agent_booster_edit_file to convert var to const in src/utils.js
-
-Claude: I'll apply that edit using Agent Booster...
-[Calls agent_booster_edit_file with exact code replacement]
-
-Result: ✅ Successfully edited (11ms, 57% confidence)
-```
-
-**Example 2: Low Confidence → LLM Fallback**
-```
-User: Use agent_booster_edit_file to add error handling to src/api.js
-
-Claude: I'll try Agent Booster first...
-[Calls agent_booster_edit_file, gets low confidence]
-
-Agent Booster confidence too low (42%). Falling back to LLM...
-[Uses agentic_flow_agent with coder to add error handling]
-
-Result: ✅ Successfully added error handling (24s, LLM reasoning)
-```
-
-## Testing
-
-### MCP Server Test
-
-```bash
-cd /tmp
-npm install agentic-flow@1.4.2
-
-# Test MCP server directly
-node node_modules/agentic-flow/dist/mcp/standalone-stdio.js
-# Should show: ✅ Registered 10 tools (7 agentic-flow + 3 agent-booster)
-```
-
-### Standalone CLI Test
-
-```bash
-# Test agent-booster CLI
-echo '{"code":"var x = 1;","edit":"const x = 1;"}' | npx agent-booster@0.1.1 apply --language javascript
-
-# Expected: {"success":true,"confidence":0.571,"latency":11,"strategy":"insert_after"}
-```
-
-### CLI Agent Test
-
-```bash
-# Create test file
-echo "var x = 1;" > test.js
-
-# Test CLI agent mode (uses LLM, not Agent Booster)
-npx agentic-flow@1.4.2 --agent coder --task "convert var to const in test.js"
-
-# Expected: 26s execution, 100% success, uses LLM Edit tool
-```
-
-## Recommendations
-
-### For Documentation
-
-1. **Update README** to clarify:
-   - Agent Booster is for **MCP server** (Claude Desktop/Cursor)
-   - CLI `--agent` mode uses standard LLM (NOT Agent Booster)
-   - Performance claims apply to MCP tools only
-
-2. **Add setup instructions** for Claude Desktop
-
-3. **Document confidence thresholds** and LLM fallback
-
-### For Users
-
-1. **Use Claude Desktop/Cursor** if you want Agent Booster performance
-2. **Use CLI `--agent` mode** for complex reasoning tasks
-3. **Use standalone agent-booster** for automation scripts
-4. **Don't expect CLI `--agent` mode to use Agent Booster** - it's not designed to
-
-## Conclusion
-
-**Agent Booster integration in agentic-flow@1.4.2 is working correctly** - it's just not available where you might expect it.
-
-The integration is **MCP-first** (for IDEs), not **CLI-first**. This is actually a good design choice because:
-
-- MCP tools work well with exact code replacements
-- CLI `--agent` mode works better with LLM reasoning
-- Users get the best tool for each use case
-
-**Status**: ✅ **Working as Designed** (but documentation needs clarification)
-
----
-
-**Package Versions:**
-- agentic-flow: v1.4.2
-- agent-booster: v0.1.1
-
-**Last Updated:** 2025-10-08

package/agentic-flow/CHANGELOG-v1.3.0.md

@@ -1,120 +0,0 @@
-# Changelog - v1.3.0
-
-## Release Date: October 7, 2025
-
-## 🎉 Major Features
-
-### Tool Emulation Architecture (Phase 2)
-Complete implementation of tool emulation system for models without native function calling support.
-
-**Key Features:**
-- ✅ Automatic model capability detection
-- ✅ ReAct and Prompt-based emulation strategies
-- ✅ User-facing emulation messages at 3 levels
-- ✅ Zero breaking changes - 100% backward compatible
-- ✅ 15/15 regression tests passing
-
-**Supported Models:**
-- Native tool support: DeepSeek Chat, Claude 3.5, GPT-4, Llama 3.3, Qwen 2.5 Coder, Mistral Small
-- Emulation required: Mistral 7B, Llama 2, Gemma 7B
-
-### Default Model Update
-Changed default OpenRouter model from Llama 3.1 8B to **DeepSeek Chat**:
-- ✅ Native tool support (no emulation needed)
-- ✅ 128K context window (vs 32K)
-- ✅ Cost-effective at $0.14/M tokens
-- ✅ Eliminates context overflow errors in Claude Code interactive mode
-
-## 🐛 Bug Fixes
-
-### Critical: Claude SDK Model Override
-Fixed issue where Claude Agent SDK was sending Claude model IDs to OpenRouter, causing "model not found" errors.
-
-**Solution:**
-- Automatically override SDK Claude requests to use CLI-specified model
-- Prevents errors when using OpenRouter with non-Claude models
-- Maintains compatibility with all providers
-
-## 📝 Changes
-
-### Tool Emulation Messages
-Added user-facing messages at 3 levels:
-1. **Proxy Initialization**: Shows when model lacks native tool support
-2. **Proxy Startup**: Displays emulation strategy and expected reliability
-3. **Agent Execution**: Informs about tool handling method
-
-Example output for Mistral 7B:
-```
-⚙️  Detected: Model lacks native tool support
-🔧 Using REACT emulation pattern
-📊 Expected reliability: 70-85%
-
-⚙️  Tool Emulation: REACT pattern
-📊 Note: This model uses prompt-based tool emulation
-   Tools are handled by Claude Agent SDK (limited to SDK tools)
-```
-
-### Files Modified
-- `src/cli-proxy.ts` - Added emulation messages, updated default model
-- `src/proxy/anthropic-to-openrouter.ts` - Added model override logic, emulation routing
-- `src/cli/claude-code-wrapper.ts` - Updated default model
-- `src/agents/claudeAgent.ts` - Updated default model
-- `src/utils/modelCapabilities.ts` - Created (Phase 1)
-- `src/proxy/tool-emulation.ts` - Created (Phase 1)
-
-## 🧪 Testing
-
-### Regression Tests: 15/15 PASS
-- Tool emulation files exist
-- Integration verified in cli-proxy and anthropic-to-openrouter
-- Gemini proxy remains isolated
-- TypeScript compilation succeeds
-- Model capability detection working
-- No tool name rewriting
-- Tool schemas unchanged
-- Backward compatibility verified
-
-### Manual Testing Results
-- ✅ DeepSeek (native tools): Works perfectly, no emulation messages
-- ✅ Mistral 7B (emulation): Works correctly, emulation messages appear
-- ✅ Claude Code interactive mode: No context errors
-- ✅ Claude Code non-interactive mode: Executes correctly
-- ✅ Agent execution: Both model types work
-
-## 📦 Migration Guide
-
-### For Users
-No migration needed! This release is 100% backward compatible.
-
-**To use new default model (DeepSeek Chat):**
-```bash
-npx agentic-flow claude-code --provider openrouter
-```
-
-**To use emulation with non-tool models:**
-```bash
-npx agentic-flow --agent coder --task "Your task" \
-  --provider openrouter \
-  --model "mistralai/mistral-7b-instruct"
-```
-
-### For Developers
-If you've set `COMPLETION_MODEL` in `.env`, it will override the new default.
-
-To explicitly use DeepSeek Chat:
-```bash
-export COMPLETION_MODEL="deepseek/deepseek-chat"
-```
-
-## 🔗 Related Issues
-- Closes #8 - Tool Emulation Phase 2 Integration
-
-## 🙏 Credits
-- Tool emulation architecture design
-- Phase 2 integration implementation
-- Model capability detection system
-- Comprehensive testing and validation
-
----
-
-**Full Changelog**: https://github.com/ruvnet/agentic-flow/compare/v1.2.7...v1.3.0