switchailocal

Route AI model requests across providers via a local endpoint.

2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/traylinx/switchAILocal --skill switchailocal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: switchailocal
Source: https://github.com/traylinx/switchAILocal/tree/main
Command: npx skills add https://github.com/traylinx/switchAILocal --skill switchailocal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

switchAILocal provides a unified local endpoint to route and manage requests across multiple AI providers, eliminating the need to individually configure and call each service.

Core Features & Use Cases

  • Unified provider routing: switch between CLI tools, local models, and cloud APIs using provider prefixes or auto-routing.
  • Attach context: pass files/folders to CLI providers and enrich prompts.
  • Intelligent routing & health: dynamic model selection, health checks, and fallback strategies for reliability.

Quick Start

Point your client at http://localhost:18080/v1 and issue a chat request using a provider-formatted model, such as geminicli:gemini-2.5-pro or ollama:llama3.2, or use auto-routing with switchai:auto.

Frequently Asked Questions about switchailocal

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route AI requests across multiple providers from a single endpoint?

Routing AI requests across providers uses a unified local endpoint at http://localhost:18080/v1. Point your client there and specify the provider using a formatted model name like geminicli:gemini-2.5-pro, ollama:llama3.2, or use switchai:auto for automatic routing across CLI tools, local models, and cloud APIs.

Can I use CLI tools and local models alongside cloud APIs in the same request flow?

Yes. The unified endpoint integrates CLI tools, local models, and cloud APIs with provider prefixes and auto-routing. You can attach files to CLI providers, enable health checks, and set fallback strategies for reliable provider selection across your mixed stack.

What's the best way to manage multiple AI provider configurations without separate endpoints?

A single local endpoint eliminates individual provider configuration. The pluggable architecture with provider executors and routing matrices lets you switch providers via model prefix or auto-routing, reducing operational complexity and centralized management overhead.

How do I attach files or context to AI provider requests?

File attachment and context enrichment is built into the unified endpoint. Pass files or folders directly to CLI providers, and the system enriches prompts automatically, enabling richer interactions across your provider mix without manual payload construction.

Does provider routing include fallback strategies if a service fails?

Yes. Dynamic model selection with health checks and fallback strategies ensures reliability. If a provider is unavailable, the routing logic automatically selects an alternative, maintaining uptime across your integration.

What security options are available for local AI provider routing?

Optional security hardening is available to meet deployment security needs. The pluggable architecture supports enforcement policies within the routing and provider execution layer, protecting your local endpoint configuration.