conversationStarters in Rovo agent

Question

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!

Dr Valeri Colon (Connect Centric) · Answer

@Arkadiusz Wroblewski you were there!? Had I seen I would've taken a moment to celebrate you taking #1 on the Rovo Q&A leaderboard. Its no small feat, Rebekka has held the position for months. I learn new AI tips and tricks from the community all the time. I'm glad the analogies landed, I was making them up as I went.

Arkadiusz Wroblewski · Answer

@Dr Valeri Colon _Connect Centric_

Thanks for picking up the phone.😉

And for the good "food for thought" during the AI session—you think you know all of that, but it is always better to hear from somebody else, and you have quite the "Teacher of the Year" explaining style.

@Eunji Roh  That from Valeri and the important part report to Developer Community and JAC.

Rovo is in active development, so they need all the feedback possible to collect - like Pokemons - Catch them all 🤭😉

Best,

Arkadiusz 🤠 ☀️ 😎

Dr Valeri Colon (Connect Centric) · Answer

@Arkadiusz Wroblewski you rang ;)  I haven't found any documentation indicating that rovo:agent manifest fields currently support Forge i18n resources. The validation error suggests the schema still expects literal strings. As a workaround, some developers create multilingual conversation starters (e.g., English/Korean in the same string) or handle localization dynamically within agent responses, as you're already doing @Eunji Roh. If localization of agent metadata is important, this may be worth raising as a feature request in the Atlassian Developer Community or JAC.