Skip to content

fix: make LLM less apologetic, increase listDirectory result size #1242

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 2, 2025

Conversation

jguoamz
Copy link
Contributor

@jguoamz jguoamz commented May 2, 2025

Problem

  • LLM apologizes for when listDirectory fails because project is too big

Solution

  • Make LLM less apologetic, increase listDirectory result size to reduce the chance of this happening

Screenshot 2025-05-01 at 9 46 17 PM

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@jguoamz jguoamz marked this pull request as ready for review May 2, 2025 05:13
@jguoamz jguoamz requested a review from a team as a code owner May 2, 2025 05:13
@jguoamz jguoamz merged commit 572cabb into aws:main May 2, 2025
7 checks passed
@jguoamz jguoamz deleted the apologize branch May 2, 2025 16:03
if (toolResult.status === ToolResultStatus.ERROR) {
for (const content of toolResult.content ?? []) {
if (content.json && JSON.stringify(content.json).includes(outputLimitExceedsPartialMsg)) {
// do not send the content response back for this case to avoid unnecessary messages
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this could result in the duplicate explanation issue again

Copy link
Contributor Author

Choose a reason for hiding this comment

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

it shouldn't, this only happens for when result is too large

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.

3 participants