language-operator 0.1.81 → 0.1.82

data/docs/quickstart.md

@@ -4,7 +4,7 @@ Get your first Language Operator agent running in 5 minutes.
 
 ## Before You Begin
 
-- Install aictl: `gem install language-operator`
+- Install langop: `gem install language-operator`
 - Have Kubernetes cluster access
 - Set up API keys for your preferred LLM provider
 
@@ -13,7 +13,7 @@ Get your first Language Operator agent running in 5 minutes.
 Run the interactive setup wizard:
 
 ```bash
-aictl quickstart
+langop quickstart
 ```
 
 The wizard will guide you through:
@@ -30,38 +30,38 @@ If you prefer step-by-step setup:
 
 ```bash
 # Create cluster configuration
-aictl cluster create my-cluster
+langop cluster create my-cluster
 
 # Switch to it
-aictl use my-cluster
+langop use my-cluster
 
 # Check connectivity
-aictl status
+langop status
 ```
 
 ### Install Language Operator
 
 ```bash
-aictl install
+langop install
 ```
 
 Wait for installation to complete, then verify:
 
 ```bash
-aictl status
+langop status
 ```
 
 ### Create a Model
 
 ```bash
 # For OpenAI (set OPENAI_API_KEY first)
-aictl model create gpt4 --provider openai --model gpt-4-turbo
+langop model create gpt4 --provider openai --model gpt-4-turbo
 
 # For Anthropic (set ANTHROPIC_API_KEY first)  
-aictl model create claude --provider anthropic --model claude-3-sonnet
+langop model create claude --provider anthropic --model claude-3-sonnet
 
 # Verify model
-aictl model list
+langop model list
 ```
 
 ## Step 3: Create Your First Agent
@@ -71,7 +71,7 @@ aictl model list
 Create an agent that runs daily:
 
 ```bash
-aictl agent create daily-reporter
+langop agent create daily-reporter
 ```
 
 You'll be prompted to describe what the agent should do. Try:
@@ -81,13 +81,13 @@ You'll be prompted to describe what the agent should do. Try:
 
 ```bash
 # List all agents
-aictl agent list
+langop agent list
 
 # Get detailed info
-aictl agent inspect daily-reporter
+langop agent inspect daily-reporter
 
 # View logs
-aictl agent logs daily-reporter -f
+langop agent logs daily-reporter -f
 ```
 
 ## Step 4: Understanding What Was Created
@@ -96,7 +96,7 @@ aictl agent logs daily-reporter -f
 
 ```bash
 # Open agent workspace
-aictl agent workspace daily-reporter
+langop agent workspace daily-reporter
 ```
 
 This shows the synthesized agent definition that Language Operator created from your description.
@@ -146,7 +146,7 @@ end
 Create an agent that responds to GitHub webhooks:
 
 ```bash
-aictl agent create github-responder
+langop agent create github-responder
 ```
 
 Description: "Respond to GitHub pull request webhooks with automated code reviews"
@@ -156,7 +156,7 @@ Description: "Respond to GitHub pull request webhooks with automated code review
 Create a conversational agent:
 
 ```bash
-aictl agent create support-bot
+langop agent create support-bot
 ```
 
 Description: "Provide customer support through a chat interface"
@@ -166,7 +166,7 @@ Description: "Provide customer support through a chat interface"
 Create an agent that runs continuously:
 
 ```bash
-aictl agent create system-monitor
+langop agent create system-monitor
 ```
 
 Description: "Continuously monitor system health and alert on issues"
@@ -176,17 +176,17 @@ Description: "Continuously monitor system health and alert on issues"
 ### View All Agents
 
 ```bash
-aictl agent list
+langop agent list
 ```
 
 ### Check Agent Logs
 
 ```bash
 # Follow logs in real-time
-aictl agent logs daily-reporter -f
+langop agent logs daily-reporter -f
 
 # View recent logs
-aictl agent logs daily-reporter --since 1h
+langop agent logs daily-reporter --since 1h
 ```
 
 ### Monitoring Agents
