Skip to content

docs(prompt-management): Document fetching prompts by label#18626

Open
inkeep[bot] wants to merge 1 commit into
masterfrom
docs-writer-ai-update-2026-07-17T09-58-49-904Z-cmvemr
Open

docs(prompt-management): Document fetching prompts by label#18626
inkeep[bot] wants to merge 1 commit into
masterfrom
docs-writer-ai-update-2026-07-17T09-58-49-904Z-cmvemr

Conversation

@inkeep

@inkeep inkeep Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Changes

This PR documents the new ability to fetch prompts by label, introduced in PostHog/posthog#71509.

Updates made:

  1. Added new "Labels" section - Explains what labels are (movable pointers to prompt versions like production, staging), how they work, and how to set/delete them

  2. Updated MCP tools table - The prompt-get tool description now mentions the label parameter

  3. Updated Python SDK example - Added example showing label='production' as an alternative to version=2

  4. Updated JavaScript/TypeScript SDK example - Added example showing label: 'production' as an alternative to version: 2

  5. Updated "Linking prompts to traces" section - Documented the new $ai_prompt_label property for tracking which label was used when fetching prompts

Key concepts documented:

  • Labels are movable pointers to specific prompt versions
  • label and version parameters are mutually exclusive (400 error if both provided)
  • Without label or version, the latest version is returned
  • Labels enable deploying prompt updates without code changes - just move the production label to a new version

This PR was created by the Inkeep Content Writer agent, which is maintained by the Docs and Wizard team. Please reach out on Slack for help if needed.

- Add Labels section explaining movable pointers to versions
- Update MCP tools table with label parameter for prompt-get
- Add Python and JS/TS SDK examples for fetching by label
- Document $ai_prompt_label property for trace linking
- Update trace linking code examples with label property
@inkeep
inkeep Bot requested a review from jurajmajerik July 17, 2026 10:00
@github-actions

github-actions Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Jul 17, 2026 10:13AM

@github-actions

Copy link
Copy Markdown
Contributor

Vale prose linter → found 7 errors, 4 warnings, 0 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/docs/prompt-management/index.mdx — 7 errors, 4 warnings, 0 suggestions
Line Severity Message Rule
9:177 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
31:24 warning Use 'Markdown' instead of 'markdown'. Vale.Terms
31:132 warning Use 'Markdown' instead of 'markdown'. Vale.Terms
31:161 warning Use 'Markdown' instead of 'markdown'. Vale.Terms
52:66 warning Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept. PostHogBase.ProductNames
80:22 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
85:137 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
90:26 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
116:248 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
308:1 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash
309:1 error Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash. PostHogBase.EnDash

@github-actions

Copy link
Copy Markdown
Contributor

Bundle report

Total JS (gzip)

6.73 MiB (+0.0 KiB / +0.0%)

Eager graph (modules shipped in each entrypoint's initial chunks)

Entrypoint Eager size Budget Modules
app 16.10 MiB (+0.2 KiB / +0.0%) report-only 1956
Largest modules in the app closure
Module Size
./src/data/mcp-tools.json 833.8 KiB
css ./node_modules/.pnpm/css-loader@5.2.7_webpack@5.101.3/node_modules/css-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[1]!./node_modules/.pnpm/postcss-loader@4.3.0_postcss@8.5.6_webpack@5.101.3/node_modules/postcss-loader/dist/cjs.js??ruleSet[1].rules[8].oneOf[1].use[2]!./src/styles/global.css 737.9 KiB
./src/components/Stickers/Stickers.tsx 696.4 KiB
./node_modules/.pnpm/@radix-ui+react-icons@1.3.2_react@18.3.1/node_modules/@radix-ui/react-icons/dist/react-icons.esm.js 481.4 KiB
./node_modules/.pnpm/rehype-raw@7.0.0/node_modules/rehype-raw/lib/index.js + 29 modules 395.1 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.cjs.js 364.8 KiB
./src/hooks/useCustomers.tsx + 54 modules 355.1 KiB
./node_modules/.pnpm/@posthog+icons@0.36.6_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/@posthog/icons/dist/posthog-icons.es.js 354.8 KiB
./node_modules/.pnpm/react-markdown@8.0.7_@types+react@16.14.66_react@18.3.1/node_modules/react-markdown/lib/react-markdown.js + 88 modules 351.4 KiB
./node_modules/.pnpm/cloudinary-core@2.14.0_lodash@4.17.21/node_modules/cloudinary-core/cloudinary-core.js 281.9 KiB
./src/components/ProductComparisonTable/index.tsx + 120 modules 278.6 KiB
./src/components/SearchUI/index.tsx + 87 modules 271.8 KiB
./gatsby-browser.tsx + 45 modules 248.0 KiB
./node_modules/.pnpm/d3@7.9.0/node_modules/d3/src/index.js + 208 modules 247.4 KiB
./src/components/Pricing/PricingSlider/Slider.tsx + 87 modules 239.9 KiB

Eager-graph budgets are report-only until a baseline is established. Sizes are gzip of public/**/*.js; eager size is webpack module source bytes for the modules actually shipped in the entrypoint's initial chunks (post-tree-shake).

@github-actions

Copy link
Copy Markdown
Contributor

Hey @jurajmajerik! This docs PR was generated for you by an agent. You're responsible for reviewing and merging it into production.

  1. Review and approve the PR
  2. Merge the PR
    a. Check the preview env and CI build and merge it yourself
    b. Enable auto-merge if you're confident in the changes

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants