coder3
efb774403e
Three fixes for reasoning_content handling:
1. agent.rs: Preserve reasoning_content when splitting parallel tool calls.
Providers like Kimi require reasoning_content on all assistant messages
with tool_calls when thinking mode is enabled.
2. openai.rs format_messages: Omit reasoning_content field entirely when
empty instead of sending empty string. Kimi rejects empty
reasoning_content ("").
3. openai.rs streaming: Properly accumulate reasoning_content chunks
across streaming deltas and emit as MessageContent::reasoning().
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: clayarnoldg2m <carnold@g2m.ai>
goose
a local, extensible, open source AI agent that automates engineering tasks
goose is your on-machine AI agent, capable of automating complex development tasks from start to finish. More than just code suggestions, goose can build entire projects from scratch, write and execute code, debug failures, orchestrate workflows, and interact with external APIs - autonomously.
Whether you're prototyping an idea, refining existing code, or managing intricate engineering pipelines, goose adapts to your workflow and executes tasks with precision.
Designed for maximum flexibility, goose works with any LLM and supports multi-model configuration to optimize performance and cost, seamlessly integrates with MCP servers, and is available as both a desktop app as well as CLI - making it the ultimate AI assistant for developers who want to move faster and focus on innovation.
Quick Links
- Quickstart
- Installation
- Tutorials
- Documentation
- Responsible AI-Assisted Coding Guide
- Governance
- Custom Distributions - build your own goose distro with preconfigured providers, extensions, and branding
Need Help?
a little goose humor 🦢
Why did the developer choose goose as their AI agent?
Because it always helps them "migrate" their code to production! 🚀