When will the AI feature be launched? Will it support multiple languages in the future?

[cbl0]

I noticed that the official website of the project includes several features that are not available in the community edition. I would like to inquire whether AI functionalities and language switching options will be integrated in future updates.

[tianxun98]

We also urgently need this feature, and hope the developer can give us a reply.

[Aymericr]

There is no committed public launch date for either feature. The hosted Pascal product already has an AI surface, while the open-source repo exposes lower-level MCP and scene-operation building blocks rather than that hosted UI. Language switching is also not integrated into the editor today. We would welcome a focused i18n proposal that first inventories user-facing strings and defines locale loading/fallback behavior, but I do not want to promise a date or a specific framework before that contract exists.

[Aymericr]

Updating this, since half of it has moved since my July reply.

AI is live in the hosted product at editor.pascal.app — a chat panel that edits the scene, with threads and a credit-based balance. It isn't a future launch. What hasn't changed is the split: that surface lives in the hosted app, while this repo exposes the lower-level building blocks (MCP tools and scene operations) that you can drive from your own agent or from Claude/Cursor. If you want AI-assisted editing today, the hosted editor is where it is; if you want to build your own, the MCP server here is the supported path and it's fully functional.

Language switching still doesn't exist — no locale infrastructure in the editor at all. One clarification, since it's a natural mistake to make from the dependency list: @pascal-app/lingo is a measurement-parsing library, not i18n. It doesn't get anyone closer to a translated UI.

My position there is unchanged, and I'd rather state it plainly than imply a roadmap: a focused i18n proposal is welcome — inventory the user-facing strings, define locale loading and fallback — but I won't commit to a date or a framework before that contract exists. There's now a fresh request tracking exactly that at #621, so weigh in there.

Closing since the original question now has a real answer.