feat: Remove model tags from message content in human-relay

[NyxJae]

Related GitHub Issue

Closes: #2706

Description

This PR modifies the getMessageContent function in src/api/providers/human-relay.ts to ensure that <model>...</model> tags are removed from message content.

A new helper function, removeModelTags, has been introduced in src/api/providers/human-relay.ts to handle the stripping of these tags. The getMessageContent function now utilizes this helper to process both string content and text content within arrays of message parts. This change ensures that downstream consumers of the message content receive cleaner text, free of model-specific tags.

Test Procedure

Type of Change

• 🐛 Bug Fix: Non-breaking change that fixes an issue.
• ✨ New Feature: Non-breaking change that adds functionality.
• 💥 Breaking Change: Fix or feature that would cause existing functionality to not work as expected.
• ♻️ Refactor: Code change that neither fixes a bug nor adds a feature.
• 💅 Style: Changes that do not affect the meaning of the code (white-space, formatting, etc.).
• 📚 Documentation: Updates to documentation files.
• ⚙️ Build/CI: Changes to the build process or CI configuration.
• 🧹 Chore: Other changes that don't modify src or test files.

Pre-Submission Checklist

• Issue Linked: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above). (假设已链接)
• Scope: My changes are focused on the linked issue (one major feature/fix per PR).
• Self-Review: I have performed a thorough self-review of my code.
• Code Quality:
  • My code adheres to the project's style guidelines.
  • There are no new linting errors or warnings (npm run lint).
  • All debug code (e.g., console.log) has been removed.
• Testing:
  • New and/or updated tests have been added to cover my changes.
  • All tests pass locally (npm test).
  • The application builds successfully with my changes.
• Branch Hygiene: My branch is up-to-date (rebased) with the main branch.
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Changeset: A changeset has been created using npm run changeset if this PR includes user-facing changes or dependency updates. (由于函数行为改变，建议创建)
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

N/A (Backend logic change)

Documentation Updates

• No documentation updates are required.

Additional Notes

None.

---

Important

getMessageContent in human-relay.ts now removes <model>...</model> tags using the new removeModelTags function for cleaner message content.

• Behavior:
  • getMessageContent in human-relay.ts now removes <model>...</model> tags from message content.
  • Introduces removeModelTags function to strip model tags from strings.
  • Processes both string content and text content within arrays of message parts.
• Functions:
  • Adds removeModelTags to handle tag removal.
  • Updates getMessageContent to use removeModelTags for cleaner text output.

^{This description was created by for db95abee1057943021b419f0b00e315c6f340c55. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

The filtering on line 109 already ensures only items with type "text" pass through, making the ternary check in the map redundant. Consider simplifying it to simply map item => removeModelTags(item.text).

Suggested change

	.map((item) => (item.type === "text" ? removeModelTags(item.text) : ""))
	.map((item) => removeModelTags(item.text))

^{This comment was generated because it violated a code review rule: mrule_aQsEnH8jWdOfHq2Z.}

[ellipsis-dev]

Please add unit tests covering both removeModelTags and getMessageContent functions. Tests should cover cases with multiple, nested, or absent <model> tags to ensure robust functionality.

^{This comment was generated because it violated a code review rule: mrule_oAUXVfj5l9XxF01R.}

[adamhill]

🚀 (pending consideration of the comments)

[mrubens]

Any idea why the apiModelId is getting set to a random other model? It seems like the ideal approach would be to unset it for this provider and then only output it in the environment details if it's actually present.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 302dc2d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR