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.

dual-workspace-sync - Skill

Name: dual-workspace-sync
Author: lawrencekuo1118

Instruction file imported from lawrencekuo1118/theYNowApp (.cursor/rules/dual-workspace-sync.mdc). Copyright stays with the author.

Dual-workspace sync (deployed shinyapps is source of truth)

Latest app version: app_20.0

App / development baseline = currently deployed line on shinyapps.io, not whatever happens to be at Git tip.
Authoritative record: scripts/DEPLOY_BASELINE.txt (bundleId, deploy commit, URL).

Treat that deploy commit’s app_20.0/ tree as the canonical app.
GitHub origin/master may be one or more commits ahead for chore/docs (e.g. updating DEPLOY_BASELINE.txt); that does not change the app baseline unless a new shinyapps deploy is recorded.
Do not treat Cursor Cloud workspace tip, unreleased local edits, or OneDrive drift as newer “truth” for the live app.

Edited from either:

/Users/lawrencekuo/coding/theYNowApp (fast local clone — prefer all git operations here)
/Users/lawrencekuo/Library/CloudStorage/OneDrive-Personal/coding/R/Just4Fun/theYNowApp (OneDrive mirror)

Before any edit session, ensure both paths match the deploy baseline (prefer the commit in DEPLOY_BASELINE.txt; Git tip is OK only when its app_20.0/ tree matches that baseline):

/Users/lawrencekuo/coding/bin/sync-theynow-workspaces.sh
# or: scripts/sync-workspaces.sh

Use --force only if you intentionally want to overwrite dirty local changes.

After finishing edits:

From coding clone: git add/commit then git push origin HEAD, then run the sync script.
From OneDrive: /Users/lawrencekuo/coding/bin/push-theynow-from-onedrive.sh "your message" (mirror → coding → push → re-sync).
After a shinyapps deploy: update scripts/DEPLOY_BASELINE.txt so the recorded commit/bundle stays the baseline.

Never run git status / git diff / git push inside the OneDrive folder.
OneDrive’s tree is a lightweight sync stub (objects via alternates → coding clone). Cloud I/O often times out (mmap failed: Operation timed out), so those commands hang or fail. To verify OneDrive alignment, read:

cat "$ONEDRIVE/.ynow-synced-sha"
# or: scripts/check-od-sync.sh

Install dual-workspace-sync 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.

{ "ocm": "1", "id": "lawrencekuo1118-theynowapp-dual-workspace-sync-rule", "kind": "skill", "name": "dual-workspace-sync", "description": "Keep coding + OneDrive theYNow copies aligned to deployed shinyapps baseline", "publisher": "lawrencekuo1118", "version": "1.0.0", "capabilities": { "domains": [ "coding", "math" ], "tags": [ "skill-md", "github-cursor-rules" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Keep coding + OneDrive theYNow copies aligned to deployed shinyapps baseline" ], "primary": false, "metadata": { "source": { "provider": "github-cursor-rules", "repository": "https://github.com/lawrencekuo1118/theYNowApp", "path": ".cursor/rules/dual-workspace-sync.mdc", "ref": "14864f592620367e7672d985c3e79e69d49d3ff3", "url": "https://github.com/lawrencekuo1118/theYNowApp/blob/14864f592620367e7672d985c3e79e69d49d3ff3/.cursor/rules/dual-workspace-sync.mdc", "key": "lawrencekuo1118/theYNowApp/.cursor/rules/dual-workspace-sync.mdc" } }, "instructions": "# Dual-workspace sync (deployed shinyapps is source of truth)\n\nLatest app version: **app_20.0**\n\n**App / development baseline = currently deployed line on shinyapps.io**, not whatever happens to be at Git tip. \nAuthoritative record: `scripts/DEPLOY_BASELINE.txt` (bundleId, deploy commit, URL).\n\n- Treat that deploy commit’s `app_20.0/` tree as the canonical app.\n- GitHub `origin/master` may be one or more commits ahead for chore/docs (e.g. updating `DEPLOY_BASELINE.txt`); that does **not** change the app baseline unless a new shinyapps deploy is recorded.\n- Do not treat Cursor Cloud workspace ", "cost": { "context_tokens": 507 } }

dual-workspace-sync

About

Dual-workspace sync (deployed shinyapps is source of truth)

Install dual-workspace-sync 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