import { z } from 'zod';
export declare const configExampleSchema: z.ZodObject<{
    provider: z.ZodEnum<{
        overmind: "overmind";
        ilmu: "ilmu";
        glm: "glm";
        anthropic: "anthropic";
        openrouter: "openrouter";
        "hermes-minimax-cn": "hermes-minimax-cn";
        "hermes-minimax-global": "hermes-minimax-global";
        "hermes-zai": "hermes-zai";
        "hermes-anthropic": "hermes-anthropic";
    }>;
}, z.core.$strip>;
/**
 * config_example tool — provides copy-pasteable config templates for each
 * supported provider. Updated for Overmind 2.8.34+:
 *   - Hermes runner uses the CANONICAL Hermes layout (HERMES_HOME/agents/<name>/)
 *     instead of the legacy polylgot `agent_<name>/.hermes/` dir.
 *   - The runner auto-injects provider-specific env vars (MINIMAX_CN_API_KEY,
 *     MINIMAX_CN_BASE_URL, etc.) into the canonical settings.json based on
 *     the token prefix + ANTHROPIC_BASE_URL. Users only need to set
 *     ANTHROPIC_AUTH_TOKEN (+ ANTHROPIC_BASE_URL) and the runner does the rest.
 *   - `--provider` is now passed to the CLI (forces Hermes upstream to skip
 *     the auto-router that was picking openrouter for MiniMax-M3).
 *
 * Use case: when a user asks "how do I configure agent X for provider Y",
 * call this tool and copy/paste the relevant section.
 */
export declare function configExample(args: z.infer<typeof configExampleSchema>): Promise<{
    content: {
        type: "text";
        text: string;
    }[];
}>;
//# sourceMappingURL=config_example.d.ts.map