suggestions felix

[felixkrrr]

Merge everything into 1 Prompt

Installation Experience

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
langfuse-docs	Ready	Preview, Comment	Mar 30, 2026 0:16am

[github-actions]

@claude review

[claude]

LGTM — straightforward docs enhancement. One nit noted inline (missing CopyAgentPromptButton in the Cursor tab), and copyable-agent-prompt.tsx appears to be unused in this PR.

Extended reasoning...

Overview

This PR refactors the agentic installation section of the get-started docs. It introduces topic-specific agent prompts (observability vs. prompt-management), a reusable CopyAgentPromptButton component, and wires the auto-install MDX component to receive a topic prop. Eight files are touched: six new component files and two existing docs pages.

Security Risks

None. All changes are UI/docs — MDX content, React components with clipboard API usage, and static text. No auth, data handling, or external requests introduced.

Level of Scrutiny

Low. This is a documentation site with no production-critical logic. The components follow established patterns in the codebase, and the conditional rendering logic is simple and readable.

Other Factors

One nit flagged by the bug hunter (missing CopyAgentPromptButton in the Cursor plugin tab — already noted as an inline comment). Additionally, copyable-agent-prompt.tsx is added but not imported or used anywhere in this PR; it may be intended for future use or is leftover, but it does not cause any functional issues. Neither issue warrants blocking the PR.

[claude]

🟡 The 'Cursor plugin' tab shows the agent prompt but is missing the that appears in the 'Ask your coding agent' tab. Adding after the prompt MDX components in the Cursor tab (around line 46 of auto-install.mdx) would restore consistency.

Extended reasoning...

Both tabs in auto-install.mdx display the same agent prompt via the conditional AgentPromptObservability / AgentPromptPromptManagement MDX components, and both were clearly intended to give users a prominent, labeled way to copy that prompt text. The PR introduced CopyAgentPromptButton and wired it up correctly in Tab 1 ('Ask your coding agent'), but the same button was not added to Tab 2 ('Cursor plugin').

The specific code path: in auto-install.mdx, Tab 1 ends with <CopyAgentPromptButton topic={props.topic} /> (line 20), while Tab 2 ends after the prompt MDX block with no corresponding button (lines 42–46). The import for CopyAgentPromptButton is already present at the top of the file, so the fix is simply a one-line addition.

Existing code does not compensate for this omission in a fully equivalent way. Fumadocs code blocks do render a small native copy icon, so the prompt text is not uncopyable — but that icon is small, unlabeled, and part of the code block UI rather than a standalone, discoverable action. The CopyAgentPromptButton is a larger, labeled button ('Copy Agent Prompt') that makes the action explicit, especially for users who may not notice the code-block icon.

The practical impact is a UX inconsistency: users who land on the Cursor plugin tab see a less polished experience than those on the first tab. The button's absence may also be mildly confusing if users notice it exists on Tab 1 but not Tab 2. There is no functional breakage, which is why this is nit-level.

The fix is minimal: add <CopyAgentPromptButton topic={props.topic} /> directly after the prompt MDX components in Tab 2, mirroring exactly what Tab 1 does. No new imports are needed since CopyAgentPromptButton is already imported.

Step-by-step proof: (1) A user visits the Cursor plugin tab. (2) They see the agent prompt rendered via AgentPromptObservability or AgentPromptPromptManagement. (3) They look for a 'Copy Agent Prompt' button like the one visible on the first tab — it is absent. (4) They must rely on the smaller native code-block copy icon or manually select the text. Meanwhile, a user on Tab 1 gets the large labeled button immediately below the prompt.