@defai.digital/automatosx 11.2.5 → 11.2.7

package/examples/providers/README.md

@@ -1,117 +1,85 @@
-# Provider Configuration Examples
+# Provider Configuration Templates
 
-This directory contains example YAML configurations for AutomatosX providers.
+This directory contains YAML templates for configuring AI providers in AutomatosX.
 
-## Available Examples
+## Available Templates
 
 ### Grok Provider
 
-- **`grok-z-ai.yaml`** - Z.AI GLM 4.6 (code-optimized model)
-  - Best for: Development, code generation, technical tasks
-  - Endpoint: `https://api.z.ai/api/coding/paas/v4`
-  - Model: `glm-4.6`
+**1. X.AI Official Grok** (`grok.yaml.template`)
+- **Model**: `grok-3-fast`
+- **Endpoint**: `https://api.x.ai/v1`
+- **Best for**: General AI tasks, reasoning, analysis
+- **API Key**: Get from https://x.ai/api
+- **Cost**: Paid API (check X.AI pricing)
 
-- **`grok-x-ai.yaml`** - X.AI Official Grok Model
-  - Best for: Reasoning, analysis, general chat
-  - Endpoint: `https://api.x.ai/v1`
-  - Model: `grok-beta`
-
-- **`grok-with-mcp.yaml`** - Grok with MCP Tools
-  - Includes: Filesystem, GitHub, Slack, PostgreSQL integrations
-  - Demonstrates: Model Context Protocol (MCP) setup
-  - Requires: MCP server packages installed
-
-### Multi-Provider Setup
-
-- **`multi-provider.yaml`** - Complete multi-provider configuration
-  - Demonstrates: Priority-based routing
-  - Includes: Claude, Gemini, Grok configurations
-  - Shows: Automatic fallback setup
+**2. Z.AI GLM 4.6** (`grok-zai.yaml.template`)
+- **Model**: `glm-4.6`
+- **Endpoint**: `https://api.z.ai/api/coding/paas/v4`
+- **Best for**: Code generation, Chinese language support
+- **API Key**: Get from https://z.ai
+- **Cost**: Free tier available
 
 ## Quick Start
 
-### 1. Choose a Template
+### Using X.AI Grok
 
 ```bash
-# List available examples
-ls examples/providers/
+# 1. Copy template
+cp templates/providers/grok.yaml.template .automatosx/providers/grok.yaml
 
-# View example
-cat examples/providers/grok-z-ai.yaml
-```
-
-### 2. Copy to Your Project
-
-```bash
-# Create providers directory
-mkdir -p .automatosx/providers
+# 2. Edit the file and add your API key
+# Replace: YOUR_X_AI_API_KEY_HERE
+# With: xai-your-actual-api-key
 
-# Copy template
-cp examples/providers/grok-z-ai.yaml .automatosx/providers/grok.yaml
+# 3. Test configuration
+ax doctor grok
 ```
 
-### 3. Set Environment Variables
+### Using Z.AI GLM 4.6
 
 ```bash
-# For Z.AI
-export GROK_API_KEY="your-z-ai-key"
-
-# For X.AI
-export GROK_API_KEY="xai-your-key"
-
-# For MCP tools (if using)
-export GITHUB_TOKEN="your-github-token"
-```
+# 1. Copy template
+cp templates/providers/grok-zai.yaml.template .automatosx/providers/grok.yaml
 
-### 4. Test Configuration
+# 2. Edit the file and add your API key
+# Replace: YOUR_Z_AI_API_KEY_HERE
+# With: your-actual-z-ai-key
 
-```bash
-# Check provider status
+# 3. Test configuration
 ax doctor grok
-
-# Test execution
-ax run --provider grok backend "simple task"
 ```
 
 ## Configuration Priority
 
-When using multiple providers, AutomatosX routes requests based on priority:
-
-```yaml
-# .automatosx/providers/claude.yaml
-provider:
-  priority: 1    # ← Highest priority (tried first)
+You can adjust the provider priority to control routing order:
 
-# .automatosx/providers/gemini.yaml
-provider:
-  priority: 2    # ← Medium priority
+- **Priority 1** - Highest (tried first)
+- **Priority 2** - High
+- **Priority 3** - Medium
+- **Priority 4** - Low (fallback)
 
-# .automatosx/providers/grok.yaml
+Example:
+```yaml
 provider:
-  priority: 3    # ← Lowest priority (fallback)
+  priority: 2  # Try Grok after OpenAI but before Gemini/Claude
 ```
 
-**Routing behavior:**
-1. Try highest priority provider (1)
-2. If unavailable/failed → try next (2)
-3. If all fail → try lowest priority (3)
-4. If all exhausted → return error
+## Environment Variables
 
-## Environment Variable Interpolation
-
-All examples use `${VAR_NAME}` syntax for environment variables:
+Instead of hardcoding API keys, use environment variables:
 
 ```yaml
 provider:
-  apiKey: ${GROK_API_KEY}           # ← Replaced at runtime
-  baseUrl: https://${API_HOST}/v1    # ← Supports multiple vars
+  apiKey: ${GROK_API_KEY}
+  baseUrl: ${GROK_BASE_URL}
 ```
 
-**Benefits:**
-- ✅ Keep secrets out of version control
-- ✅ Easy environment switching (dev/staging/prod)
-- ✅ Works with CI/CD pipelines
-- ✅ Compatible with `.env` files
+Set environment variables:
+```bash
+export GROK_API_KEY="your-key"
+export GROK_BASE_URL="https://api.x.ai/v1"
+```
 
 ## Customization
 
@@ -119,110 +87,31 @@ provider:
 
 ```yaml
 rateLimits:
