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.

dotfiles - Skill - OpenSmartRoute

Name: dotfiles
Author: chetaldrich

Imported from chetaldrich/dotfiles (AGENTS.md). Install upstream with npx skills add chetaldrich/dotfiles. Copyright stays with the author.

Dotfiles

Personal dotfiles managed with chezmoi.

Setup

sh -c "$(curl -fsLS get.chezmoi.io)" -- init --apply chetaldrich

If chezmoi is already installed, run make apply.

Script conventions

Prefix	Runs when
`run_once_*`	First apply only
`run_onchange_*`	Script contents change
`run_always_*`	Every `chezmoi apply` (avoid)

Scripts ending in .tmpl are Go templates processed by chezmoi.

Makefile

Run make with apply, diff, status, edit (opens source dir), or update.

Brewfile

Run brew bundle dump from the repo root to snapshot current machine state.

Git

Author: Chet Aldrich chetaldrich@gmail.com

Code organization

As you work, prefer to factor the existing monolith (e.g. src/App.jsx) into smaller, focused files (components, hooks, lib, data) rather than appending to it, and extract reusable pieces when you touch them. Keep new functionality in appropriately named modules instead of growing the monolith.

Testing

Before calling any change complete, run the project's unit tests and ensure they pass. Add unit tests for any new functionality or refactored logic you introduce, and run them. Do not declare a task done while tests are failing.

Install dotfiles 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.

dotfiles

About

Dotfiles

Setup

Script conventions

Makefile

Brewfile

Git

Code organization

Testing

Install dotfiles 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