@@ -195,10 +195,10 @@ Monitor your agent's execution and performance:
 
 ```bash
 # View detailed agent information
-aictl agent inspect daily-reporter
+langop agent inspect daily-reporter
 
 # Check recent execution logs
-aictl agent logs daily-reporter --since 1h
+langop agent logs daily-reporter --since 1h
 ```
 
 ## Common Patterns
@@ -247,13 +247,13 @@ end
 
 ```bash
 # Check agent status
-aictl agent inspect my-agent
+langop agent inspect my-agent
 
 # View detailed logs
-aictl agent logs my-agent
+langop agent logs my-agent
 
 # Check cluster status
-aictl status
+langop status
 ```
 
 ### High Costs
@@ -262,7 +262,7 @@ Agents use LLM APIs which have costs. Monitor usage:
 
 ```bash
 # Check agent configuration
-aictl agent inspect my-agent
+langop agent inspect my-agent
 
 # Look for budget constraints
 # Adjust constraints if needed
@@ -278,7 +278,7 @@ kubectl get nodes
 kubectl get pods -n language-operator
 
 # Verify model connectivity
-aictl model test my-model
+langop model test my-model
 ```
 
 ## Next Steps
@@ -293,7 +293,7 @@ Now that you have a working agent:
 
 ## Getting Help
 
