mthds-runner-setup

What problem does it solve?

Many MTHDS methods cannot run until inference backends and API keys are configured; this Skill guides users through initial setup, reconfiguration, and recovery from credential or config errors so methods can execute live model inference.

Core Features & Use Cases

• Environment and version validation: Checks mthds-agent presence and version and handles outdated or missing toolchain scenarios.
• Interactive choice flow: Presents Pipelex Gateway (recommended) or Bring Your Own Key (BYOK) options and follows the selected path.
• Pipelex Gateway onboarding: Records terms acceptance, opens login to obtain an API key, initializes gateway backends, and verifies health with mthds-agent doctor.
• BYOK setup: Guides adding provider keys to ~/.pipelex/.env, initializes specified backends, requires primary_backend when multiple non-gateway backends are selected, and runs verification.
• Recovery and verification: Offers upgrade guidance, surfaces CLI errors, and instructs users how to re-run the original method after success.

Quick Start

Choose Pipelex Gateway or BYOK when prompted, run mthds login to obtain a Pipelex API key if using the gateway, then run mthds-agent init -g with your chosen backends and mthds-agent doctor to verify the configuration.