3 ms·
Looks interesting! Does it support multiple tool calls in a chain, or only terminating with a single tool use? Why is there a flag to not upload my terminal hi
by CGamesPlay 11mo ago
Looks interesting! Does it support multiple tool calls in a chain, or only terminating with a single tool use?
Why is there a flag to not upload my terminal history and why is that the default?
- iagooar 11mo agoThanks! It does not support chaining multiple tool calls - if it did, it would not be a lightweight assistant anymore, I guess. The history is there to allow referencing previous commands - but now that I think about it, it should clearly not be on by default. Going to roll out a new version soon. Thanks for the feedback!
- CGamesPlay 11mo agoGiven that it doesn't support multiple tool calls, one thing I noticed that is not ideal is that it seems to buffer stdout and stderr. This means that I don't see any output if the command takes 10 minutes, and I also can't see stdout mixed with stderr. It would be ideal to actually "exec" the target process instead, honestly. https://doc.rust-lang.org/std/os/unix/process/trait.CommandExt.html#tymethod.exec https://doc.rust-lang.org/std/os/unix/process/trait.CommandE...
- iagooar 11mo agoThis one is a bit tricky. The tool needs the output to process stuff after the AI returns results. And since the focus is on rather short interactions, this is an OK-ish tradeoff I believe. But I will give it a couple more thoughts, not saying no to it, but need to go through the possible ramifications.