[lilyshen0722]

The landing hero said each agent has "its own memory and workstation". Nothing in the code backs "workstation", and "its own memory" was true in code but never walked. This PR fixes that sentence, plus the two other landing strings that made the same claim, in English and zh-CN. It changes copy and the claim table only. No keys are added or removed.

What changes

Phrase	Verdict	Now	Evidence (claim-table rows, Other customer surfaces)
"its own workstation" / 工位	FALSE	Removed	git grep -i workstation over backend, cli and frontend/src finds no code (only a sentence about an operator's workstation in guides.json)
"its own memory"	true in code, not walked	"memory that stays with it"	Keyed by agent identity: backend/models/AgentMemory.ts:326 (unique {agentName, instanceId}); read as itself at backend/routes/agentsRuntime.ts:2781-2785, write at :2822 (ADR-003)
"no per-agent fees"	TRUE	Kept	backend/routes/billing.ts:91: one Pro line item, quantity: 1, no agent count. Same promise as pricing's "Never per agent" (#2805)

No-loss table (D138)

Every string this PR touches, before and after. Nothing else in either locale changes.

Key	Locale	Before	After	Lost?
landing.hero.lede	en	Get real work done with a team of AI agents — each with its own memory and workstation, all in one pod where they hand off instead of making you re-explain. Open source, your infra, no per-agent fees.	Get real work done with a team of AI agents — each with memory that stays with it, all in one pod where they hand off instead of making you re-explain. Open source, your infra, no per-agent fees.	Only the unbacked claim
landing.features.team.text	en	Claude Code, Codex and hosted agents side by side. Hire a hosted agent or connect your own — every one gets a name, its own memory, its own skills, and its own workstation. A real seat on the team, not a subagent you spawn and lose.	Claude Code, Codex and hosted agents side by side. Hire a hosted agent or connect your own — every one gets a name, its own skills, and memory that stays with it. A real seat on the team, not a subagent you spawn and lose.	Only the unbacked claim
landing.proof.sub	en	Role-specialized agents and a solo founder ship this project together — each agent with its own memory and workstation. Every agent-authored PR is labeled; {{count}} architecture decision records document the why.	Role-specialized agents and a solo founder ship this project together — each agent with memory that stays with it. Every agent-authored PR is labeled; {{count}} architecture decision records document the why.	Only the unbacked claim
landing.hero.lede	zh-CN	和一支 AI 团队一起把正事办成——每个智能体都有自己的记忆和工位，在同一个群里互相交接，不用你一遍遍重复解释。开源、部署在你自己的基础设施上，绝不按智能体收费。	和一支 AI 团队一起把正事办成——每个智能体的记忆都跟着它走，大家在同一个 Pod 里互相交接，不用你一遍遍重复解释。开源、部署在你自己的基础设施上，绝不按智能体收费。	Only the unbacked claim
landing.features.team.text	zh-CN	Claude Code、Codex 和托管智能体并肩协作。你可以雇一个托管智能体，也可以接入自己的——每个都有名字、自己的记忆、自己的技能、自己的工位。是团队里真正的一员，不是你用完就丢的子智能体。	Claude Code、Codex 和托管智能体并肩协作。你可以雇一个托管智能体，也可以接入自己的——每个都有名字、有自己的技能，记忆也一直跟着它。是团队里真正的一员，不是你用完就丢的子智能体。	Only the unbacked claim
landing.proof.sub	zh-CN	各有专长的智能体和一位独立创始人一起做出了这个项目——每个智能体都有自己的记忆和工位。每个由智能体提交的 PR 都有标注；{{count}}份架构决策记录写清了缘由。	各有专长的智能体和一位独立创始人一起做出了这个项目——每个智能体的记忆都跟着它走。每个由智能体提交的 PR 都有标注；{{count}}份架构决策记录写清了缘由。	Only the unbacked claim

Every other phrase in these three strings is unchanged: the pod and hand-off line, "Open source, your infra", the subagent contrast, the PR labelling and the ADR count. The zh-CN hero also replaces 群 with Pod, the locked glossary term, to match the English "pod".

zh-CN review (zh-cn-ui-localization)

Two passes, then adjudicated. Terminology: 智能体, 记忆, 技能 and Pod (with half-width spaces) all follow the glossary, and 工位 is gone with the English claim. Voice: "每个智能体的记忆都跟着它走" is the native way to say memory that goes where the agent goes. The team string reads "有自己的技能，记忆也一直跟着它" rather than stacking 的 phrases. No 您, and no banned calques.

Key	Before	After	Reason
landing.hero.lede	每个智能体都有自己的记忆和工位，在同一个群里互相交接	每个智能体的记忆都跟着它走，大家在同一个 Pod 里互相交接	Drop 工位 (unbacked), soften 记忆 to what code does, 群 → Pod (glossary)
landing.features.team.text	每个都有名字、自己的记忆、自己的技能、自己的工位。	每个都有名字、有自己的技能，记忆也一直跟着它。	Same claim change; breaks the four-way 自己的 stack
landing.proof.sub	每个智能体都有自己的记忆和工位。	每个智能体的记忆都跟着它走。	Same claim change

Renders (1440 and 390, en and zh-CN)

How the "after" frames were made: each pair is the live commonly.me landing page, rendered headless at 2x. "Before" is the page as served. "After" is the same loaded page with this PR's string written into the same element. These frames were not taken from a build of this branch. For a text-only change the layout comes from the text, so the frames show the real wrap and length. A preview after merge is still the final check.

String	Width	Locale	Before	After
hero	1440	en
hero	390	en
hero	1440	zh-CN
hero	390	zh-CN
team	1440	en
team	390	en
team	1440	zh-CN
team	390	zh-CN
proof	1440	en
proof	390	en
proof	1440	zh-CN
proof	390	zh-CN

Tests

No test pins these strings (a grep of frontend/src/**/__tests__ and frontend/scripts/*.test.mjs for the keys and both phrases finds nothing), and no keys changed, so locale parity holds. The full suite runs in CI.

Gate: Opus docs gate (D138), then a hand press. Found during the launch claim check of the landing page (Show HN links to it).

🤖 Generated with Claude Code

https://claude.ai/code/session_01MDs9DPuqzcZk8TdGaHUr5Y

[coderabbitai]

No actionable comments were generated in the recent review.

Recent review info

Run configuration

• Source mode: Auto
• Repository: Team-Commonly/commonly
• Branch: fix/landing-hero-claims
• File: .coderabbit.yaml
• Commit: 5560180
• Layers: Repository YAML
• Review profile: QUIET
• Plan: Advanced
• Run ID: 98b9df7f-4b39-4295-b16d-ac18028bc938

Commits

Reviewing files that changed from the base of the PR and between 63034af and 5560180.

Files selected for processing: 3

• docs/audits/claim-table.md
• frontend/src/i18n/locales/en.json
• frontend/src/i18n/locales/zh-CN.json

Limit details: You’ve used all 10 included reviews currently available.

Walkthrough

The English and Chinese landing-page copy now describes agent memory as staying with or following the agent, and no longer mentions an agent’s own workstation. The claim table records related memory, workstation, and per-agent fee claims.

Changes: Landing Copy and Claim Audit

Layer / File(s)	Summary
Update landing copy and claim records frontend/src/i18n/locales/en.json, frontend/src/i18n/locales/zh-CN.json, docs/audits/claim-table.md	The English and Chinese landing copy describes memory as staying with or following the agent and removes workstation wording. The claim table records the memory, workstation, and per-agent fee claims.

Priority: Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Possibly related issues

• Team-Commonly/commonly issue 709: The PR updates translated landing-page copy, which is within the issue’s listed translation scope.
• Team-Commonly/commonly issue 632: The landing copy and claim table describe agent-scoped memory, but the PR does not change memory behavior or add inspection features.

Merge Risk: Minimal · up to 55601

The landing copy accurately reflects the implementation, with no identified billing or runtime risk blocking merge.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title names the main change: it removes the unsupported "workstation" claim from landing copy and rewords memory to match what the code does. It is specific and matches the three landing strings a…
Description check		The description states the problem, the verdicts, and the before and after copy for the three landing strings in English and zh-CN. It also covers the claim table evidence, the lack of test pins, and …
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title names the main change: it removes the unsupported "workstation" claim from landing copy and rewords memory to match what the code does. It is specific and matches the three landing strings and the claim table update.

Full details: Description check

Explanation

The description states the problem, the verdicts, and the before and after copy for the three landing strings in English and zh-CN. It also covers the claim table evidence, the lack of test pins, and the rendered comparisons. It is directly related to the changeset.

Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Usage-based review receipt

• Mode: Continue automatically
• Reviewed files: 3
• Waived: $0.75 (charged $0.00)
• View usage details

Note

This review exceeded your plan’s limits and used usage-based reviews—free during trial, billed after paid activation unless disabled. Manage usage-based reviews.

_{Comment @coderabbitai help to get the list of available commands.}

[lilyshen0722]

D138 gate at 5560180.

Claims against code.

• "memory that stays with it": AgentMemory has a unique index on { agentName, instanceId } (AgentMemory.ts:326). The runtime reads it with findOne({ agentName, instanceId }) from the caller's resolved identity (agentsRuntime.ts:2784) and writes through PUT /memory (:2822). So memory follows the agent identity, not the install or runtime. The row honestly marks this "code path only, not walked".
• "workstation" / 工位: the row shows no backing code, and it's removed from all three strings in both locales.
• "no per-agent fees" (kept): billing.ts:91 creates one Pro line item at quantity: 1 with no agent count.

No loss. The diff touches exactly landing.hero.lede, landing.features.team.text and landing.proof.sub in en and zh-CN. Every other clause in those strings is unchanged (hand-off, open source / your infra, the subagent contrast, PR labels, ADR count). The team string keeps "a name" and "its own skills".

zh-CN. "每个智能体的记忆都跟着它走", "有自己的技能，记忆也一直跟着它" and "同一个 Pod 里" (half-width spaces) read natively. 群 → Pod matches the English and the glossary.

The renders in the body are the prod page with the strings swapped in. That's adequate for a copy-only change, since the new strings are shorter than the old ones in every case.

Written by Lumen, a Commonly agent — https://commonly.me/v2/pods/6a692a1be833c668acdb84cf
GATE: PASS