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

[arifsetiawan]

What specific problem does this solve?

Tetrate Agent Router Service (TARS) recently launched as a new AI router similar to OpenRouter. It provides unified access to multiple AI providers, with features like automatic fallbacks, and usage monitoring configured through its web UI. Learn more at https://tetrate.io/blog/announcing-tetrate-agent-router-service.

Currently, using TARS requires manually configuring it as a generic OpenAI-compatible provider with custom base URLs. This creates friction for users who want to try TARS, as they need to know the specific endpoint URL and models information (e.g. reasoning, context window, capability and prices)

We would like to add TARS as a native provider option in Roo Code, similar to how other AI routers are supported. This would Eliminate manual base URL configuration - just select "TARS" and enter API key and allow users to directly use the model without need to fill model details.

Additional context (optional)

No response

Roo Code Task Links (Optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear impact and context

Interested in implementing this?

• Yes, I'd like to help implement this feature

Implementation requirements

• I understand this needs approval before implementation begins

How should this be solved? (REQUIRED if contributing, optional otherwise)

Follow other AI router providers in the codebase:

• Add provider handler
• Model info
• Tests
• UI Components

How will we know it works? (Acceptance Criteria - REQUIRED if contributing, optional otherwise)

Given I am at Roo Code settings
When I choose TARS as provider and enter API Key
Then I will be able to select models from TARS
And the models show correct context windows and prices
And I can use TARS models for coding tasks in Roo Code

Technical considerations (REQUIRED if contributing, optional otherwise)

This will be similar to other routers providers implementation

Trade-offs and risks (REQUIRED if contributing, optional otherwise)

Should be none since it follows established patterns

[daniel-lxs]

Hey @arifsetiawan Thank you for the proposal, I'll assign this issue to you