conversationStarters in Rovo agent

[Eunji Roh]

Hi,

I'm building a Forge Rovo agent and want to localize the `conversationStarters` shown on the empty agent screen (Korean / English depending on the user's profile language). I tried the standard manifest i18n object syntax:

```yaml
conversationStarters:
- i18n: agent.starter.appSetup
- i18n: agent.starter.other
```

but forge lint rejects it:

rovo:agent conversationStarters property X must be string.

Is there any supported way to localize conversationStarters (or other static rovo:agent fields like name / description)?

For the agent reply body I already use an action that detects user locale via /rest/api/3/myself and returns the correct-language summary verbatim, so the reply is bilingual — only the static starter chips are stuck in one language.

Thanks!

[Arkadiusz Wroblewski]

Hello @Eunji Roh 

As far as I know The Forge manifest schema doesn't support i18n keys for conversationStarters. The platform strictly requires a literal string here, which is why the validation error triggers. The same limitation currently applies to the agent's name and description fields as well.

@Dr Valeri Colon _Connect Centric_ 

Do you have information on whether that has been addressed at all?

I remember there was a feature/bug request about that.

Best,

Arkadiusz 🤠 ☀️