Nostr Web Client

If it’s ok, I have a number of questions because it seems that my setup is still clunky.

I updated the url to the local host, this seems to be working now. I also seem to need to open the the project file and change the default agent name from Claude to the one I’m running. (Currently trying qwen2.5-coder)

The agent is replying to me in text, instead of actually developing an app… I don’t understand why.

Any suggestions?

chad 4mo ago 💬 1

I know that model supports tool use, but I recall a very similar experience when trying to use it with goose a while back. I'll need to set some of these models up to experiment so I can provide you with more robust feedback.

Reply to this note

Please Login to reply.

Discussion

TKay 4mo ago 💬 1

I would really appreciate the help!

chad 4mo ago 💬 1

I finally had a moment to test. This interaction needs 'some love'; I believe it would require an update to stacks-cli to be more aware of how this model interacts with tools.

I'm currently experimenting to see if we can make this work a bit more nicely.

TKay 4mo ago 💬 1

Sweet! Thank you for testing.

That’s what I reached as well based on your instructions.

Had to go and edit the agent.json manually to get here.

Stacks-CLI should ask me for the agents name at least, that would be very helpful.

But yeah, somehow it’s still not using tools correctly.

chad 4mo ago 💬 1

Indeed, this would require updates to stacks-cli's codebase directly to properly support this model.

Also, in case this might prove helpful, you can do `stacks agent -m ` to directly override the active model at runtime.

TKay 4mo ago

Very helpful.