open-interpreter icon indicating copy to clipboard operation
open-interpreter copied to clipboard

Any plans on saving the generated scripts to files ?

Open KitoKotowa opened this issue 2 years ago • 4 comments

It can be pretty convenient to watch the code saved on a file, rather than seeing the generated code in the terminal

KitoKotowa avatar Sep 03 '23 14:09 KitoKotowa

Hey @KitoKotowa. For sure! The desktop app will let you export all the non-erroring code blocks in a chat session as a .py or .ipynb.

Perhaps we can implement this in the CLI first if enough folks want it. We're thinking of making some magic commands that control the interpreter from within the chat. Commands would start with %.

We could make it so %export or %export script.py exports all the non-erroring code blocks into the current directory. What do you think?

KillianLucas avatar Sep 04 '23 21:09 KillianLucas

That seems to be a good one, @KillianLucas. Although if you want to export to ipynb, the interpreter needs to be able to seperate markdown and python codes, so export to .py files only is a good start

KitoKotowa avatar Sep 05 '23 07:09 KitoKotowa

Hey @KitoKotowa. For sure! The desktop app will let you export all the non-erroring code blocks in a chat session as a .py or .ipynb.

Perhaps we can implement this in the CLI first if enough folks want it. We're thinking of making some magic commands that control the interpreter from within the chat. Commands would start with %.

We could make it so %export or %export script.py exports all the non-erroring code blocks into the current directory. What do you think?

Any word on that desktop app? Would love the ability to pick up and resume data analysis sessions (currently working with Jupyter + Interpreter + saving sessions, a bit archaic!)

djmango avatar Oct 27 '23 16:10 djmango

I think saving the code snippets in the CLI would be a very good feature!

jacksongoode avatar Nov 09 '23 04:11 jacksongoode