Skip to content

PR #2613 broke goose cli developer shell tool calls #2767

@GitMurf

Description

@GitMurf

I mentioned this in the Discord but am bringing over all the info here.

This commit (which was large and changed a lot) has broken the github copilot provider in goose cli (and maybe other providers). Tools like developer shell commands output gets cutoff and only the first line or two gets sent back to the LLM. See my screenshot for example when trying to do an ls command. The notifications / "loader" or whatever you call it in the CLI you see repeated ("total 400") in numerous ways.

Here is the commit: 03e5549
Here is the PR: #2613

Here for example is what it looks like running the ls shell command:

Image

Here is the response from the LLM stating that all that returned was "total 400" instead of the ls command output:

Image

If I run the ls command in my shell you see the full real response starts with "total 400" which is all that is being returned to the LLM after the tool call (with the actual ls results being cutoff):

Image

Since the github copilot provider using models like gpt4.1 requires streaming, I wonder if that was not taken into account or tested for?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions