Changelog

The project setup experience is now easier to review while the agent runs:

• The setup step shows a concise objective checklist before events stream in.
• Agent events are rendered as structured cards with badges (Prompt, Status, Tool, Tool output, Pull request).
• The setup backend emits a dedicated pr_created event so the UI can reliably show an Open pull request link.

The setup prompt was also tightened to produce a minimal, reference-ready GLOSSIA.md aligned with selected target languages and the documented GLOSSIA.md structure.

The profile avatar section now uses a dedicated native multipart form with a standard file input and submit action. This avoids custom upload picker behavior and improves reliability in Chrome while keeping the same image validation and avatar storage behavior.

You can now manage GitHub connections from a dedicated Account page in the avatar menu. The sidebar GitHub settings link has been removed to keep account management in one place.

We renamed the contributor conversation surface from Tickets to Discussions.

What changed:

• Sidebar navigation now links to Discussions.
• Dashboard routes now use /discussions (legacy /tickets routes continue to resolve).
• Admin views now use Discussions labels and /admin/discussions routes.
• The application layer now uses Glossia.Discussions as the primary context.
• Suggestion links from voice and glossary now point to discussion URLs.

This keeps the product language aligned with the suggestion-driven collaboration workflow while preserving backward compatibility for older links.

The Glossary editor now makes pending edits much easier to spot:

• Changed terms, definitions, and translation rows are visually highlighted while editing.
• Added or modified glossary entry blocks are highlighted so reviewers can quickly scan what changed.
• The request finalization page now shows proposed glossary changes in the same term-card layout as the editor (read-only), with clear added/updated/removed highlighting.

The suggestion flow also keeps draft context in the URL, so canceling or navigating back from the suggestion creation page returns to the edited glossary state without losing in-progress changes.

Voice and glossary collaboration now supports a proposal workflow:

• Users without direct write access can edit the forms and submit a suggestion instead of saving immediately.
• Suggestions are stored as structured discussions (voice_suggestion or glossary_suggestion kind).
• Voice and Glossary pages now show open related suggestions.
• Maintainers with write access can open a suggestion discussion and apply it directly from the discussion page.

This keeps direct edits restricted while still letting external contributors propose concrete updates with full context.

You can now create and manage account tokens and OAuth applications directly from the API section in your account dashboard.

Account tokens let you authenticate with the Glossia API from scripts, CI pipelines, or any tool that needs programmatic access. Each token can be scoped to specific permissions and set to expire after 30, 60, or 90 days.

OAuth applications let you build integrations that access Glossia on behalf of users. Register an application to get a client ID and secret, then use the standard OAuth 2.1 authorization code flow with PKCE to obtain user tokens.

Both features are available to account admins under the new API section in the dashboard sidebar.

We started working on Glossia, a platform for teams who want to manage multi-lingual and mono-lingual content with AI at the core. Here are the first pieces we built:

What we built so far

• Voice and glossary management to keep your content consistent across every language.
• GitHub and GitLab integrations so content updates flow straight from your repositories.
• Organization and member management with role-based access control.
• A public REST API and MCP server for programmatic access to all platform features.

Follow this changelog for updates as we keep building.

Sharing a Glossia link on Twitter/X, LinkedIn, Mastodon, or Slack now renders a rich preview card with the page title, description, and category. Images are generated lazily on the first request and cached on S3 so subsequent hits are fast.

Every marketing page (blog posts, features, docs, changelog) and every public account or project page gets its own unique image. When content changes the hash changes, so the cache invalidates automatically.

We added a super admin system for internal operations. Super admins can manage users, accounts, and access from a dedicated /admin area with its own layout and a private MCP server for programmatic administration.

We added a Tickets section to every account dashboard. You can now submit tickets to report issues or request features without leaving the app.

Each ticket supports a full conversation thread so our team can ask for details and keep you updated on progress. Tickets have clear status labels (open, in progress, resolved, implemented) so you always know where things stand.

Super admins can manage all tickets from the admin panel, reply as staff, and update ticket status. The same operations are available through the admin MCP server for integration with LLM tools.

The Voice page has a new About section at the top. It includes:

• A description field where you briefly explain what you do and who you serve.
• A target countries picker with searchable country flags. Add as many countries as you need.
• Cultural notes generated by AI for each selected country. When you fill in a description (20+ characters) and add at least one country, Glossia generates tailored cultural advice for communicating in that market. You can edit the generated notes before saving.

All new fields are versioned alongside the rest of your voice settings, so you can track changes over time in the version history.