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.

create-worktree - Prompt - OpenSmartRoute

Name: create-worktree
Author: jabrena

Prompt file imported from jabrena/plinth (.cursor/commands/create-worktree.md). Copyright stays with the author.

create-worktree

Always create a new branch and linked Git worktree for isolated or parallel work without changing the current checkout.

Usage

/create-worktree <issue-or-change|type description> [<target-path>] [<base-reference>]

Accepted Inputs

An issue/change identifier, or an explicit branch type and description
Optional preferred target path
Optional base reference
Supported branch types: feat, fix, docs, refactor, and chore
Preferred branch format: <type>/<issue-or-change>-<kebab-case-description> when an issue or OpenSpec change is available, otherwise <type>/<kebab-case-description>
Fresh-name rule: if the preferred branch name or target path already exists, derive the next unused suffix such as -2, -3, and continue with the fresh branch/worktree

Owning Agent

@plinth-tech-lead

Associated Capabilities

Git branch naming and validation
Git linked worktrees
Parallel OpenSpec child-change coordination

Workflow

Resolve the preferred branch name from the issue/change identifier or explicit branch details.
Resolve an absolute preferred target path and the base reference.
Resolve the repository default branch and the current branch.
Verify the current checkout is main or the repository default branch before creating the worktree branch.
If the current branch is not main or the default branch, stop and ask whether to switch to the default branch, choose a different base, or continue explicitly from the current branch.
Verify the repository and selected base reference are valid before creating anything.
Derive a fresh branch name and fresh target path when the preferred branch exists, is checked out in another worktree, or the preferred target path exists.
Verify the final branch name does not exist, is not checked out in another worktree, and the final target path does not exist.
Run the equivalent of git worktree add -b <branch> <target-path> <base-reference>.
Report the created branch, absolute worktree path, base reference, and cleanup command.

Output

Created local branch
Created linked worktree
Exact branch name, absolute path, and base reference
Cleanup command: git worktree remove <absolute-worktree-path>

Safeguards

Never reuse the current checkout or an existing worktree for the requested work.
When the preferred branch or path conflicts with existing state, choose a fresh unused branch name and target path instead of reusing or overwriting existing state.
Stop and ask when the current branch is not main or the repository default branch.
Stop if the base reference is invalid.
Leave existing branches, worktrees, directories, and files unchanged on conflict.
Do not commit, push, remove worktrees, delete branches, or use force.

Install create-worktree 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.

# create-worktree Always create a new branch and linked Git worktree for isolated or parallel work without changing the current checkout. ## Usage ```text /create-worktree <issue-or-change|type description> [<target-path>] [<base-reference>] ``` ## Accepted Inputs - An issue/change identifier, or an explicit branch type and description - Optional preferred target path - Optional base reference - Supported branch types: `feat`, `fix`, `docs`, `refactor`, and `chore` - Preferred branch format: `<type>/<issue-or-change>-<kebab-case-description>` when an issue or OpenSpec change is available, otherwise `<type>/<kebab-case-description>` - Fresh-name rule: if the preferred branch name or target path already exists, derive the next unused suffix such as `-2`, `-3`, and continue with the fresh branch/worktree ## Owning Agent `@plinth-tech-lead` ## Associated Capabilities - Git branch naming and validation - Git linked worktrees - Parallel OpenSpec child-change coordination ## Workflow 1. Resolve the preferred branch name from the issue/change identifier or explicit branch details. 2. Resolve an absolute preferred target path and the base reference. 3. Resolve the repository default branch and the current branch. 4. Verify the current checkout is `main` or the repository default branch before creating the worktree branch. 5. If the current branch is not `main` or the default branch, stop and ask whether to switch to the default branch, choose a different base, or continue explicitly from the current branch. 6. Verify the repository and selected base reference are valid before creating anything. 7. Derive a fresh branch name and fresh target path when the preferred branch exists, is checked out in another worktree, or the preferred target path exists. 8. Verify the final branch name does not exist, is not checked out in another worktree, and the final target path does not exist. 9. Run the equivalent of `git worktree add -b <branch> <target-path> <base-reference>`. 10. Report the created branch, absolute worktree path, base reference, and cleanup command. ## Output - Created local branch - Created linked worktree - Exact branch name, absolute path, and base reference - Cleanup command: `git worktree remove <absolute-worktree-path>` ## Safeguards - Never reuse the current checkout or an existing worktree for the requested work. - When the preferred branch or path conflicts with existing state, choose a fresh unused branch name and target path instead of reusing or overwriting existing state. - Stop and ask when the current branch is not `main` or the repository default branch. - Stop if the base reference is invalid. - Leave existing branches, worktrees, directories, and files unchanged on conflict. - Do not commit, push, remove worktrees, delete branches, or use force.

