Skip to content

Conversation

@alexander-alderman-webb
Copy link
Contributor

@alexander-alderman-webb alexander-alderman-webb commented Jan 21, 2026

Description

Set the system instruction attribute, conforming to OTtel structure:

https://opentelemetry.io/docs/specs/semconv/registry/attributes/gen-ai/#gen-ai-system-instructions

Issues

Reminders

@github-actions
Copy link
Contributor

github-actions bot commented Jan 21, 2026

Semver Impact of This PR

🟡 Minor (new features)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).


New Features ✨

  • feat(langchain): Set system instruction attribute by alexander-alderman-webb in #5357

Internal Changes 🔧

  • ci: Fix path in AI integration tests by alexander-alderman-webb in #5347

🤖 This preview updates automatically when you update the PR.

@alexander-alderman-webb alexander-alderman-webb marked this pull request as ready for review January 22, 2026 13:16
@alexander-alderman-webb alexander-alderman-webb requested a review from a team as a code owner January 22, 2026 13:16
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

"type": "text",
"content": instruction.content,
}
for instruction in system_instructions
Copy link

Choose a reason for hiding this comment

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

System instructions field uses wrong key name

Medium Severity

The _transform_system_instructions function creates dictionaries with "content" as the key, but the docstring example in consts.py and other integrations (anthropic, pydantic_ai) consistently use "text" as the key for text parts. The docstring shows {"type": "text", "text": "You are a helpful assistant."} but the implementation produces {"type": "text", "content": "..."}. This inconsistency will cause the langchain integration to produce data in a different format than other integrations and what's documented.

Additional Locations (2)

Fix in Cursor Fix in Web

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.

2 participants