feat: add Tetrate Agent Router Service (TARS) as provider #6832

arifsetiawan · 2025-08-08T04:04:02Z

Related GitHub Issue

Closes: #6747

Roo Code Task Context (Optional)

Description

This PR adds TARS (Tetrate Agent Router Service) as a native provider option in Roo Code, following the same implementation pattern as other AI router providers (e.g., Requesty).

Users can now select TARS directly from the provider dropdown
No need to manually configure base URLs
Automatic model information and context windows
Consistent experience with other native providers

Test Procedure

Added unit tests for the TARS handler (src/api/providers/tests/tars.spec.ts)
Updated existing test suites to include TARS in router provider expectations

Manual Testing Steps:

Open Roo Code settings
Navigate to API Provider selection
Select "Tetrate Agent Router Service (TARS)" from the dropdown
Obtain an API key from https://router.tetrate.ai
Enter the API key in the settings
Click "Refresh available models" to fetch the model list
Select a model
Test with a coding task to verify the integration works

Pre-Submission Checklist

Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
Scope: My changes are focused on the linked issue (one major feature/fix per PR).
Self-Review: I have performed a thorough self-review of my code.
Testing: New and/or updated tests have been added to cover my changes (if applicable).
Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

Kapture.2025-08-08.at.10.35.36.mp4

Documentation Updates

Does this PR necessitate updates to user-facing documentation?

No documentation updates are required.
Yes, documentation updates are required. PR feature: add Tetrate Agent Router Service (TARS) as provider Roo-Code-Docs#303

Additional Notes

To use TARS, signup to https://router.tetrate.ai. API URL is https://api.router.tetrate.ai/v1
The implementation follows the same pattern as Requesty for consistency

Get in Touch

Discord: @arifsetiawan

Important

Adds Tetrate Agent Router Service (TARS) as a new provider, integrating it into the system with UI, handlers, and validation support.

Behavior:
- Adds TARS as a provider option, allowing users to select it from the dropdown without manual URL configuration.
- Fetches model information automatically, similar to other providers.
Handlers and Models:
- Implements TarsHandler in tars.ts for API interactions.
- Updates provider-settings.ts and index.ts to include TARS.
- Adds TARS model fetching logic in fetchers/tars.ts.
UI Components:
- Adds Tars component in providers/Tars.tsx for UI settings.
- Updates ApiOptions.tsx and ModelPicker.tsx to support TARS.
Validation and Tests:
- Updates validation logic in validate.ts to include TARS.
- Adds tests in tars.spec.ts and updates existing tests to include TARS.

^{This description was created by}^{for 6f0ad59. You can customize this summary. It will automatically update as commits are pushed.}

roomote

Thank you for your contribution! I've reviewed the changes and the implementation looks solid overall. The code follows the established patterns used by other router providers and successfully addresses the requirements from issue #6747. I have a few suggestions for improvement that you might want to consider.

roomote · 2025-08-08T04:08:56Z

src/api/providers/fetchers/tars.ts

+				(rawModel.id.includes("openai") || rawModel.id.includes("google/gemini-2.5"))
+
+			const modelInfo: ModelInfo = {
+				maxTokens: rawModel.max_output_tokens || rawModel.max_tokens || 4096,


I noticed the handling here uses . Is this intentional? Could we verify if the TARS API actually returns both fields, or should we handle this more consistently?

For comparison, the Requesty fetcher only uses without the fallback. Would it make sense to align the approach?

roomote · 2025-08-08T04:08:57Z

src/api/providers/tars.ts

+	total_cost?: number
+}
+
+export class TarsHandler extends RouterProvider implements SingleCompletionHandler {


I noticed that doesn't override the method from the base class. Some other providers have specific temperature support logic for certain models (e.g., OpenAI o3-mini models don't support temperature).

Is this intentional, or should TARS have specific temperature handling for any of its models?

roomote · 2025-08-08T04:08:57Z

src/api/providers/tars.ts

+	total_cost?: number
+}
+
+export class TarsHandler extends RouterProvider implements SingleCompletionHandler {


Consider adding JSDoc comments to document the TARS-specific behavior, especially around the usage metrics processing which includes special handling for caching tokens. This would help future maintainers understand the implementation details.

For example:

roomote · 2025-08-08T04:08:57Z

src/api/providers/__tests__/tars.spec.ts

+	}),
+}))
+
+describe("TarsHandler", () => {


The test coverage looks good! Consider adding a few more edge case tests:

Handling when TARS API returns models with missing fields

Testing the behavior when API key is invalid

Testing model fetching with network errors

These additional tests would help ensure robustness of the implementation.

roomote · 2025-08-08T04:08:57Z

webview-ui/src/i18n/locales/en/settings.json

 			"error": "Failed to refresh models list. Please try again."
 		},
 		"getRequestyApiKey": "Get Requesty API Key",
+		"tarsApiKey": "TARS API Key",


Good job adding the English translations! Could we verify if translations need to be added for other supported languages to maintain consistency across all locales?

The project supports multiple languages (ca, de, es, fr, hi, id, it, ja, ko, nl, pl, pt-BR, ru, tr, vi, zh-CN, zh-TW), and it would be good to ensure TARS-related strings are available in all of them.

daniel-lxs

Thank you for adding TARS as a provider! The implementation looks good overall, but I have some concerns about UI consistency that should be addressed before merging.

daniel-lxs · 2025-08-14T17:12:10Z

webview-ui/src/components/settings/providers/Tars.tsx

+				<VSCodeButtonLink href="https://router.tetrate.ai" style={{ width: "100%" }} appearance="primary">
+					{t("settings:providers.getTarsApiKey")}
+				</VSCodeButtonLink>
+			)}


The refresh button seems unnecessary here. Other router providers like OpenRouter and Requesty don't include a separate refresh button - they refresh models automatically when the API key changes. Could we remove this to maintain consistency?

The refresh functionality should happen automatically when the API key is entered, similar to how other router providers work.

I removed refresh button

daniel-lxs · 2025-08-14T17:12:10Z

webview-ui/src/components/settings/providers/Tars.tsx

+					<label className="block font-medium">{t("settings:providers.tarsApiKey")}</label>
+				</div>
+			</VSCodeTextField>
+			<div className="text-sm text-vscode-descriptionForeground -mt-2">


Instead of this conditional button, could we add a documentation link similar to OpenRouter? OpenRouter shows a "OpenRouter Documentation" link at the top of the component rather than a button.

The current approach with buttons makes the UI feel loaded and inconsistent compared to other providers. A simple documentation link would be cleaner and more consistent with the existing pattern.

I think documentation link is already handled similar with others. Let me know if I missed something.

…-provider

…-provider # Conflicts: # packages/types/src/provider-settings.ts

arifsetiawan · 2025-08-19T22:50:45Z

src/core/webview/ClineProvider.ts

 			userInfo,
 			enabled,
-			{ ...bridgeConfig, provider: this, sessionId: vscode.env.sessionId },
+			{ ...bridgeConfig, provider: this as any, sessionId: vscode.env.sessionId },


You can revert this change, the failing CI shouldn't be an issue while we figure out how to fix our NPM packages

- Replace 'any' with proper OpenAI.CompletionUsage type in tars.ts - Replace 'any' with 'unknown' type in CustomModesManager.ts - Maintains type safety while avoiding the use of 'any'

daniel-lxs

Thank you for addressing my previous reviews and sorry for the delay, there are a couple of unrelated formatting changes, could you revert those?

Also do not worry about the failing CI you saw, the ExtensionBridgeService depends on external packages and will be solved by us.

Let me know if you have any questions!

daniel-lxs · 2025-08-22T14:16:17Z

src/core/webview/ClineProvider.ts

 			userInfo,
 			enabled,
-			{ ...bridgeConfig, provider: this, sessionId: vscode.env.sessionId },
+			{ ...bridgeConfig, provider: this as any, sessionId: vscode.env.sessionId },


You can revert this change, the failing CI shouldn't be an issue while we figure out how to fix our NPM packages

daniel-lxs · 2025-08-22T14:16:53Z

