Skip to content
Merged
Show file tree
Hide file tree
Changes from 12 commits
Commits
Show all changes
17 commits
Select commit Hold shift + click to select a range
33de0e0
Add i18n framework with next-intl for 19 languages
lawrencecchen Mar 12, 2026
6c3198b
Add translations for de, fr, it, ja, zh-CN, zh-TW
lawrencecchen Mar 12, 2026
d496fa3
Add translations for ar, bs, da, es, km, no, pl, pt-BR, ru, th, tr
lawrencecchen Mar 12, 2026
9b801a3
Convert docs and legal pages to use useTranslations()
lawrencecchen Mar 12, 2026
b08bd7e
Add i18n to keyboard shortcuts component
lawrencecchen Mar 12, 2026
a85780c
Add i18n to wall-of-love, add missing blog posts to sitemap
lawrencecchen Mar 12, 2026
79eacda
Add keyboard shortcuts and wallOfLove translations to all locales
lawrencecchen Mar 12, 2026
a8748f1
Update bun lockfile for next-intl dependency
lawrencecchen Mar 12, 2026
f22779a
Fix t.rich() configPath: pass ReactNode not function for {var} interp…
lawrencecchen Mar 12, 2026
295c4f9
Fix configPath: use rich text tag instead of plain interpolation for …
lawrencecchen Mar 12, 2026
a2231e0
Fix t.rich() interpolation: use rich text tags for all ReactNode plac…
lawrencecchen Mar 12, 2026
cd3eefb
Escape ICU curly braces in socketCallout rich text across all locales
lawrencecchen Mar 12, 2026
dc8543e
Fix i18n issues: Khmer RTL, zh-CN quality, locale-aware testimonials,…
lawrencecchen Mar 12, 2026
f724861
Address PR review comments: metadata localization, blog fixes, legal …
lawrencecchen Mar 12, 2026
d08c8e8
Convert remaining layout/index metadata to generateMetadata
lawrencecchen Mar 12, 2026
f9f77ac
Add translated metadata keys to all locales, fix docs redirect
lawrencecchen Mar 12, 2026
e640389
Add translated docs page metaTitle keys to all locales
lawrencecchen Mar 12, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -1,14 +1,16 @@
import type { Metadata } from "next";
import { useTranslations } from "next-intl";

export const metadata: Metadata = {
title: "EULA — cmux",
description: "End-User License Agreement for cmux",
};

export default function EulaPage() {
const t = useTranslations("legal");
return (
<>
<h1>End-User License Agreement</h1>
<h1>{t("eula")}</h1>
Comment thread
cubic-dev-ai[bot] marked this conversation as resolved.
Resolved
Comment thread
coderabbitai[bot] marked this conversation as resolved.
Resolved
<p>Last updated: December 2, 2025</p>

<p>
Expand Down
File renamed without changes.
Original file line number Diff line number Diff line change
@@ -1,14 +1,17 @@
import type { Metadata } from "next";

@cubic-dev-ai cubic-dev-ai Bot Mar 12, 2026 •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: This heading is hardcoded in English on a locale-scoped page, so non-English locales won’t get a translated title. Restore the translation key usage for privacyPolicy.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At web/app/[locale]/(legal)/privacy-policy/page.tsx, line 12:

<comment>This heading is hardcoded in English on a locale-scoped page, so non-English locales won’t get a translated title. Restore the translation key usage for `privacyPolicy`.</comment>

<file context>
@@ -8,10 +7,9 @@ export const metadata: Metadata = {
   return (
     <>
-      <h1>{t("privacyPolicy")}</h1>
+      <h1>Privacy Policy</h1>
       <p>Last updated: December 2, 2025</p>
 
</file context>
Fix with Cubic

import { useTranslations } from "next-intl";
import { Link } from "../../../../i18n/navigation";

export const metadata: Metadata = {
title: "Privacy Policy — cmux",
description: "Privacy policy for cmux",
};

export default function PrivacyPolicyPage() {
const t = useTranslations("legal");
return (
<>
<h1>Privacy Policy</h1>
<h1>{t("privacyPolicy")}</h1>
<p>Last updated: December 2, 2025</p>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

This policy is still only partially localized.

The heading moved to next-intl, but the body copy — including the inline “Terms of Service” link text you just touched — remains hard-coded English. That makes /[locale]/privacy-policy look translated when it is not.

Also applies to: 35-35

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@web/app/`[locale]/(legal)/privacy-policy/page.tsx around lines 11 - 15, The
page currently uses useTranslations("legal") for the heading but leaves the body
copy and the inline "Terms of Service" link text hard-coded English; update the
component in page.tsx to replace the hard-coded paragraph and the link text with
translation lookups using the t function (e.g., t("privacyPolicyLastUpdated"),
t("privacyPolicyBody"), and t("termsOfServiceLinkText") or similar keys) and
ensure those keys are added to the locale resource files for all supported
locales so the full body and link are localized; keep the existing structure and
link href but use t(...) for all user-visible strings in the component
(references: useTranslations, t in page.tsx).


<p>
Expand All @@ -29,7 +32,7 @@ export default function PrivacyPolicyPage() {
</p>
<p>
By using our Service, you accept this Privacy Policy and our{" "}
<a href="/terms-of-service">Terms of Service</a>, and you consent to
<Link href="/terms-of-service">Terms of Service</Link>, and you consent to
our collection, storage, use and disclosure of your information as
described here.
</p>
Expand Down
Original file line number Diff line number Diff line change
@@ -1,14 +1,16 @@
import type { Metadata } from "next";
import { useTranslations } from "next-intl";

export const metadata: Metadata = {
title: "Terms of Service — cmux",
description: "Terms of service for cmux",
};

export default function TermsOfServicePage() {
const t = useTranslations("legal");
return (
<>
<h1>Terms of Service</h1>
<h1>{t("termsOfService")}</h1>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Don’t expose a localized Terms route with English terms.

Only the <h1> is translated here; the actual Terms of Service remain hard-coded English. That makes the locale route look translated when it is not, which is especially risky for legal content.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@web/app/`[locale]/(legal)/terms-of-service/page.tsx around lines 10 - 13, The
page uses useTranslations("legal") only for the <h1> (t("termsOfService")) while
the Terms of Service body remains hard-coded English; update the component to
source the full TOS content from your localization system instead of inline
English — either replace the hard-coded text with translation keys accessed via
useTranslations (e.g., t("termsBody", { /* or t("termsParagraph1")... */ })) or
load a locale-specific markdown/JSON file and render it; ensure all text
currently in the body is mapped to translation keys or locale assets and
rendered via the same translated-source (symbols to change: useTranslations, t,
and the page component rendering the body).

<p>Last revised on: December 2, 2025</p>

<p>
Expand Down
File renamed without changes.
Original file line number Diff line number Diff line change
@@ -1,19 +1,14 @@
import type { Metadata } from "next";
import Link from "next/link";
import { useTranslations } from "next-intl";
import { Link } from "../../../../i18n/navigation";

export const metadata: Metadata = {
title: "Cmd+Shift+U",
description:
"How Cmd+Shift+U navigates between finished agents across workspaces in cmux.",
keywords: [
"cmux",
"terminal",
"macOS",
"notifications",
"AI coding agents",
"keyboard shortcuts",
"developer tools",
"workflow",
"cmux", "terminal", "macOS", "notifications", "AI coding agents",
"keyboard shortcuts", "developer tools", "workflow",
],
openGraph: {
title: "Cmd+Shift+U",
Expand All @@ -29,34 +24,30 @@ export const metadata: Metadata = {
description:
"How Cmd+Shift+U navigates between finished agents across workspaces in cmux.",
},
alternates: {
canonical: "https://cmux.dev/blog/cmd-shift-u",
},
alternates: { canonical: "https://cmux.dev/blog/cmd-shift-u" },
Comment thread
cubic-dev-ai[bot] marked this conversation as resolved.
Resolved
};

export default function CmdShiftUPage() {
const t = useTranslations("blog.posts.cmdShiftU");
const tc = useTranslations("common");

return (
<>
<div className="mb-8">
<Link
href="/blog"
className="text-sm text-muted hover:text-foreground transition-colors"
>
&larr; Back to blog
&larr; {tc("backToBlog")}
</Link>
</div>

<h1>Cmd+Shift+U</h1>
<h1>{t("title")}</h1>
<time dateTime="2026-03-04" className="text-sm text-muted">
March 4, 2026
{t("date")}
</time>

<p className="mt-6">
My favorite cmux feature is <kbd>Cmd+Shift+U</kbd>. I have 17
workspaces open right now, each running an agent. I used to click
through tabs and the notification panel to figure out what completed.
Typing is faster.
</p>
<p className="mt-6">{t("p1")}</p>

<video
src="/blog/cmd-shift-u.mp4"
Expand All @@ -70,12 +61,11 @@ export default function CmdShiftUPage() {
/>

<p>
<kbd>Cmd+Shift+U</kbd> jumps to the newest unread{" "}
<Link href="/docs/notifications">notification</Link>. In practice
that means the last agent that finished. It switches to the right
workspace, focuses the exact pane, flashes it so you see where to
look, and marks it read. If the notification came from another window,
that window comes forward.
{t.rich("p2", {
link: (chunks) => (
<Link href="/docs/notifications">{chunks}</Link>
),
})}
</p>
</>
);
Expand Down
70 changes: 70 additions & 0 deletions web/app/[locale]/blog/introducing-cmux/page.tsx
Original file line number Diff line number Diff line change
@@ -0,0 +1,70 @@
import type { Metadata } from "next";
import { useTranslations } from "next-intl";
import { Link } from "../../../../i18n/navigation";

export const metadata: Metadata = {
title: "Introducing cmux",
description:
"A native macOS terminal built on Ghostty, designed for running multiple AI coding agents side by side.",
keywords: [
"cmux", "terminal", "macOS", "Ghostty", "libghostty",
"AI coding agents", "Claude Code", "vertical tabs", "split panes", "socket API",
],
openGraph: {
title: "Introducing cmux",
description:
"A native macOS terminal built on Ghostty, designed for running multiple AI coding agents side by side.",
type: "article",
publishedTime: "2026-02-12T00:00:00Z",
url: "https://cmux.dev/blog/introducing-cmux",
Comment thread
cubic-dev-ai[bot] marked this conversation as resolved.
Resolved
},
twitter: {
card: "summary",
title: "Introducing cmux",
description:
"A native macOS terminal built on Ghostty, designed for running multiple AI coding agents side by side.",
},
alternates: { canonical: "https://cmux.dev/blog/introducing-cmux" },
Comment thread
coderabbitai[bot] marked this conversation as resolved.
Resolved
};

export default function IntroducingCmuxPage() {
const t = useTranslations("blog.posts.introducingCmux");
const tc = useTranslations("common");

return (
<>
<div className="mb-8">
<Link
href="/blog"
className="text-sm text-muted hover:text-foreground transition-colors"
>
&larr; {tc("backToBlog")}
</Link>
</div>

<h1>{t("title")}</h1>
<time dateTime="2026-02-12" className="text-sm text-muted">{t("date")}</time>

<p className="mt-6">{t("p1")}</p>

<h2>{t("whyTitle")}</h2>
<p>{t("whyP")}</p>

<h2>{t("featuresTitle")}</h2>
<ul>
<li><strong>Vertical tabs</strong>: {t("featureVerticalTabs").split(": ")[1] || t("featureVerticalTabs")}</li>
Comment thread
cubic-dev-ai[bot] marked this conversation as resolved.
Resolved

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Stop splitting localized feature copy on ASCII colon

The feature bullets parse translated strings with split(": ") to drop the label, but this assumes every locale uses an ASCII colon-plus-space delimiter. In this commit, several locales (for example ja, zh-CN, and zh-TW in web/messages/*.json) use full-width punctuation (:), so the split fails and the full localized sentence is appended after the hardcoded English label, resulting in duplicated/mixed-language output on the published blog page. Please avoid delimiter-based parsing here and use separate translation fields (or rich placeholders) for label vs description.

Useful? React with 👍 / 👎.

<li><strong>Notification rings</strong>: {t("featureNotifications").split(": ")[1] || t("featureNotifications")}</li>
<li><strong>Split panes</strong>: {t("featureSplitPanes").split(": ")[1] || t("featureSplitPanes")}</li>
<li><strong>Socket API</strong>: {t("featureSocketApi").split(": ")[1] || t("featureSocketApi")}</li>
<li><strong>GPU-accelerated</strong>: {t("featureGpu").split(": ")[1] || t("featureGpu")}</li>
</ul>
Comment thread
coderabbitai[bot] marked this conversation as resolved.
Resolved

<h2>{t("getStartedTitle")}</h2>
<p>
{t.rich("getStartedP", {
link: (chunks) => <Link href="/docs/getting-started">{chunks}</Link>,
})}
</p>
</>
);
}
File renamed without changes.
52 changes: 52 additions & 0 deletions web/app/[locale]/blog/page.tsx
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
import type { Metadata } from "next";
import { useTranslations } from "next-intl";
import { Link } from "../../../i18n/navigation";

export const metadata: Metadata = {
title: "Blog",
description: "News and updates from the cmux team",
};

const blogSlugs = [
"cmdShiftU",
"zenOfCmux",
"showHnLaunch",
"introducingCmux",
] as const;

const slugToPath: Record<string, string> = {

@cubic-dev-ai cubic-dev-ai Bot Mar 12, 2026 •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: slugToPath is typed too loosely. Use the blogSlugs union as map keys so missing slug mappings are caught at compile time.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At web/app/[locale]/blog/page.tsx, line 17:

<comment>`slugToPath` is typed too loosely. Use the `blogSlugs` union as map keys so missing slug mappings are caught at compile time.</comment>

<file context>
@@ -0,0 +1,52 @@
+  "introducingCmux",
+] as const;
+
+const slugToPath: Record<string, string> = {
+  cmdShiftU: "cmd-shift-u",
+  zenOfCmux: "zen-of-cmux",
</file context>
Suggested change
const slugToPath: Record<string, string> = {
const slugToPath: Record<(typeof blogSlugs)[number], string> = {
Fix with Cubic

cmdShiftU: "cmd-shift-u",
zenOfCmux: "zen-of-cmux",
showHnLaunch: "show-hn-launch",
introducingCmux: "introducing-cmux",
};

export default function BlogPage() {
const t = useTranslations("blog");

return (
<>
<h1>{t("title")}</h1>
<div className="space-y-4 mt-6">
{blogSlugs.map((slug) => (
<article key={slug}>
<Link
href={`/blog/${slugToPath[slug]}`}
className="block group"
>
<h2 className="text-lg font-medium group-hover:underline">
{t(`posts.${slug}.title`)}
</h2>
<time className="text-sm text-muted">
{t(`posts.${slug}.date`)}
</time>
<p className="mt-1 text-muted">
{t(`posts.${slug}.summary`)}
</p>
</Link>
</article>
))}
</div>
</>
);
}
Loading
Loading