feat(api): add cognima provider support

[hiudyy]

Add the AI provider Cognima, it"s a Brazilian provider, I used it in openai compatible but I think it would be interesting to have it natively.

---

Important

Adds support for Cognima AI provider, including handler, model fetching, and provider settings integration.

• Behavior:
  • Adds CognimaHandler to handle Cognima API requests in index.ts and providers/cognima.ts.
  • Implements createMessage in CognimaHandler to convert messages and handle streaming responses.
  • Adds getCognimaModels in fetchers/cognima.ts to fetch models from Cognima API.
• Provider Settings:
  • Adds cognima to dynamicProviders and providerNames in provider-settings.ts.
  • Defines cognimaSchema in provider-settings.ts for provider configuration.
  • Updates providerSettingsSchemaDiscriminated and providerSettingsSchema to include cognimaSchema.
• Misc:
  • Adds cognimaApiKey to SECRET_STATE_KEYS in global-settings.ts.
  • Exports CognimaHandler in providers/index.ts and api/index.ts.
  • Updates MODELS_BY_PROVIDER in provider-settings.ts to include Cognima.

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

[roomote]

Review Summary

I've reviewed the Cognima provider implementation. The overall structure follows the established patterns for adding new providers, but there are a few issues that need to be addressed:

Issues Found

• Add cognimaModelId property to the cognimaSchema in packages/types/src/provider-settings.ts
• Remove unused parseApiPrice import from src/api/providers/fetchers/cognima.ts
• Add missing newline at end of packages/types/src/providers/cognima.ts
• Add Cognima model fetch logic to modelFetchPromises array in src/core/webview/webviewMessageHandler.ts
• Fix formatting: add space after comma in test expectation on line 224 of src/core/webview/__tests__/webviewMessageHandler.spec.ts

Follow Along on Roo Code Cloud

[roomote]

The cognimaModelId property is referenced here but is not defined in the cognimaSchema in packages/types/src/provider-settings.ts. The schema only includes cognimaApiKey. You need to add cognimaModelId: z.string().optional() to the cognimaSchema (around line 358) to match the pattern used by other providers like Groq.

[ellipsis-dev]

The import parseApiPrice is not used; please remove it to keep the code clean.

Suggested change

import { parseApiPrice } from "../../../shared/cost"

[roomote]

The parseApiPrice import is unused in this file and should be removed to keep the code clean.

[roomote]

Missing newline at end of file. Add a newline after the last line to follow standard conventions.

[roomote]

Review complete. Found 3 issues that need to be addressed before approval. Please see the inline comments for details.

[roomote]

Two of the three issues have been resolved. One issue remains: the missing newline at the end of packages/types/src/providers/cognima.ts.

[roomote]

The cognima: {} entry initializes an empty model record, but there's no corresponding entry in the modelFetchPromises array (around lines 789-820) to actually fetch Cognima models from the API. Since Cognima is defined as a dynamic provider and has a getCognimaModels function in src/api/providers/fetchers/cognima.ts, you should add a fetch entry similar to other dynamic providers like glama or unbound. For example:

{
  key: "cognima",
  options: {
    provider: "cognima",
    apiKey: apiConfiguration.cognimaApiKey,
  },
}

Without this, users won't be able to see or select any Cognima models in the UI.

[roomote]

Missing space after comma. Should be { provider: "unbound", apiKey: "unbound-key" } for consistency with the rest of the codebase.

Suggested change

	expect(mockGetModels).toHaveBeenCalledWith({ provider: "unbound",apiKey: "unbound-key" })
	expect(mockGetModels).toHaveBeenCalledWith({ provider: "unbound", apiKey: "unbound-key" })

[roomote]

Review complete. There are still 2 minor issues to address before approval.

[roomote]

The latest commit adds proper test coverage for the Cognima provider. No new issues found in this update. There are still 2 minor issues remaining from the previous review that need to be addressed before approval.

[daniel-lxs]

Thanks for the contribution!. We’re not planning to add new third-party providers at this time, as we’re focusing on maintaining the existing integrations. Closing this for now, but thank you again for the PR and for your interest in improving Roo Code.