lynkr 7.2.5 → 8.0.0

package/ROUTER_COMPARISON.md

@@ -1,173 +0,0 @@
-# Comparison: claude-code-router vs Lynkr Proxy
-
-## Architecture Differences
-
-**claude-code-router:**
-- **CLI-first design** - `ccr` commands for interactive model switching
-- **Request interceptor** - Sits between Claude Code CLI and LLM providers
-- **Transformer pipeline** - Middleware system for request/response modification
-- **Built with Fastify** (web framework)
-- **TypeScript + esbuild** compilation
-- **Web UI** for configuration
-
-**Lynkr:**
-- **HTTP proxy server** - Express-based API endpoint
-- **Provider abstraction** - Unified interface for 7+ providers
-- **Long-term memory system** (Titans-inspired)
-- **Built with Express** (web framework)
-- **Pure JavaScript** (no compilation)
-- **Token optimization focus** (6 optimization phases)
-
----
-
-## Key Feature Comparison
-
-| Feature | claude-code-router | Lynkr | Winner |
-|---------|-------------------|-------|--------|
-| **Dynamic Model Switching** | ✅ Runtime `/model` command | ❌ Static .env config | 🏆 Router |
-| **Routing Logic** | ✅ Context-aware (think/background/long-context) | ❌ Simple provider fallback only | 🏆 Router |
-| **Custom Router Scripts** | ✅ JavaScript-based routing rules | ❌ No custom routing | 🏆 Router |
-| **Web UI** | ✅ `ccr ui` browser interface | ❌ No UI | 🏆 Router |
-| **Long-Term Memory** | ❌ None | ✅ Vector search + surprise scoring | 🏆 Lynkr |
-| **Token Optimization** | ⚠️ Basic (long-context detection) | ✅ 6 phases (smart tools, compression, etc.) | 🏆 Lynkr |
-| **Smart Tool Selection** | ❌ None | ✅ Heuristic-based (just implemented) | 🏆 Lynkr |
-| **History Compression** | ❌ None | ✅ Automatic + token budget enforcement | 🏆 Lynkr |
-| **Prompt Caching** | ✅ Via transformer | ✅ Built-in | 🟰 Tie |
-| **Provider Count** | 6 (OpenRouter, DeepSeek, Ollama, Gemini, etc.) | 7 (Databricks, Azure, OpenAI, OpenRouter, Ollama, llama.cpp) | 🟰 Tie |
-| **Tool Enhancement** | ✅ `enhancetool` transformer | ❌ Basic passthrough | 🏆 Router |
-| **GitHub Actions** | ✅ CI/CD integration | ❌ None | 🏆 Router |
-| **Logging** | ✅ Rotating file logs | ✅ Pino logger | 🟰 Tie |
-| **TypeScript** | ✅ Full TypeScript | ❌ JavaScript only | 🏆 Router |
-
----
-
-## Improvements for Lynkr (Ranked by Impact)
-
-### 🔴 **Critical - High Impact, High Value**
-
-#### 1. Dynamic Model Switching via `/model` Command
-- **What**: Allow users to switch models mid-conversation without restarting server
-- **Why**: Router's killer feature - flexibility without configuration edits
-- **Implementation**: Add chat command parser, session-level model overrides
-- **Effort**: Medium (2-3 days)
-
-#### 2. Context-Aware Routing (Background/Think/Long-Context)
-- **What**: Automatically route requests based on context type
-- **Why**: Cost optimization + performance (cheap models for background, reasoning models for planning)
-- **Example**:
-  - Background tasks → `gpt-4o-mini` ($0.15/1M)
-  - Planning/thinking → `o1-preview` (reasoning model)
-  - Long context (>60k tokens) → `claude-sonnet-4` (200k context)
-- **Effort**: Medium (3-4 days)
-
-#### 3. Custom Router Scripts (JavaScript-based)
-- **What**: Let users define routing logic in JavaScript
-- **Why**: Ultimate flexibility - enterprise users need custom rules
-- **Example**:
-  ```javascript
-  // router.js
-  module.exports = function(request) {
-    if (request.tools.length > 5) return 'gpt-4o'; // Complex task
-    if (request.content.includes('urgent')) return 'databricks'; // Fast provider
-    return 'openrouter/nova-lite'; // Default cheap
-  }
-  ```
-- **Effort**: High (5-7 days)
-
-#### 4. Web UI for Configuration
-- **What**: Browser-based interface at `http://localhost:8081/ui`
-- **Why**: Non-technical users can't edit .env files
-- **Features**: Model selection, provider config, logs viewer, cost tracking
-- **Effort**: High (7-10 days)
-
-### 🟡 **High Impact, Medium Complexity**
-
-#### 5. Tool Enhancement Transformer
-- **What**: Add error tolerance and response buffering to tool calls
-- **Why**: Prevents cascade failures when tools return malformed JSON
-- **Example**: Retry tool calls with exponential backoff, validate tool outputs
-- **Effort**: Low (1-2 days)
-
-#### 6. Request/Response Transformer Pipeline
-- **What**: Middleware system to modify requests/responses per provider
-- **Why**: Provider-specific quirks (Azure needs different format, Ollama strips thinking blocks)
-- **Current**: Hardcoded in client adapters
-- **Improved**: Pluggable transformer chain
-- **Effort**: Medium (3-4 days)
-
-#### 7. Token-Based Auto-Routing
-- **What**: Switch to high-context models when input exceeds threshold
-- **Why**: Prevent truncation errors, automatic upgrade
-- **Example**: Request >100k tokens → auto-switch from `gpt-4o` (128k) to `claude-sonnet-4` (200k)
-- **Effort**: Low (1-2 days) - you already have token counting
-
-### 🟢 **Nice to Have - Lower Priority**
-
-#### 8. GitHub Actions Integration
-- **What**: Trigger Claude Code workflows in CI/CD
-- **Why**: Automated code reviews, documentation generation
-- **Use Case**: PR opens → Claude reviews code → posts comments
-- **Effort**: Medium (3-4 days)
-
-#### 9. CLI Commands (`lynkr model`, `lynkr ui`)
-- **What**: Interactive terminal commands for management
-- **Why**: Better DX than editing .env and restarting
-- **Effort**: Medium (2-3 days)
-
-#### 10. Rotating File Logs
-- **What**: Auto-rotate logs by size/date (keep last 7 days)
-- **Why**: Prevent disk bloat in production
-- **Current**: Pino logs to stdout only
-- **Effort**: Low (1 day) - use `pino-rotating-file-stream`
-
-#### 11. LRU Caching for Responses
-- **What**: Cache identical requests for X minutes
-- **Why**: Save money on repeated queries
-- **Example**: User asks "what is 2+2?" 3 times → only 1 LLM call
-- **Effort**: Low (1-2 days)
-
-#### 12. TypeScript Migration
-- **What**: Convert codebase to TypeScript
-- **Why**: Type safety, better IDE support, fewer runtime errors
-- **Effort**: Very High (15-20 days) - 87 files to convert
-
----
-
-## Unique Strengths of Lynkr (Don't Lose These!)
-
-1. **Long-term memory system** - Router doesn't have this
-2. **Smart tool selection** - Just implemented, very valuable
-3. **6-phase token optimization** - Industry-leading
-4. **History compression** - Automatic context management
-5. **7 providers** - Broader support than Router
-6. **Hybrid routing** - Ollama + cloud fallback
-
----
-
-## Recommended Implementation Order
-
-### Phase 1: Quick Wins (1-2 weeks)
-1. Token-based auto-routing
-2. Tool enhancement transformer
-3. Rotating file logs
-4. LRU caching
-
-### Phase 2: Game Changers (3-4 weeks)
-5. Dynamic model switching via `/model` command
-6. Context-aware routing (background/think/long-context)
-7. Request/Response transformer pipeline
-
-### Phase 3: Enterprise Features (4-6 weeks)
-8. Custom router scripts
-9. Web UI
-10. CLI commands
-11. GitHub Actions integration
-
-### Phase 4: Long-Term (Optional)
-12. TypeScript migration
-
----
-
-## Bottom Line
-
-Router excels at **flexibility and user experience** (dynamic switching, routing logic, Web UI). Lynkr excels at **optimization and intelligence** (memory, token optimization, smart tools). Merging the best of both would create the ultimate Claude Code proxy.