-
-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gptme often tries to use python instead of ipython to execute python code #327
Comments
python instead of
ipython to execute python codepython instead of \
ipython to execute python code
python instead of \
ipython to execute python code\
\python instead of \
\\
ipython to execute python code
\
\python instead of \
\\
ipython to execute python codepython instead of
ipython to execute python code
python instead of
ipython to execute python codepython instead of \
ipython to execute python code
python instead of \
ipython to execute python codepython instead of
ipython to execute python code
python instead of
ipython to execute python codepython instead of
ipython to execute python code
python instead of
ipython to execute python code
We used to just use ```python and ```bash for python and shell tool, but had to change it since it kept trying/asking to run non-runnable code snippets/examples it showed using the same markup. I later changed it to just ipython/shell respectively, and it works much better, but it sometimes messes it up still. Tried different prompts, but hard to measure what has impact since it's somewhat rare/random. See #67 for backstory |
Perhaps not using ``` for tool execution could be a solution. Maybe use XML tags instead? |
@Miyou you can try that with the |
Maybe changing the name of the tool from python -> ipython? |
@bjsi Yeah I think that might help, could eval some small model which struggles and see if it helps. |
Just released https://github.com/ErikBjare/gptme/releases/tag/v0.26.0 Let me know if it still happens! |
Just happened to me again :( Although it had just mentioned the still-not-renamed
Might still be a lot more rare after the tool rename, should perhaps rename the tool file too. |
Would it work better by formatting tool calls using xml?
…On Tue, 14 Jan 2025 at 18:04, Erik Bjäreholt ***@***.***> wrote:
Just happened to me again :(
—
Reply to this email directly, view it on GitHub
<#327 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AN3UCA32HUT7J6QKVUFLMNT2KVGURAVCNFSM6AAAAABTP654HOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJQG42DOMZQGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@bjsi Possibly, I haven't tested it extensively. I assume different models struggle to different extents as well (but I almost only run Claude 3.6). |
I feel like this could be solved by adding some extra prompting around this
The text was updated successfully, but these errors were encountered: