saigontechnology

AgentCrew Configuration Guide — Data & AI agent for Claude Code

Data & AI community intermediate

This guide explains how to configure AgentCrew to work with different AI providers, customize agents, set up tools, and manage system settings.

How to install AgentCrew Configuration Guide

This entry records only its repository, not the path inside it, so there is no exact command to give. Open saigontechnology/AgentCrew and copy the folder into ~/.claude/agents/.

What AgentCrew Configuration Guide does

This guide explains how to configure AgentCrew to work with different AI providers, customize agents, set up tools, and manage system settings.

Alternatives in Data & AI

  • Docs Drift Reviewer — Checks whether clickhouse-go documentation matches changes to its ClickHouse API, database/sql API, transports 3.3k ★
  • Gaia Agent Builder — GAIA agent creation specialist 1.5k ★
  • LLM Expert — Use this agent for AI SDK integration, LLM provider configuration, prompt template management, error handling 434 ★

README

AgentCrew Configuration Guide

This guide explains how to configure AgentCrew to work with different AI providers, customize agents, set up tools, and manage system settings.

Configuration Files

AgentCrew stores all configuration in `~/.AgentCrew/` (or `%USERPROFILE%\.AgentCrew\` on Windows):

~/.AgentCrew/
├── config.json              # Global settings and API keys
├── agents.toml              # Agent definitions and configurations
├── mcp_servers.json         # Model Context Protocol server configs
├── persistents/
│   └── adaptive.json        # Learned behaviors for all agents
└── conversations/           # Saved conversation history

Global Configuration (config.json)

The main configuration file controls API keys, UI preferences, and system behavior.

API Keys

Add your API keys to connect AgentCrew with AI providers:

{
  "api_keys": {
    "ANTHROPIC_API_KEY": "sk-ant-...",
    "OPENAI_API_KEY": "sk-proj-...",
    "GEMINI_API_KEY": "AIza...",
    "GITHUB_COPILOT_API_KEY": "",
    "DEEPINFRA_API_KEY": "",
    "TAVILY_API_KEY": "tvly-...",
    "VOYAGE_API_KEY": "pa-...",
    "ELEVENLABS_API_KEY": ""
  }
}

**Required Keys:**

  • At least one AI provider key (Anthropic, OpenAI, Gemini, etc.)

**Optional Keys:**

  • TAVILY_API_KEY - For web search capabilities
  • VOYAGE_API_KEY - For alternative embedding provider
  • ELEVENLABS_API_KEY - For voice synthesis

**Getting API Keys:**

Custom LLM Providers

Add OpenAI-compatible providers like llama.cpp, Ollama, or LM Studio:

{
  "custom_llm_providers": [
    {
      "name": "llama.cpp",
      "type": "openai_compatible",
      "api_base_url": "http://localhost:8009",
      "api_key": "",
      "default_model_id": "qwen-14b",
      "available_models": [
        {
          "id": "../Qwen3-14B-Q6_K.gguf",
          "name": "Local Qwen 14B",
          "provider": "llama.cpp",
          "capabilities": ["thinking", "vision"],
          "default": true,
          "description": "Quantized Qwen model running locally",
          "input_token_price_1m": 0.0,
          "output_token_price_1m": 0.0
        }
      ],
      "is_stream": false,
      "extra_headers": {}
    }
  ]
}

**Fields:**

  • name - Unique identifier for the provider
  • type - Always "openai_compatible" for custom providers
  • api_base_url - Base URL for the API endpoint
  • api_key - API key if required (leave empty for local servers)
  • default_model_id - Default model to use
  • available_models - List of models this provider offers
  • is_stream - Whether to enable streaming responses
  • `extra_headers