Skip to content

docs: align SEO handoff pages with product UI labels - #394

Merged
zxch3n merged 1 commit into
mainfrom
cursor/seo-docs-handoff-consistency-9f7b
Sep 4, 2026
Merged

docs: align SEO handoff pages with product UI labels#394
zxch3n merged 1 commit into
mainfrom
cursor/seo-docs-handoff-consistency-9f7b

Conversation

@zxch3n

@zxch3n zxch3n commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Audit of the SEO session-handoff / parallel-agents pages against product code found a few high-severity navigation errors: users following the published steps would open the wrong Settings page and look for a filter that does not exist.

This draft only corrects those facts. It does not rewrite the handoff marketing frame.

What this PR changes

  • Invite path: Settings → Workspace → General → Members, not Settings → Account → Members
  • Invite email: any sign-in email, not “GitHub-linked email”
  • Session list filter: sidebar My Tasks / All Tasks (mobile Team Tasks), default All Tasks — not a “GitHub Worktree filter”
  • Usage tab: AI Usage / By member (cited team.mdx)
  • Agent Session Control: gated on Developer mode + Tasks beta

Left for the audit report (not in this PR)

  • No per-session share grant (machine/project sharedWithTeam only)
  • No exclusive lock if two people prompt the same session
  • session.mdx still says fork is never a worktree (New worktree fork exists)
  • worktrees.mdx overclaims isolation for every task
  • Production unknown URLs still HTTP 200 after fix(site-docs): return HTTP 404 for unknown routes (stop soft-404) #383 merge (not deployed yet)

Test plan

  • Read the EN/ZH handoff, parallel-agents, team, and blog pages
  • Confirm labels match locales/en.json / zh_CN.json (settings.tabs.workspaceGeneral, sessions.sidebar.*, workspace.members.invite)
Open in Web Open in Cursor 

Correct Settings path, session-list filter names, invite email wording,
usage-tab label, and the Tasks-beta gate for Agent Session Control.

Model: cursor-grok-4.6

Co-authored-by: Zixuan Chen <zx@loro.dev>
@zxch3n
zxch3n marked this pull request as ready for review September 4, 2026 11:21
@zxch3n
zxch3n merged commit 20a822b into main Sep 4, 2026
5 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1728aadefc

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +16 to +18
These tools are available when **Developer mode** and the **Tasks** beta are on
(**Settings** -> **About**). Without that gate, a normal conversation cannot create or drive other
sessions this way.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Remove the nonexistent Tasks-beta prerequisite

When Developer mode or the Tasks beta is off—the default for ordinary users—this tells readers that session orchestration is unavailable, but buildLodyMcpServer registers lody_session_create and the other session-control tools unconditionally (apps/cli/src/mcp/lody-mcp-server.ts:4197-4215); the taskToolsEnabled check at lines 5049-5060 disables only the lody_task_* family. Users may therefore enable an unrelated experimental UI, or conclude that session control is unavailable when the hidden Developer-mode switch cannot be found. Remove this prerequisite or limit it specifically to Task tools.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants