"goose session" fails to find configured provider #7889
Description
goose session fails with a "No provider configured. Run 'goose configure' first" error message after going through the setup instructions.
To Reproduce
curl -fsSL https://github.com/block/goose/releases/download/stable/download_cli.sh | bashgoose configure-> add local OpenAI compatible providergoose session
$ RUST_BACKTRACE=full goose session
thread 'main' (2050648) panicked at crates/goose-cli/src/session/builder.rs:362:10:
No provider configured. Run 'goose configure' first
stack backtrace:
0: 0x5d7c6a79bc12 - <std::sys::backtrace::BacktraceLock::print::DisplayBacktrace as core::fmt::Display>::fmt::h718e2d17a1928e63
1: 0x5d7c6a7b18cf - core::fmt::write::h1d2246b072ea91eb
2: 0x5d7c6a75d233 - std::io::Write::write_fmt::haf55272405c09d9b
3: 0x5d7c6a76d222 - std::sys::backtrace::BacktraceLock::print::h61c3bd81a9458a03
4: 0x5d7c6a773fff - std::panicking::default_hook::{{closure}}::haf1ffb5d1e33a97f
5: 0x5d7c6a773e59 - std::panicking::default_hook::hc32245deb6eaa988
6: 0x5d7c6a774685 - std::panicking::panic_with_hook::h43adc00fd0e494cb
7: 0x5d7c6a77446a - std::panicking::panic_handler::{{closure}}::h44391079756da3e7
8: 0x5d7c6a76d369 - std::sys::backtrace::__rust_end_short_backtrace::h934e1568393e5b8f
9: 0x5d7c6a74f99d - __rustc[d9b87f19e823c0ef]::rust_begin_unwind
10: 0x5d7c6a7bd590 - core::panicking::panic_fmt::h62031895f6e012da
11: 0x5d7c6a7bc3ab - core::option::expect_failed::h40dde8b63ee0f843
12: 0x5d7c64b6ab7f - goose_cli::session::builder::resolve_provider_and_model::h322f2ebb481c474a
13: 0x5d7c643022d3 - goose_cli::session::builder::build_session::{{closure}}::he1748930fd461ec6
14: 0x5d7c642efcb0 - goose_cli::cli::cli::{{closure}}::hf3c5b477289e884e
15: 0x5d7c64240ce4 - goose::main::{{closure}}::hb830e3023e24cd09
16: 0x5d7c644f7b97 - tokio::runtime::park::CachedParkThread::block_on::hc5a1324e943b54a6
17: 0x5d7c6496d91e - tokio::runtime::context::runtime::enter_runtime::hb6633c0894837ec7
18: 0x5d7c64a78ccb - goose::main::ha98f5be6ae219b52
19: 0x5d7c64ac2ef3 - std::sys::backtrace::__rust_begin_short_backtrace::hef42716616a613b7
20: 0x5d7c649035bd - std::rt::lang_start::{{closure}}::h49ba9b1565687bf0
21: 0x5d7c6a75f200 - std::rt::lang_start_internal::h00c7908c7c2f92b8
22: 0x5d7c64a9f235 - main
23: 0x77e841a2a1ca - __libc_start_call_main
at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16
24: 0x77e841a2a28b - __libc_start_main_impl
at ./csu/../csu/libc-start.c:360:3
25: 0x5d7c641de02e - _start
26: 0x0 - <unknown>
Expected behavior
A session should start.
- OS & Arch: Ubuntu 24.04 x86_64
- Interface: CLI
- Version: v1.27.2
- Extensions enabled: none
- Provider & Model: local llama.cpp, Qwen 3.5
Additional context
custom_qwen_3.5.json:
{
"name": "custom_qwen_3.5",
"engine": "openai",
"display_name": "Qwen 3.5",
"description": "Custom Qwen 3.5 provider",
"api_key_env": "",
"base_url": "http://10.10.10.2:11434/",
"models": [
{
"name": "Qwen 3.5",
"context_limit": 128000,
"input_token_cost": null,
"output_token_cost": null,
"currency": null,
"supports_cache_control": null
}
],
"headers": null,
"timeout_seconds": null,
"supports_streaming": true,
"requires_auth": false,
"catalog_provider_id": null,
"base_path": null
}Goose does know about the provider: it is listed in goose configure -> Custom providers -> Remove custom provider. I tried both "/" and "/v1" as the path of the URL, but the URL doesn't seem to have any effect on this.