{ "prompt": "# create-worktree\n\nAlways create a new branch and linked Git worktree for isolated or parallel work without changing the current checkout.\n\n## Usage\n\n```text\n/create-worktree <issue-or-change|type description> [<target-path>] [<base-reference>]\n```\n\n## Accepted Inputs\n\n- An issue/change identifier, or an explicit branch type and description\n- Optional preferred target path\n- Optional base reference\n- Supported branch types: `feat`, `fix`, `docs`, `refactor`, and `chore`\n- Preferred branch format: `<type>/<issue-or-change>-<kebab-case-description>` when an issue or OpenSpec change is available, otherwise `<type>/<kebab-case-description>`\n- Fresh-name rule: if the preferred branch name or target path already exists, derive the next unused suffix such as `-2`, `-3`, and continue with the fresh branch/worktree\n\n## Owning Agent\n\n`@plinth-tech-lead`\n\n## Associated Capabilities\n\n- Git branch naming and validation\n- Git linked worktrees\n- Parallel OpenSpec child-change coordination\n\n## Workflow\n\n1. Resolve the preferred branch name from the issue/change identifier or explicit branch details.\n2. Resolve an absolute preferred target path and the base reference.\n3. Resolve the repository default branch and the current branch.\n4. Verify the current checkout is `main` or the repository default branch before creating the worktree branch.\n5. If the current branch is not `main` or the default branch, stop and ask whether to switch to the default branch, choose a different base, or continue explicitly from the current branch.\n6. Verify the repository and selected base reference are valid before creating anything.\n7. Derive a fresh branch name and fresh target path when the preferred branch exists, is checked out in another worktree, or the preferred target path exists.\n8. Verify the final branch name does not exist, is not checked out in another worktree, and the final target path does not exist.\n9. Run the equivalent of `git worktree add -b <branch> <target-path> <base-reference>`.\n10. Report the created branch, absolute worktree path, base reference, and cleanup command.\n\n## Output\n\n- Created local branch\n- Created linked worktree\n- Exact branch name, absolute path, and base reference\n- Cleanup command: `git worktree remove <absolute-worktree-path>`\n\n## Safeguards\n\n- Never reuse the current checkout or an existing worktree for the requested work.\n- When the preferred branch or path conflicts with existing state, choose a fresh unused branch name and target path instead of reusing or overwriting existing state.\n- Stop and ask when the current branch is not `main` or the repository default branch.\n- Stop if the base reference is invalid.\n- Leave existing branches, worktrees, directories, and files unchanged on conflict.\n- Do not commit, push, remove worktrees, delete branches, or use force.", "variables": [], "notes": "Create an isolated Git worktree on a new conventionally named branch. Tools: Read, Bash. Arguments: [issue-or-change|type description] [target-path] [base-reference].", "metadata": { "source": { "provider": "github-cursor-commands", "repository": "https://github.com/jabrena/plinth", "path": ".cursor/commands/create-worktree.md", "ref": "2827e2e72af02b35be4da7314248628fa994c16e", "url": "https://github.com/jabrena/plinth/blob/2827e2e72af02b35be4da7314248628fa994c16e/.cursor/commands/create-worktree.md", "key": "jabrena/plinth/.cursor/commands/create-worktree.md" } }, "model_hints": [ "inherit" ] }

create-worktree

About

create-worktree

Usage

Accepted Inputs

Owning Agent

Associated Capabilities

Workflow

Output

Safeguards

Install create-worktree 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