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.

project-notes - Skill - OpenSmartRoute

Instruction file imported from visnudeva/SweetPotatOs (.cursor/rules/project-notes.mdc). Copyright stays with the author.

SweetPotatOs context

Before non-trivial changes, read NOTES.md at the repo root. After a host reinstall / new machine, also read AGENT_MEMORY_BACKUP.md (full ISO workflow + restore checklist).

Hard rules from prior work

Theme source of truth is the sibling SweetPotato repo. Sync into this ISO with ./sync-theme.sh (not by hand-copying one tree only). On a GNOME/Bluefin host, sync-theme.sh must not copy Papirus/glycin into $HOME (that blanks half the GNOME icons). It skips live home automatically; never pass --live on this host.
Desktop compositor is Swirl. The swirl package ships swirlbar, swirlmsg, swirlnag, and swirlmenu, with swaybar / swaymsg / swaynag symlinks. Do not install the Arch sway package (it conflicts). User config is ~/.config/swirl/ only — do not also ship ~/.config/sway/ (Swirl checks sway first). Keep include /etc/sway/config.d/*. swayidle, swaybg, swaylock-effects, and swayimg stay separate.
Fastfetch primary logo is colored SPLogo.png via logo.type: chafa (potato-colored ASCII). Do not switch primary to sixel/auto or monochrome SPLogo.asc.
Lid close suspends via logind lid-sleep.conf. Never reintroduce do-not-suspend.conf that sets HandleLidSwitch=ignore. Caffeine must not block lid suspend.
Ly always lists root first; never ship /etc/ly/save.txt as 0. Post-install sweetpotatos-fix-ly (Calamares shellprocess@fix-ly) must set the saved user to ${USER} and remove liveuser.
Installed user sudo: sweetpotatos-fix-sudo (via fix-ly + cleanup-live) must add ${USER} to wheel, write /etc/sudoers.d/10-installed-user (explicit user rule) and /etc/sudoers.d/10-wheel. Never rely only on Calamares 10-installer or a commented %wheel line in /etc/sudoers.
After install, shellprocess@cleanup-live must remove Install SweetPotatOs / calamares .desktop leftovers from the app launcher.
Default terminal is foot (opaque); do not switch Mod+Return to kitty without updating skel + SweetPotato + sync. Do not ship ~/.config/kitty/.
Ly default_input = password. Enable bluetooth.service on live/install.
Wallpaper: ensure-wallpaper.sh must not overwrite a saved wallpaper.conf with the SPONeonKanjiDefault fallback. Default wallpaper is SPONeonKanjiDefault.png; do not ship UsefulBinds/BindsBG. sweetpotatos-sprout refreshes shipped wallpapers into ~/Pictures/Wallpapers but does not switch the active waypaper selection or delete wallpapers already on a PC.
Live Calamares keyboard needs sweetpotatos-sway-xkb-watch (locale1 → Swirl via busctl poll). Do not assume Calamares Wayland apply changes the compositor by itself, and do not listen with a system-bus monitor as liveuser.
Do not put nvidia-open / nvidia-utils in packages.x86_64. Calamares Notes page + shellprocess@install-nvidia (sweetpotatos-install-nvidia) install them online-only for Turing+ GPUs; offline keeps Mesa/nouveau.
Power menu is power-menu.sh (Mod+Escape only): swirlnag icons for lock/sleep/logout/reboot/poweroff. No X button; Escape or click-outside dismisses (swaynag-power-menu.patch).
Push SweetPotatOs to both origin (GitHub) and sourceforge when the user asks to publish git. ISO upload is separate (sourceforge/upload.sh). Point-release ISOs only — do not reintroduce an in-place spo-upgrade / overlay pacman channel.
Installed-system packages: publish builds to the testing release only (./scripts/publish-repo.sh testing, prerelease pacman-repo-testing) until the user explicitly says to push to stable (./scripts/publish-repo.sh, live tag pacman-repo). A plain “publish” is testing. On a SweetPotatOs install, sudo sweetpotatos-update --testing tracks testing until --stable. Do not point the Ryoku host at either tag.
Ryoku host hygiene: never install SPO packages or wire [sweetpotatos] into this machine’s pacman. After any SweetPotatOs build.sh / package / publish work, clean Ryoku before ending (remove sweetpotatos-local.conf Include + files, clear /var/lib/pacman/sync/sweetpotatos.*, verify pacman works). See NOTES.md “Build-host rule”.

Install project-notes 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.

project-notes

About

SweetPotatOs context

Hard rules from prior work

Install project-notes 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