How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

tuya-local - Skill - OpenSmartRoute

Imported from girishkvs/constraining-agent-procedures (corpus/make-all/tuya-local/AGENTS.md). Install upstream with npx skills add girishkvs/constraining-agent-procedures --skill tuya-local. Copyright stays with the author.

Instructions for autonomous agents

Development environment

This project is a Home Assistant integration.
The source languages are Python, YAML and JSON
Use pip install -r requirements-dev.txt to install dependencies

Coding standards

Python files should be checked with ruff check, ruff check --select -I
Python files should be formatted consistently with ruff format
YAML files should be checked with yamllint
YAML files should be located in the custom_components/tuya_local/devices folder
Python files implementing the HA integration should be located in custom_components/tuya_local and its subfolders, with unit tests in tests and its subfolders.
JSON files for translations should be located in the custom_components/tuya_local/translations folder.
Icons should be defined in custom_components/tuya_local/icons.json, and use icons from the material design icons at https://pictogrammers.com/library/mdi/
Where possible, new devices should use existing translation_keys which are present in custom_components/tuya_local/translations/*.json and custom/components/tuya_local/icons.json
if new translation_keys are added, they should be generic, not device specific, and translations should be added to all files in custom_components/tuya_local/translations and relevant icons to custom_components/tuya_local/icons.json

Testing instructions

Find the CI plan in the .github/workflows folder
Ignore the .github/workflows/hacs-validate.yml workflow if not running from the main repository at https://github.com/make-all/tuya-local
run pytest to run every test defined for the project
run pytest tests/test_device_config.py to test only yaml file changes or additions
run pytest tests/test_translations.py to test only json file changes or additions
do not add new tests if only making a yaml or json file change
add new tests if making a python file change that introduces new functionality
fix any test or lint failures until the whole test suite passes

PR instructions

Always run ruff check ., ruff check --select -I ., ruff format --check . and yamllint custom_components/tuya_local/devices before committing

Install tuya-local and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

tuya-local

About

Instructions for autonomous agents

Development environment

Coding standards

Testing instructions

PR instructions

Install tuya-local and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews