Jack Amadeo
Jack Amadeo
Also snuck in a small change not to treat EOF/Cmd+D as an error.
Another way to experiment with this today is to run goose's developer extension in the dev container. This means the filesystem and shell calls happen in the dev container, while...
@eduardolat that would work for shell commands, but we'd need something else for file edits. goose could edit them on the host if mounted in the container, but the paths...
see also: https://github.com/lensapp/lens/issues/8181
I've tested HTTP servers with authorization headers and they appear to be set, so I don't think that is the problem. @kgeis what does your extension config look like? Is...
Thank you @kgeis , that's been very helpful! I tracked this issue down to this part of the transport flow: https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#listening-for-messages-from-the-server goose, using rmcp, issues a GET to open an...
I think rmcp should not block on waiting for this response. I agree with @kgeis that the spec does not say the server must immediately write headers for the event...
https://github.com/modelcontextprotocol/rust-sdk/pull/553 should fix this
Hey @GitMurf thanks for raising the issue -- I'm not able to reproduce it on main with copilot + gpt-4.1 ``` goose % ./target/debug/goose run -t "run ls -al and...
@GitMurf aha, I have an idea of what might be happening. I don't think it's related to the approval mode, I think it's because we're closing the output stream too...