-- View command help: `aictl --help`
-- Check specific commands: `aictl agent --help`
+- View command help: `langop --help`
+- Check specific commands: `langop agent --help`
 - Report issues: [GitHub Issues](https://github.com/language-operator/language-operator-gem/issues)
 - Join discussions: [GitHub Discussions](https://github.com/language-operator/language-operator/discussions)

data/docs/using-tools.md

@@ -210,7 +210,7 @@ For advanced use cases, you can specify tool requirements:
 
 ```bash
 # During agent creation
-aictl agent create my-agent \
+langop agent create my-agent \
   --tools database,slack,github \
   --database-url postgres://... \
   --slack-token xoxb-... \
@@ -242,13 +242,13 @@ Language Operator provides basic tool management commands:
 
 ```bash
 # Deploy a tool server to your cluster
-aictl tool deploy ./path/to/tool
+langop tool deploy ./path/to/tool
 
 # Test tool connectivity
-aictl tool test my-tool
+langop tool test my-tool
 
 # View tool logs
-aictl tool logs my-tool
+langop tool logs my-tool
 ```
 
 For available tools, check the `components/tool/examples/` directory in the repository.
@@ -323,10 +323,10 @@ end
 
 ```bash
 # Deploy your custom tool server
-aictl tool deploy ./my-custom-tools
+langop tool deploy ./my-custom-tools
 
 # Register with Language Operator
-aictl tool register my-custom-tools \
+langop tool register my-custom-tools \
   --endpoint https://my-tools.company.com
 ```
 
@@ -369,10 +369,10 @@ All tool usage is logged for security and debugging:
 
 ```bash
 # View tool usage logs
-aictl agent logs my-agent --tools-only
+langop agent logs my-agent --tools-only
 
 # Audit specific tool usage
-aictl tool audit database --agent my-agent --since 24h
+langop tool audit database --agent my-agent --since 24h
 ```
 
 ## Performance Optimization
@@ -434,13 +434,13 @@ end
 
 ```bash
 # Test tool connectivity
-aictl tool test database
+langop tool test database
 
 # Check tool configuration
-aictl tool config database
+langop tool config database
 
 # View tool logs
-aictl tool logs database --since 1h
+langop tool logs database --since 1h
 ```
 
 ### Common Issues

data/docs/webhooks.md

@@ -9,7 +9,7 @@ When you describe an agent that responds to external events, Language Operator c
 ### Creating Webhook Agents
 
 ```bash
-aictl agent create github-pr-reviewer
+langop agent create github-pr-reviewer
 # Wizard asks:
 # - What service sends webhooks? (GitHub, Stripe, Slack, custom)
 # - What events should trigger the agent? (pull_request, push, etc.)
@@ -422,13 +422,13 @@ Monitor webhook activity:
 
 ```bash
 # View webhook logs
-aictl agent logs pr-reviewer --webhooks-only
+langop agent logs pr-reviewer --webhooks-only
 
 # Follow webhook activity in real-time
-aictl agent logs pr-reviewer --follow --filter webhook
+langop agent logs pr-reviewer --follow --filter webhook
 
 # View specific webhook processing
-aictl agent webhook-logs pr-reviewer --webhook-id abc123
+langop agent webhook-logs pr-reviewer --webhook-id abc123
 ```
 
 ### Webhook Testing
@@ -437,12 +437,12 @@ Test webhooks during development:
 
 ```bash
 # Test webhook endpoint
-aictl agent test-webhook pr-reviewer \
+langop agent test-webhook pr-reviewer \
   --payload ./test-payload.json \
   --event pull_request.opened
 
 # Simulate webhook with custom data
-aictl agent simulate-webhook pr-reviewer \
+langop agent simulate-webhook pr-reviewer \
   --github-pr 123 \
   --repository company/main-repo
 ```

data/examples/ux_helpers_demo.rb

@@ -119,10 +119,10 @@ class UxDemo
 
     # Multi-line box
     puts box(<<~MSG, title: 'Next Steps', padding: 2)
-      1. Monitor logs:    aictl agent logs my-agent
-      2. Check status:    aictl agent inspect my-agent
-      3. View metrics:    aictl agent metrics my-agent
-      4. Scale replicas:  aictl agent scale my-agent --replicas=3
+      1. Monitor logs:    langop agent logs my-agent
+      2. Check status:    langop agent inspect my-agent
+      3. View metrics:    langop agent metrics my-agent
+      4. Scale replicas:  langop agent scale my-agent --replicas=3
     MSG
     puts "\n"
   end

data/lib/language_operator/agent/task_executor.rb

@@ -142,25 +142,20 @@ module LanguageOperator
           current_span = OpenTelemetry::Trace.current_span
           current_span&.set_attribute('task.outputs', result.to_json) if current_span && capture_enabled?(:outputs)
 
-          # Emit Kubernetes event for successful task completion
-          emit_task_execution_event(task_name, success: true, execution_start: execution_start)
 
           result
         end
       rescue ArgumentError => e
         # Validation errors should not be retried - re-raise immediately
         log_task_error(task_name, e, :validation, execution_start)
-        emit_task_execution_event(task_name, success: false, execution_start: execution_start, error: e, event_type: :validation)
         raise TaskValidationError.new(task_name, e.message, e)
       rescue TaskValidationError => e
         # TaskValidationError from validate_inputs should be logged as :validation
         log_task_error(task_name, e, :validation, execution_start)
-        emit_task_execution_event(task_name, success: false, execution_start: execution_start, error: e, event_type: :validation)
         raise e
       rescue StandardError => e
         # Catch any unexpected errors that escaped retry logic
         log_task_error(task_name, e, :system, execution_start)
-        emit_task_execution_event(task_name, success: false, execution_start: execution_start, error: e)
         raise create_appropriate_error(task_name, e)
       end
 
@@ -383,38 +378,6 @@ module LanguageOperator
         'Agent::TaskExecutor'
       end
 
-      # Emit Kubernetes event for task execution
-      #
-      # @param task_name [Symbol, String] Task name
-      # @param success [Boolean] Whether task succeeded
-      # @param execution_start [Time] Task execution start time
-      # @param error [Exception, nil] Error if task failed
-      # @param event_type [Symbol, nil] Event type override (:success, :failure, :validation)
-      def emit_task_execution_event(task_name, success:, execution_start:, error: nil, event_type: nil)
-        return unless @agent.respond_to?(:kubernetes_client)
-
-        duration_ms = ((Time.now - execution_start) * 1000).round(2)
-
-        metadata = {
-          'task_type' => determine_task_type(@tasks[task_name.to_sym])
-        }
-
-        if error
-          metadata['error_type'] = error.class.name
-          metadata['error_category'] = categorize_error(error).to_s
-        end
-
-        @agent.kubernetes_client.emit_execution_event(
-          task_name.to_s,
-          success: success,
-          duration_ms: duration_ms,
-          metadata: metadata
-        )
-      rescue StandardError => e
-        logger.warn('Failed to emit task execution event',
-                    task: task_name,
-                    error: e.message)
-      end
 
       # Summarize hash values for logging (truncate long strings)
       # Optimized for performance with lazy computation