-  maxRequestsPerMinute: 120        # ← Increase for higher quota
-  maxTokensPerMinute: 200000       # ← Adjust based on plan
-  maxConcurrentRequests: 10        # ← More parallel requests
+  maxRequestsPerMinute: 120  # Increase for higher quota
+  maxTokensPerMinute: 400000
 ```
 
 ### Modify Timeouts
 
 ```yaml
 provider:
-  timeout: 300000                  # ← 5 minutes for complex tasks
+  timeout: 300000  # 5 minutes for complex tasks
 ```
 
-### Add Circuit Breaker
-
-```yaml
-circuitBreaker:
-  failureThreshold: 5              # ← More tolerant
-  resetTimeout: 120000             # ← Longer cooldown
-```
-
-## Advanced Features
-
-### MCP Tools
-
-Enable Model Context Protocol for extended capabilities:
+### Enable/Disable Provider
 
 ```yaml
-mcp:
-  enabled: true
-  servers:
-    - name: filesystem
-      command: npx
-      args: ["-y", "@modelcontextprotocol/server-filesystem", "/path"]
-```
-
-**Available MCP Servers:**
-- `@modelcontextprotocol/server-filesystem` - File operations
-- `@modelcontextprotocol/server-github` - GitHub API
-- `@modelcontextprotocol/server-slack` - Slack integration
-- `@modelcontextprotocol/server-postgres` - Database access
-
-### Custom Morph Agents
-
-Define specialized agents in configuration:
-
-```yaml
-morph:
-  enabled: true
-  agents:
-    - name: security-auditor
-      prompt: "Analyze code for security vulnerabilities"
-      capabilities: ["security", "audit"]
-```
-
-## Troubleshooting
-
-### Provider Not Found
-
-```bash
-# Check file exists
-ls -la .automatosx/providers/grok.yaml
-
-# Verify provider name
-cat .automatosx/providers/grok.yaml | grep "name:"
-# Should show: name: grok
-```
-
-### Environment Variable Not Set
-
-```bash
-# Check variable
-echo $GROK_API_KEY
-
-# Set if missing
-export GROK_API_KEY="your-key"
-
-# Make persistent (add to ~/.bashrc or ~/.zshrc)
-echo 'export GROK_API_KEY="your-key"' >> ~/.bashrc
-source ~/.bashrc
-```
-
-### YAML Syntax Error
-
-```bash
-# Validate YAML
-yamllint .automatosx/providers/grok.yaml
-
-# Or use online validator
-# https://www.yamllint.com/
+provider:
+  enabled: true  # or false to disable
 ```
 
-## Documentation
-
-- **Full Documentation**: [docs/providers/grok.md](../../docs/providers/grok.md)
-- **AutomatosX Docs**: [README.md](../../README.md)
-- **Z.AI Docs**: https://docs.z.ai
-- **X.AI Docs**: https://x.ai/api
-
 ## Support
 
-- GitHub Issues: https://github.com/defai-digital/automatosx/issues
-- Email: support@defai.digital
+- **Documentation**: See [docs/providers/grok.md](../../docs/providers/grok.md)
+- **Examples**: See [examples/providers/](../../examples/providers/)
+- **Issues**: https://github.com/defai-digital/automatosx/issues
 
 ---
 
-**Version**: 8.3.0
-**Last Updated**: 2025-11-16
+**Version**: 8.3.1
+**Last Updated**: 2025-11-17

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@defai.digital/automatosx",
-  "version": "11.2.5",
+  "version": "11.2.7",
   "description": "Provider-agnostic AI orchestration platform with 20+ specialized agents, persistent memory, and multi-provider routing for Claude Code, Gemini CLI, Codex CLI, and ax-cli",
   "type": "module",
   "publishConfig": {

package/CHANGELOG.md

@@ -1,41 +0,0 @@
-# Changelog
-
-All notable changes to AutomatosX will be documented in this file.
-
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-
-## [11.0.1] - 2025-12-02
-
-### Added - AI-Assisted Orchestration Platform Release
-
-AutomatosX v11.0.1 - Production-ready AI Agent Orchestration Platform.
-
-#### Core Features
-- **Workflow Templates**: YAML-based workflow templates with `--workflow` flag for iterate mode
-- **Spec-Kit Generators**: Auto-generate plans, DAGs, scaffolds, and tests (`ax gen` commands)
-- **Pure CLI Wrapper**: Seamlessly wraps around `claude`, `gemini`, `codex`, `ax-cli` CLIs
-- **Persistent Memory**: SQLite FTS5 full-text search with < 1ms response time
-- **20+ Specialized Agents**: Autonomous task delegation across specialized domains
-- **Token-Based Budget Control**: Reliable budget management using token limits
-- **Complete JSONL Observability**: Full trace logging for every execution decision
-
-#### Platform Support
-- macOS 26.0+
-- Windows 10+
-- Ubuntu 24.04+
-- Node.js >= 24.0.0
-
-#### Providers Supported
-- Claude Code (Anthropic)
-- Gemini CLI (Google)
-- OpenAI Codex
-- ax-cli (GLM, xAI, Ollama)
-
-### Changed
-- Simplified documentation by removing legacy version references
-- Streamlined CLAUDE.md and integration guides
-
----
-
-For complete version history prior to v11.0.0, see git commit history.

package/CODE_OF_CONDUCT.md

@@ -1,133 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, caste, color, religion, or sexual
-identity and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the overall
-  community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or advances of
-  any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email address,
-  without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official email address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-[support@defai.digital](mailto:support@defai.digital).
-
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series of
-actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or permanent
-ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within the
-community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.1, available at
-[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
-
-Community Impact Guidelines were inspired by
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
-[https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/diversity
-[FAQ]: https://www.contributor-covenant.org/faq
-[translations]: https://www.contributor-covenant.org/translations