src/core/tools/codebaseSearchTool.ts

 ) {
 	const toolName = "codebase_search"
-	const workspacePath = (cline.cwd && cline.cwd.trim() !== '') ? cline.cwd : getWorkspacePath()
+	const workspacePath = cline.cwd && cline.cwd.trim() !== "" ? cline.cwd : getWorkspacePath()


These changes seem unrelated

daniel-lxs · 2025-08-22T14:17:30Z

src/services/browser/__tests__/UrlContentFetcher.spec.ts

These changes seem unrelated

…-provider

arifsetiawan · 2025-08-29T08:03:41Z

@daniel-lxs, I reverted unrelated changes.

hannesrudolph · 2025-09-23T00:19:27Z

Thanks for the issue and accompanying PR to add this API provider. We haven't heard community interest in supporting this provider specifically, so we're not moving forward with it at this time.

For now, users can use the OpenAI Native provider with this service since it's compatible. If we see more community demand for dedicated support, we'll reconsider.

Closing this to keep the tracker focused on providers with clear demand. Appreciate the work you put into this—the implementation looked solid. If community support materializes, please open a new issue referencing this one.

missBerg · 2025-09-30T09:22:36Z

Hi @hannesrudolph 👋, having this work would make life a bit easier for me using Roo in VSCode 🙏

It's a bit annoying for me at the moment when I use TARS with Roo, so I would appreciate any improvements that make setup, configuration, and cost visibility easier.

What blockers are there to bring this code in?

Add TARS as provider

6f0ad59

arifsetiawan requested review from cte, jr and mrubens as code owners August 8, 2025 04:04

github-project-automation bot added this to Roo Code Roadmap and Roo Code Roadmap Aug 8, 2025

github-project-automation bot moved this to Triage in Roo Code Roadmap Aug 8, 2025

github-project-automation bot moved this to New in Roo Code Roadmap Aug 8, 2025

dosubot bot added size:XL This PR changes 500-999 lines, ignoring generated files. documentation Improvements or additions to documentation enhancement New feature or request labels Aug 8, 2025

roomote bot reviewed Aug 8, 2025

View reviewed changes

hannesrudolph added the Issue/PR - Triage New issue. Needs quick review to confirm validity and assign labels. label Aug 8, 2025

fix translation

a1e3535

daniel-lxs moved this from Triage to PR [Needs Prelim Review] in Roo Code Roadmap Aug 11, 2025

hannesrudolph added PR - Needs Preliminary Review and removed Issue/PR - Triage New issue. Needs quick review to confirm validity and assign labels. labels Aug 12, 2025

arifsetiawan mentioned this pull request Aug 14, 2025

Add Tetrate Agent Router Service (TARS) as a native provider #6747

Closed

4 tasks

daniel-lxs requested changes Aug 14, 2025

View reviewed changes

daniel-lxs moved this from PR [Needs Prelim Review] to PR [Changes Requested] in Roo Code Roadmap Aug 14, 2025

hannesrudolph added PR - Changes Requested and removed PR - Needs Preliminary Review labels Aug 14, 2025

arifsetiawan added 6 commits August 19, 2025 12:00

Merge remote-tracking branch 'upstream/main' into feature/add-tars-as…

04579e2

…-provider

update tars page

1e84fcb

fix: add type assertions for tars provider compatibility

07a7877

Merge remote-tracking branch 'upstream/main' into feature/add-tars-as…

8119b11

…-provider # Conflicts: # packages/types/src/provider-settings.ts

add TARS provider translations for all locales

a23fb19

fix test

8e7fa56

arifsetiawan commented Aug 19, 2025

View reviewed changes

arifsetiawan requested a review from daniel-lxs August 20, 2025 00:41

daniel-lxs moved this from PR [Changes Requested] to PR [Needs Prelim Review] in Roo Code Roadmap Aug 20, 2025

hannesrudolph added PR - Needs Preliminary Review and removed PR - Changes Requested labels Aug 20, 2025

fix: remove any types from tars provider and CustomModesManager

87d4d00

- Replace 'any' with proper OpenAI.CompletionUsage type in tars.ts - Replace 'any' with 'unknown' type in CustomModesManager.ts - Maintains type safety while avoiding the use of 'any'

daniel-lxs requested changes Aug 22, 2025

View reviewed changes

daniel-lxs moved this from PR [Needs Prelim Review] to PR [Changes Requested] in Roo Code Roadmap Aug 22, 2025

hannesrudolph added PR - Changes Requested and removed PR - Needs Preliminary Review labels Aug 22, 2025

arifsetiawan added 8 commits August 29, 2025 13:57

revert changes

1052b20

revert changes

9a289fd

revert changes

7d6a6da

revert changes

1718264

Merge remote-tracking branch 'upstream/main' into feature/add-tars-as…

202ae37

…-provider

fix import

bf9b87d

revert changes

00fa9ae

revert changes

05f3b52

arifsetiawan requested a review from daniel-lxs September 4, 2025 23:04

hannesrudolph closed this Sep 23, 2025

github-project-automation bot moved this from New to Done in Roo Code Roadmap Sep 23, 2025

github-project-automation bot moved this from PR [Changes Requested] to Done in Roo Code Roadmap Sep 23, 2025

feat: add Tetrate Agent Router Service (TARS) as provider #6832

feat: add Tetrate Agent Router Service (TARS) as provider #6832

Uh oh!

Conversation

arifsetiawan commented Aug 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Related GitHub Issue

Roo Code Task Context (Optional)

Description

Test Procedure

Pre-Submission Checklist

Screenshots / Videos

Documentation Updates

Additional Notes

Get in Touch

Uh oh!

roomote bot left a comment

Choose a reason for hiding this comment

Uh oh!

roomote bot Aug 8, 2025

Choose a reason for hiding this comment

Uh oh!

roomote bot Aug 8, 2025

Choose a reason for hiding this comment

Uh oh!

roomote bot Aug 8, 2025

Choose a reason for hiding this comment

Uh oh!

roomote bot Aug 8, 2025

Choose a reason for hiding this comment

Uh oh!

roomote bot Aug 8, 2025

Choose a reason for hiding this comment

Uh oh!

daniel-lxs left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

daniel-lxs left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

arifsetiawan commented Aug 29, 2025

Uh oh!

hannesrudolph commented Sep 23, 2025

Uh oh!

missBerg commented Sep 30, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

arifsetiawan commented Aug 8, 2025 •

edited

Loading