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.

triage-issue - Prompt - OpenSmartRoute

Name: triage-issue
Author: priyankatiwari08

Prompt file imported from priyankatiwari08/SqlClient-test-prtiwar (.github/prompts/triage-issue.prompt.md). Fill in {{issue}} before use. Copyright stays with the author.

Triage GitHub issue #{{issue}} in dotnet/SqlClient.

IMPORTANT: This prompt is reference material only. Do NOT post comments, do NOT output results for individual sections. Gather all information silently and return findings to the calling workflow.

GitHub Project: https://github.com/orgs/dotnet/projects/588/ — All issues are tracked here. After triaging, update the issue's project fields.

Use the reference sections below to gather information. Do NOT take any output actions (no comments, no reports) — just collect findings and return them.

Reference: Issue Type Classification

Determine which issue template was used:

ISSUE_TEMPLATE/bug-report.md → Bug
ISSUE_TEMPLATE/feature_request.md → Feature
No template / sub-issue → Task
High-level work with sub-issues → Epic

Reference: Completeness Checklist

For Bugs, check for:

.NET version and target framework
Microsoft.Data.SqlClient version
SQL Server version (if relevant)
OS and platform
Repro steps or minimal repro code
Expected vs actual behavior
Stack trace or error message

For Features, check for:

Clear problem statement / motivation
Proposed solution or API shape
Use case / scenario description

If any required details are missing, add the label Needs more info :information_source:.

Reference: Available Area Labels (use exact names)

Area\Engineering — Build system, CI/CD, project infrastructure
Area\Connection Pooling — Pool behavior, timeouts, pool size
Area\AKV Provider — Always Encrypted Azure Key Vault provider
Area\Json — JSON data type support
Area\Managed SNI — Managed SNI codebase (network layer)
Area\Native SNI — Native SNI codebase (network layer)
Area\Sql Bulk Copy — SqlBulkCopy operations
Area\Netcore — Issues specific to .NET runtime / netcore folder
Area\Netfx — Issues specific to .NET Framework / netfx folder
Area\Tests — Test code / test projects
Area\Documentation — Documentation and samples
Area\Azure Connectivity — Azure connectivity issues
Area\Vector — Vector feature
Area\Async — Async operations

Reference: Available Status Labels

Triage Needed :new: — For new issues needing initial review
Needs more info :information_source: — Missing required details
Regression :boom: — Regressions from earlier PRs
Performance :chart_with_upwards_trend: — Performance-related concern
Repro Available :heavy_check_mark: — Issue has repro steps provided

Reference: GitHub Project Fields

Field	Values	Guidance
Status	`To Triage`, `Needs Response`, `Investigating`, `Waiting for customer`, `Backlog`, `In progress`, `In review`, `Done`	Set to `Investigating` if actionable, `Needs Response` if info is missing from reporter, `Waiting for customer` if awaiting external input, `Backlog` for valid lower-priority items
Priority	`P0`, `P1`, `P2`, `P3`	P0: Critical — data loss, security vulnerability, widespread breakage. P1: High — significant regression, blocking customer scenario. P2: Medium — important but has workaround, affects subset of users. P3: Low — minor issue, enhancement, nice-to-have
Size	`XS`, `S`, `M`, `L`, `XL`	Estimate effort: XS: trivial fix (<1h). S: small, well-scoped (<1 day). M: moderate, may touch multiple files (1-3 days). L: significant, cross-cutting (1-2 weeks). XL: large feature or architectural change (2+ weeks)

Reference: Duplicate Search

Search for existing issues with similar keywords: repo:dotnet/SqlClient <key terms>
Note any duplicates or related issues found — these will be linked in the triage comment.

Reference: Affected Code Area

Source files are in src/Microsoft.Data.SqlClient/src/Microsoft/Data/SqlClient/
Key components: SqlConnection, TdsParser, ConnectionPool, SqlCommand
Check if the issue is platform-specific (Windows-only, Unix-only, .NET Framework-only)

9. Summary — Internal Use Only

Do NOT output or post the summary as a separate comment. Return the following fields to the calling workflow for inclusion in the single triage comment:

Type, Area, Labels applied, Project fields, Missing info, Related issues, Severity assessment

Install triage-issue 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.

