Why goose though a json string instead of doing the job

[osenvosem]

Maybe a newby question, but I can't get it why after I give the Goose a prompt it does nothing except for returning a json string to the terminal? What do I do wrong?

{"name": "platform__manage_extensions", "arguments": {"action": "enable", "extension_name": "developer__text_editor"}}
{"name": "developer__text_editor", "arguments": {"command": "write", "path": "/repo/package.json", "file_text": "{\n  \"name\": \"gs\",\n  \"version\": \"1.0.0\",\n  \"description\": \"CLI tool to sync repositories\",\n  \"main\": \"src/index.js\",\n  \"bin\": {\n    \"gs\": \"bin/gitlab-sync.js\"\n  },\n  \"scripts\": {\n    \"build\": \"tsc\",\n    \"pkg-linux\": \"pkg package.json --targets linux-x64\",\n    \"pkg-macos\": \"pkg package.json --targets mac-x64\",\n    \"pkg-win\": \"pkg package.json --targets win-x64\"\n  },\n  \"prebuild\": \"npm run build\",\n  \"keywords\": [\"gs\", \"cli\", \"sync\"],\n  \"author\": \"Your Name\",\n  \"license\": \"MIT\",\n  \"dependencies\": {\n    \"axios\": \"^0.26.1\",\n    \"commander\": \"^9.4.1\",\n    \"dotenv\": \"^16.0.3\",\n    \"p-limit\": \"^3.1.5\",\n    \"simple-git\": \"^3.12.0\"\n  },\n  \"devDependencies\": {\n    \"typescript\": \"^4.7.4\",\n    \"@types/node\": \"^16.18.19\",\n    \"@types/commander\": \"^9.0.3\",\n    \"ts-node\": \"^10.9.1\"\n  }\n}"}}

[taniashiba]

It sounds like goose is returning to you the raw JSON string vs doing the execution. Have you verified that you've installed the latest version of goose correctly? That's usually what causes this to be the case.

[osenvosem]

Sure, I just installed Goose a couple of days ago to get familiar with it. We discussed this issue on Discord, but there’s no solution yet. I tried several models — the same ones that work great with Cline or Qwen-code, for instance. It looks like this might be a bug on Goose’s side.