karthink
karthink
> I still strongly believe that manual editings of the `:GPTEL_SYSTEM: > ` in buffer `b` should be respected upon save of `b`. I don't see how this can work...
gptel's request parameters aren't like the customize system, for an important reason. The values in the customize buffer are "dead" until they're saved, at which point they become active. gptel's...
Closing as there is no planned action for gptel. The `GPTEL_*` Org properties are not intended to be manually edited. Hope the explanation provided in the above posts is clear.
> when using org-attach's "ID based" storage support. Can you give me an example of such a link?
Thanks for the explanation. This is tricky to do correctly. The parsing sequence works like this: 1. Copy prompt to a temp buffer 2. Strip property drawers from the buffer,...
This is still on my radar to fix, just not sure how to do it yet.
Which gptel backend are you trying to use? Have you tried gptel's Copilot backend (via `gptel-make-gh-copilot`)?
> Is there any way I can try different IP / auth method? What do you have in mind? > That's probably be one of reasons I can think of...
> ariane-emory created an issue (karthink/gptel#1024) > > Tool usage doesn't seem to work with local models hosted on ollama... it just prints the tool calls as part of the...
It looks like this model is generating tool calls as part of the response text, so there's nothing gptel can do to distinguish the two. I suspect the problem is...