Triage GitHub issue #{{issue}} in `dotnet/SqlClient`. > **IMPORTANT**: This prompt is reference material only. Do NOT post comments, > do NOT output results for individual sections. Gather all information silently > and return findings to the calling workflow. **GitHub Project**: https://github.com/orgs/dotnet/projects/588/ — All issues are tracked here. After triaging, update the issue's project fields. Use the reference sections below to gather information. Do NOT take any output actions (no comments, no reports) — just collect findings and return them. ### Reference: Issue Type Classification Determine which issue template was used: - `ISSUE_TEMPLATE/bug-report.md` → Bug - `ISSUE_TEMPLATE/feature_request.md` → Feature - No template / sub-issue → Task - High-level work with sub-issues → Epic ### Reference: Completeness Checklist **For Bugs**, check for: - .NET version and target framework - Microsoft.Data.SqlClient version - SQL Server version (if relevant) - OS and platform - Repro steps or minimal repro code - Expected vs actual behavior - Stack trace or error message **For Features**, check for: - Clear problem statement / motivation - Proposed solution or API shape - Use case / scenario description If any required details are missing, add the label `Needs more info :information_source:`. ### Reference: Available Area Labels (use exact names) - `Area\Engineering` — Build system, CI/CD, project infrastructure - `Area\Connection Pooling` — Pool behavior, timeouts, pool size - `Area\AKV Provider` — Always Encrypted Azure Key Vault provider - `Area\Json` — JSON data type support - `Area\Managed SNI` — Managed SNI codebase (network layer) - `Area\Native SNI` — Native SNI codebase (network layer) - `Area\Sql Bulk Copy` — SqlBulkCopy operations - `Area\Netcore` — Issues specific to .NET runtime / netcore folder - `Area\Netfx` — Issues specific to .NET Framework / netfx folder - `Area\Tests` — Test code / test projects - `Area\Documentation` — Documentation and samples - `Area\Azure Connectivity` — Azure connectivity issues - `Area\Vector` — Vector feature - `Area\Async` — Async operations ### Reference: Available Status Labels - `Triage Needed :new:` — For new issues needing initial review - `Needs more info :information_source:` — Missing required details - `Regression :boom:` — Regressions from earlier PRs - `Performance :chart_with_upwards_trend:` — Performance-related concern - `Repro Available :heavy_check_mark:` — Issue has repro steps provided ### Reference: GitHub Project Fields | Field | Values | Guidance | |-------|--------|----------| | **Status** | `To Triage`, `Needs Response`, `Investigating`, `Waiting for customer`, `Backlog`, `In progress`, `In review`, `Done` | Set to `Investigating` if actionable, `Needs Response` if info is missing from reporter, `Waiting for customer` if awaiting external input, `Backlog` for valid lower-priority items | | **Priority** | `P0`, `P1`, `P2`, `P3` | **P0**: Critical — data loss, security vulnerability, widespread breakage. **P1**: High — significant regression, blocking customer scenario. **P2**: Medium — important but has workaround, affects subset of users. **P3**: Low — minor issue, enhancement, nice-to-have | | **Size** | `XS`, `S`, `M`, `L`, `XL` | Estimate effort: **XS**: trivial fix (<1h). **S**: small, well-scoped (<1 day). **M**: moderate, may touch multiple files (1-3 days). **L**: significant, cross-cutting (1-2 weeks). **XL**: large feature or architectural change (2+ weeks) | ### Reference: Duplicate Search - Search for existing issues with similar keywords: `repo:dotnet/SqlClient <key terms>` - Note any duplicates or related issues found — these will be linked in the triage comment. ### Reference: Affected Code Area - Source files are in `src/Microsoft.Data.SqlClient/src/Microsoft/Data/SqlClient/` - Key components: SqlConnection, TdsParser, ConnectionPool, SqlCommand - Check if the issue is platform-specific (Windows-only, Unix-only, .NET Framework-only) ## 9. Summary — Internal Use Only Do NOT output or post the summary as a separate comment. Return the following fields to the calling workflow for inclusion in the single triage comment: - Type, Area, Labels applied, Project fields, Missing info, Related issues, Severity assessment

{ "prompt": "Triage GitHub issue #{{issue}} in `dotnet/SqlClient`.\n\n> **IMPORTANT**: This prompt is reference material only. Do NOT post comments,\n> do NOT output results for individual sections. Gather all information silently\n> and return findings to the calling workflow.\n\n**GitHub Project**: https://github.com/orgs/dotnet/projects/588/ — All issues are tracked here. After triaging, update the issue's project fields.\n\nUse the reference sections below to gather information. Do NOT take any output\nactions (no comments, no reports) — just collect findings and return them.\n\n### Reference: Issue Type Classification\nDetermine which issue template was used:\n- `ISSUE_TEMPLATE/bug-report.md` → Bug\n- `ISSUE_TEMPLATE/feature_request.md` → Feature\n- No template / sub-issue → Task\n- High-level work with sub-issues → Epic\n\n### Reference: Completeness Checklist\n\n**For Bugs**, check for:\n- .NET version and target framework\n- Microsoft.Data.SqlClient version\n- SQL Server version (if relevant)\n- OS and platform\n- Repro steps or minimal repro code\n- Expected vs actual behavior\n- Stack trace or error message\n\n**For Features**, check for:\n- Clear problem statement / motivation\n- Proposed solution or API shape\n- Use case / scenario description\n\nIf any required details are missing, add the label `Needs more info :information_source:`.\n\n### Reference: Available Area Labels (use exact names)\n- `Area\\Engineering` — Build system, CI/CD, project infrastructure\n- `Area\\Connection Pooling` — Pool behavior, timeouts, pool size\n- `Area\\AKV Provider` — Always Encrypted Azure Key Vault provider\n- `Area\\Json` — JSON data type support\n- `Area\\Managed SNI` — Managed SNI codebase (network layer)\n- `Area\\Native SNI` — Native SNI codebase (network layer)\n- `Area\\Sql Bulk Copy` — SqlBulkCopy operations\n- `Area\\Netcore` — Issues specific to .NET runtime / netcore folder\n- `Area\\Netfx` — Issues specific to .NET Framework / netfx folder\n- `Area\\Tests` — Test code / test projects\n- `Area\\Documentation` — Documentation and samples\n- `Area\\Azure Connectivity` — Azure connectivity issues\n- `Area\\Vector` — Vector feature\n- `Area\\Async` — Async operations\n\n### Reference: Available Status Labels\n- `Triage Needed :new:` — For new issues needing initial review\n- `Needs more info :information_source:` — Missing required details\n- `Regression :boom:` — Regressions from earlier PRs\n- `Performance :chart_with_upwards_trend:` — Performance-related concern\n- `Repro Available :heavy_check_mark:` — Issue has repro steps provided\n\n### Reference: GitHub Project Fields\n\n| Field | Values | Guidance |\n|-------|--------|----------|\n| **Status** | `To Triage`, `Needs Response`, `Investigating`, `Waiting for customer`, `Backlog`, `In progress`, `In review`, `Done` | Set to `Investigating` if actionable, `Needs Response` if info is missing from reporter, `Waiting for customer` if awaiting external input, `Backlog` for valid lower-priority items |\n| **Priority** | `P0`, `P1`, `P2`, `P3` | **P0**: Critical — data loss, security vulnerability, widespread breakage. **P1**: High — significant regression, blocking customer scenario. **P2**: Medium — important but has workaround, affects subset of users. **P3**: Low — minor issue, enhancement, nice-to-have |\n| **Size** | `XS`, `S`, `M`, `L`, `XL` | Estimate effort: **XS**: trivial fix (<1h). **S**: small, well-scoped (<1 day). **M**: moderate, may touch multiple files (1-3 days). **L**: significant, cross-cutting (1-2 weeks). **XL**: large feature or architectural change (2+ weeks) |\n\n### Reference: Duplicate Search\n- Search for existing issues with similar keywords: `repo:dotnet/SqlClient <key terms>`\n- Note any duplicates or related issues found — these will be linked in the triage comment.\n\n### Reference: Affected Code Area\n- Source files are in `src/Microsoft.Data.SqlClient/src/Microsoft/Data/SqlClient/`\n- Key components: SqlConnection, TdsParser, ConnectionPool, SqlCommand\n- Check if the issue is platform-specific (Windows-only, Unix-only, .NET Framework-only)\n\n## 9. Summary — Internal Use Only\nDo NOT output or post the summary as a separate comment.\nReturn the following fields to the calling workflow for inclusion in the single triage comment:\n- Type, Area, Labels applied, Project fields, Missing info, Related issues, Severity assessment", "variables": [ "issue" ], "notes": "Triage a new GitHub issue — categorize, label, request info, and link related items. Tools: github/search_issues, read/readFile, codebase/search. Arguments: <issue number>.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/priyankatiwari08/SqlClient-test-prtiwar", "path": ".github/prompts/triage-issue.prompt.md", "ref": "a075f67b8560717f238f3d221a227d94830fdfd0", "url": "https://github.com/priyankatiwari08/SqlClient-test-prtiwar/blob/a075f67b8560717f238f3d221a227d94830fdfd0/.github/prompts/triage-issue.prompt.md", "key": "priyankatiwari08/SqlClient-test-prtiwar/.github/prompts/triage-issue.prompt.md" } } }

triage-issue

About

Reference: Issue Type Classification

Reference: Completeness Checklist

Reference: Available Area Labels (use exact names)

Reference: Available Status Labels

Reference: GitHub Project Fields

Reference: Duplicate Search

Reference: Affected Code Area

9. Summary — Internal Use Only

Install triage-issue 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