@agiflowai/agent-cli 0.0.9 → 0.1.0

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.1.0
+New:
+- New CLI app built with ink.
+
+## 0.0.9
+Add:
+- Support WorkUnit execution
+
 ## 0.0.9
 Update:
 - Improve Claude Code tool permissions detection.

package/README.md

@@ -6,10 +6,6 @@
 
 @agiflowai/agent-cli - Command-line interface for connecting and managing AI agents (Claude Code, Gemini) with Agiflow remotely.
 
-**Note**:
-- For `agent-cli claude` and `agent-cli router` you don't need to authenticate with Agiflow server.
-- Use `agent-cli claude --standalone` to run Claude Code locally without any backend connection.
-
 **🔗 Related Project**: Check out the [AgiFlow AI Code Toolkit](https://github.com/AgiFlow/aicode-toolkit) - an open-source collection of AI development tools and utilities.  
 
 ## Quick Start
@@ -26,281 +22,16 @@ npm install @agiflowai/agent-cli
 
 ### Available Commands
 
-The CLI provides three main commands:
+The CLI provides two main commands:
 
-#### 1. `agent-cli connect` - Connect Daemon
+#### 1. `agent-cli daemon` - Connect Daemon
 Connect your local machine to the Agiflow platform to receive remote commands.
 
 ```bash
-# Basic connection
-agent-cli connect
-
-# With custom server URL
-agent-cli connect --server-url wss://your-server.com
-
-# With verbose logging
-agent-cli connect --verbose
-```
-
-**Options:**
-- `-u, --server-url <url>` - WebSocket server URL to connect to
-- `--api-url <url>` - HTTP API base URL for daemon registration
-- `-v, --verbose` - Enable verbose logging
-- `--reconnect-interval <ms>` - Reconnection interval in milliseconds (default: 5000)
-- `--unique-instance` - Create unique daemon instance
-
-#### 2. `agent-cli claude` - Launch Claude Agent
-Launch a Claude Code agent with full functionality.
-
-```bash
-# Basic Claude agent launch in standalone mode (no backend)
-agent-cli claude --standalone
-
-# With backend connection (requires session ID)
-agent-cli claude --agent-session-id your-session-id
-
-# With custom alias for easy identification
-agent-cli claude \
-  --agent-session-id your-session-id \
-  --alias "my-dev-session"
-
-# With custom configuration
-agent-cli claude \
-  --agent-session-id your-session-id \
-  --server-url wss://your-server.com \
-  --working-directory /path/to/project \
-  --verbose
-
-# With LLM routing to GPT-5
-agent-cli claude \
-  --llm-provider chatgpt \
-  --llm-model gpt-5 \
-  --alias "gpt5-experiment"
-
-# Standalone mode (no backend connection)
-agent-cli claude --standalone --verbose
-```
-
-**Options:**
-- `-s, --server-url <url>` - WebSocket server URL
-- `-a, --api-url <url>` - HTTP API URL
-- `-k, --api-key <key>` - API key for authentication
-- `-o, --organization-id <id>` - Organization ID
-- `-i, --agent-session-id <id>` - **Required** Agent session ID
-- `-p, --claude-path <path>` - Path to Claude executable (default: 'claude')
-- `-w, --working-directory <dir>` - Working directory (default: current directory)
-- `-c, --agent-config <json>` - Agent configuration as JSON string
-- `--args <args...>` - Additional arguments to pass to Claude
-- `-v, --verbose` - Enable verbose logging
-- `--alias <alias>` - Custom session alias for easy identification
-- `--standalone` - Run in standalone mode without backend connection
-
-**LLM Routing Options:**
-- `--llm-provider <provider>` - LLM provider to route requests to (e.g., `chatgpt`, `openai`)
-- `--llm-model <model>` - LLM model to use (e.g., `gpt-5`, `gpt-5-codex`)
-
-**Note:** LLM routing configuration is saved to `~/.agiflow/sessions.json` and can be changed later using the `agent-cli router` command without restarting the agent.
-
-##### Standalone Mode
-
-Run Claude Code agent locally without connecting to the Agiflow backend server. This is useful for:
-- Development and testing
-- Running in environments without backend access
-- Privacy-focused local-only usage
-
-**Usage:**
-
-```bash
-# Explicit standalone mode
-agent-cli claude --standalone
-
-# Standalone mode with verbose logging
-agent-cli claude --standalone --verbose
-
-# Standalone mode with custom working directory
-agent-cli claude --standalone --working-directory /path/to/project
-```
-
-**How It Works:**
-
-When `--standalone` is enabled:
-- ✅ Claude Code launches normally with full functionality
-- ✅ All local features work (file operations, code analysis, etc.)
-- ❌ No WebSocket connection to Agiflow backend
-- ❌ No remote session management
-- ❌ No backend authentication required
-
-**Automatic Standalone Detection:**
-
-If no server URL is configured (via `--server-url` or environment variables), the agent automatically runs in standalone mode even without the `--standalone` flag.
-
-##### Running Claude with ChatGPT/OpenAI
-
-You can route Claude Code requests to ChatGPT/OpenAI using the LLM routing feature. This allows you to use GPT models while keeping the Claude Code interface.
-
-**Prerequisites:**
-
-1. **Authenticate with Codex CLI** (required for ChatGPT access):
-   ```bash
-   # Install Codex CLI
-   npm install -g @openai/codex
-
-   # Authenticate (opens browser for OAuth login)
-   codex auth login
-   ```
-
-   This stores your ChatGPT credentials in `~/.codex/auth.json`
-
-**Usage Examples:**
-
-```bash
-# Start with default Claude (no routing)
-agent-cli claude --alias "claude-session"
-
-# Start with GPT-5 routing
-agent-cli claude \
-  --alias "gpt5-session" \
-  --llm-provider chatgpt \
-  --llm-model gpt-5
-
-# Start with GPT-5 Codex
-agent-cli claude \
-  --alias "codex-session" \
-  --llm-provider chatgpt \
-  --llm-model gpt-5-codex
+agent-cli daemon
 ```
 
-**How It Works:**
-
-When routing is enabled:
-1. Claude Code requests are intercepted before reaching Anthropic's API
-2. Requests are transformed from Claude Messages API format → ChatGPT Responses API format
-3. The request is sent to ChatGPT with proper authentication (via Codex CLI)
-4. ChatGPT's streaming response is transformed back to Claude's format
-5. Claude Code receives responses as if they came from Anthropic
-
-**Supported Models:**
-
-- `gpt-5` - GPT-5 with reasoning (supports reasoning effort levels)
-- `gpt-5-codex` - GPT-5 optimized for coding tasks
-- More models may be added in the future
-
-**Dynamic Model Switching:**
-
-You can change the LLM routing configuration for an active session without restarting using the `agent-cli router` command (see below).
-
-#### 3. `agent-cli router` - Manage LLM Routing
-
-Manage LLM routing configuration for active Claude sessions. This allows you to switch between different LLM models without restarting your agent.
-
-```bash
-# Configure routing for a session (interactive)
-agent-cli router
-
-# Clear all session routing configurations
-agent-cli router --clear
-
-# With verbose logging
-agent-cli router --verbose
-```
-
-**Options:**
-- `-v, --verbose` - Enable verbose logging
-- `--clear` - Clear all session routing configurations
-
-**Interactive Workflow:**
-
-1. **Select a session** - The command shows all active sessions with their current routing:
-   ```
-   ? Select a session to configure routing:
-   ❯ my-dev-session [chatgpt/gpt-5 (high)]
-     gpt5-experiment [chatgpt/gpt-5-codex (medium)]
-     claude-session [default]
-   ```
-
-2. **Select routing configuration** - Choose from available options:
-   ```
-   ? Select LLM routing configuration:
-   ❯ Default (Claude)
-     GPT-5 (Reasoning: High)
-     GPT-5 (Reasoning: Medium)
-     GPT-5 (Reasoning: Low)
-     GPT-5 (Reasoning: Minimal)
-     GPT-5 Codex (Reasoning: High)
-     GPT-5 Codex (Reasoning: Medium)
-     GPT-5 Codex (Reasoning: Low)
-   ```
-
-3. **Configuration saved** - The routing configuration is updated in `~/.agiflow/sessions.json`
-
-**Available Routing Options:**
-
-- **Default (Claude)** - Remove routing, use native Claude
-- **GPT-5 (Reasoning: High)** - GPT-5 with maximum reasoning effort (best for complex problems)
-- **GPT-5 (Reasoning: Medium)** - GPT-5 with balanced reasoning (default)
-- **GPT-5 (Reasoning: Low)** - GPT-5 with minimal reasoning (faster responses)
-- **GPT-5 (Reasoning: Minimal)** - GPT-5 with no reasoning (fastest)
-- **GPT-5 Codex** - GPT-5 optimized for coding with reasoning levels
-
-**Reasoning Effort Levels:**
-
-The reasoning effort parameter controls how much computational reasoning the model uses:
-- **High** - Maximum reasoning, best for complex problems, slowest
-- **Medium** - Balanced reasoning, good for most tasks
-- **Low** - Light reasoning, faster responses
-- **Minimal** - No extra reasoning, fastest responses
-
-**Session Settings Location:**
-
-All session routing configurations are stored in `~/.agiflow/sessions.json`:
-
-```json
-{
-  "session-id-1": {
-    "provider": "chatgpt",
-    "model": "gpt-5",
-    "reasoningEffort": "high",
-    "alias": "my-dev-session"
-  },
-  "session-id-2": {
-    "provider": "chatgpt",
-    "model": "gpt-5-codex",
-    "reasoningEffort": "medium",
-    "alias": "gpt5-experiment"
-  }
-}
-```
-
-**Example Workflow:**
-
-```bash
-# 1. Start Claude with default routing
-agent-cli claude --alias "dev-session"
-
-# 2. Switch to GPT-5 with high reasoning (while agent is running)
-agent-cli router
-# Select "dev-session" → "GPT-5 (Reasoning: High)"
-
-# 3. Switch to GPT-5 Codex with medium reasoning
-agent-cli router
-# Select "dev-session" → "GPT-5 Codex (Reasoning: Medium)"
-
-# 4. Switch back to default Claude
-agent-cli router
-# Select "dev-session" → "Default (Claude)"
-
-# 5. Clear all routing configurations
-agent-cli router --clear
-```
-
-**Tips:**
-
-- Use `--alias` when launching Claude to give your sessions meaningful names
-- Session routing is dynamic - changes take effect immediately without restart
-- Clear routing with `agent-cli router --clear` to reset all sessions to default Claude
-- Reasoning effort only applies to GPT models (not Claude)
-
-#### 4. `agent-cli logout` - Clean Up Credentials
+#### 2. `agent-cli logout` - Clean Up Credentials
 Log out and clean up stored credentials.
 
 ```bash
@@ -320,80 +51,10 @@ agent-cli logout --verbose
 
 ### Authentication Flow
 
-1. **Connect Command**: Uses device code authentication flow
-   - Prompts for browser-based authentication
-   - Stores credentials in `~/.agiflow/` directory
-   - Maintains persistent connection to Agiflow platform
-
-2. **Claude Command**: Requires valid session ID
-   - Can use stored credentials from connect flow
-   - Or provide API key and organization ID directly
-
-### Troubleshooting
-
-**Common Issues:**
-
-1. **Missing Agent Session ID**
-   ```
-   Error: Agent session ID is required
-   ```
-   Solution: Provide `--agent-session-id` or set `CLAUDE_AGENT_SESSION_ID` environment variable
-
-2. **Invalid Server URL**
-   ```
-   Error: Invalid server URL
-   ```
-   Solution: Ensure URL is valid WebSocket format (ws:// or wss://)
-
-3. **Authentication Failed**
-   ```
-   Error: Authentication failed
-   ```
-   Solution: Run `agent-cli connect` first or provide valid API credentials
-
-4. **Connection Issues**
-   - Check network connectivity
-   - Verify server URL is accessible
-   - Use `--verbose` flag for detailed logging
-   - Use `--standalone` flag to run without backend connection
-
-5. **WebSocket 401 Unauthorized (Production)**
-   ```
-   Error: Unexpected server response: 401
-   ```
-   Solution: Use `--standalone` flag to run without backend authentication:
-   ```bash
-   agent-cli claude --standalone --verbose
-   ```
-
-**LLM Routing Issues:**
-
-1. **Codex Auth Not Found**
-   ```
-   Warning: Failed to read Codex auth
-   ```
-   Solutions:
-   - Install Codex CLI: `npm install -g @openai/codex`
-   - Authenticate: `codex auth login`
-   - Verify `~/.codex/auth.json` exists
-
-2. **ChatGPT Token Expired**
-   ```
-   Error: 401 Unauthorized
-   ```
-   Solution: Re-authenticate with Codex: `codex auth login`
-
-3. **Routing Not Working**
-   - Verify routing is configured via `agent-cli router` command
-   - Use `--verbose` to see routing status
-   - Check that Codex credentials are valid (`codex auth login`)
-   - Ensure network can reach ChatGPT API
-
-4. **Session Not Found in Router**
-   If your session doesn't appear in `agent-cli router`:
-   - Restart Claude agent with `--alias` to give it a meaningful name
-   - Check `~/.agiflow/sessions.json` to see saved sessions
-   - Use `agent-cli router --clear` to reset all configurations
+**Daemon Command**: Uses device code authentication flow
+- Prompts for browser-based authentication
+- Stores credentials in `~/.agiflow/` directory
+- Maintains persistent connection to Agiflow platform
 
 ### Global Options