Agent doesn't always see return value of developer view tool when reading file

[codyw912]

Describe the bug
When the agent views a file via the developer tool, the file contents output to CLI and logs, but the agent is unable to see the output (or thinks it is unable to). Here is the agent's explanation of what's happening, if it helps:

The developer__text_editor tool, when used with the command='view', successfully executes on the backend (as confirmed by external logs showing the file content was accessed), but it fails to return the actual file content within the response data provided back to the LLM agent. The LLM only receives a generic success confirmation message (e.g., {"content": {"text": "Tool call is done."}}), preventing it from accessing and utilizing the file's text for subsequent tasks like editing or analysis.

After switching the model (from gemini-2.5-pro to gemini-2.0-flash) and resuming the session, the agent was successful with the same task and resumed, but later on in the session the issue happened once again.

To Reproduce

Steps to reproduce the behavior:

1. Start a session with Goose using the CLI interface.
2. Ensure the developer extension is enabled.
3. Ask Goose to view the content of an existing file.

Expected behavior

The agent should be able to reliably view the contents of a file with the developer / view command.

Please provide following information:

• OS & Arch: macOS Sequoia 15.3.2
• Interface: CLI
• Version: Goose 1.0.17
• Extensions enabled: memory, computercontroller, git, developer
• Provider & Model: gemini-2.5-pro-exp-03-25 & gemini-2.0-flash

Additional context

Here are some logs from this interaction, with the text from uv.lock output truncated for brevity:
view_command_error.log