shell command output | Dagger | Page 1

quick zephyr Mar 4, 2025, 2:51 AM

#

Just bumped into this again on llm latest and I wasn't in nav mode. Can record it if that helps. If I rerun my command I can see my output (its a file | contents) since the run is cached the 2nd time and I don't have any output from the llm

#

so it's not actually the call traces hanging around but the output from the llm replies

#

shell command output

quick zephyr Mar 4, 2025, 3:07 AM

#

this one was short enough for me to see that the output is actually there, but the last llm reply is shown after

Screenshot_2025-03-03_at_10.07.21_PM.png

#

and then rerun is what i wanted the first time

Screenshot_2025-03-03_at_10.09.57_PM.png

obsidian fox Mar 4, 2025, 2:57 PM

#

gotcha. yea, looks like this would be fixed by moving shell output beneath the progress that created it, can look into that today

obsidian fox Mar 4, 2025, 7:06 PM

#

@quick zephyr just pushed a change to do that, lmk if it helps

#

also, there's better detection of the input prompt being incomplete now, so if it helps you can start breaking input into multiple lines. it should respect unterminated springs, parentheses, pipes, etc. etc. etc.

#

(literally just tries parsing and checks for an IsIncomplete error, so should be pretty thorough)

#shell command output