-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Open
Description
When starting a new session in the CLI using a custom LM Studio provider (qwen/qwen3-coder-next), Goose crashes immediately after initiating an execute tool call. The application exits entirely without additional logs or a stack trace.
The issue began after upgrading to Goose v1.25.0. The same model and LM Studio setup previously worked without issues.
To Reproduce
Steps to reproduce the behavior:
- Run Goose CLI inside Linux Docker environment on a new project
- Begin interaction typing
Analyze project before starting to plan - The session starts an
executetool call - Goose crashes and exits immediately
Terminal output before crash:
β new session Β· custom_lm_studio qwen/qwen3-coder-next
20260219_4 Β· /workspace
πͺΏ goose ready β type a message to get started
ββββββββββββββββββββ 0% 0/262k
πͺΏ Analyze project before starting to plan
I'll analyze the project in the workspace to understand its structure and planning requirements.
βΈ execute
code: async function run() {
// List files in the workspace to understand project structure
const files = awa...
Application exits immediately after this point.
Expected behavior
Goose should execute the execute tool call normally and continue the session without crashing.
- OS & Arch: Linux (Docker container)
- Interface: CLI
- Version: v1.25.0
- Extensions enabled: Default (no additional extensions configured)
- Provider & Model: LM Studio (127.0.0.1, v0.4.2+2) β
qwen/qwen3-coder-next
Additional context
- LM Studio is running locally and accessible at
127.0.0.1. - The model
qwen/qwen3-coder-nextpreviously worked correctly before upgrading to Goose v1.25.0. - The crash happens consistently at the moment the
executetool is invoked during project analysis. - No stack trace, panic output, or additional logs are displayed before termination.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels