Goose agent quirks
So I'm trying a docker-based selfhosted instance at home (using mostly default settings via docker-compose). One thing I struggle with is setting up AI tasks: when I set up the 'goose' module, I can run a workspace, it will do the task and all that, but I can't track the progress: when I click any of the task-related buttons in the ui, i get a blank screen like the one attached. At this point I'm running out of ideas... There are no visible error logs or details, no idea which 'user' is meant etc... anyone can help?
6 Replies
Did you use Coder Login in your template?
https://registry.coder.com/modules/coder/goose?tab=readme
indeed
it's currently a bug in the AgentAPI module - it doesn't work without
CODER_WILDCARD_ACCESS_URL. Here's a related github issue: https://github.com/coder/coder/issues/18779#issuecomment-3089380050 and docs explaining how to set up the workaround https://coder.com/docs/admin/setup#wildcard-access-urlGitHub
bug: /api/v2/users/chat/workspace/embed returns `"user" must be an ...
Is there an existing issue for this? I have searched the existing issues Current Behavior When using the new "Tasks" tab, after the workspace is created and code-server is ready, the left...
yeah i just saw this in the contributing channel
now trying to figure out how to do a wildcard acces via cloudflare tunnel (no public ip at home)
I see the underlying agent bug was resolved and now waiting for implementation in the main coder repo
hey @Pavel does this work now?
This issue should be resolved now