Import and export

The QuantCraft IDE’s File menu (in the Python editor toolbar above the editor) includes two helpers that connect your workspace to the rest of your computer:

• Export — save the file currently open in the editor to a .py file anywhere on disk.
• Import… — bring .py (or .json/other text) files from your computer into the workspace as new tabs.

Both actions open the standard system save / open dialog, so you can pick any folder on your machine.

---

Export

Use File → Export to save a copy of the active editor file to disk.

What it does:

• Takes the live contents of the file currently open in the editor (so any unsaved edits are included).
• Suggests a filename based on the tab title — the .py extension is appended for you, and characters that aren’t allowed in filenames are replaced with _.
• Opens a system Save dialog where you can change the name, choose the folder, and confirm.
• The dialog filter defaults to Python (.py), with All files as an alternative.
• After a successful save, a short confirmation appears.

Notes:

• Export works on one file at a time — the one currently focused in the editor.
• If no file is open in the editor, the menu shows a notice asking you to open one first.
• Export is independent of your linked workspace folder — the saved file goes wherever you point the dialog, not into the workspace folder. To copy a file inside your workspace, use Save As… in the File menu instead.
• The export feature is available in the desktop (Tauri) app. In the browser version it cannot open a native save dialog.

---

Import…

Use File → Import… to bring one or more files from disk into the workspace as new editor tabs.

What it does:

• Opens a system Open dialog with multi-select enabled, so you can pick several files at once.
• Filters offered:
  • Python (.py)
  • JSON (.json)
  • All files
• Reads each file as text and creates a new tab for it in the IDE.
• The new tabs use the filename you imported (with disambiguation — if a tab named strategy.py already exists, the imported one becomes strategy (1).py, strategy (2).py, and so on).
• Imported files land at the workspace root (no folder), so they appear at the top level of the Files sidebar. You can then drag them into a folder if you want.

Requirements:

• The IDE workspace has to be loaded. If you trigger Import while it’s still loading, a short notice asks you to wait.
• A workspace folder must be linked in the Files sidebar. Importing without one shows a message asking you to pick a folder first — Import writes new files to that folder so they’re part of your project on disk.
• Like Export, Import uses native file dialogs and is meant for the desktop app.

---

Tips

• Use Export to share a strategy — pick the strategy file, export it as .py, and send the file to a teammate. They can use Import… to bring it straight into their own workspace.
• Bulk import — drop a folder of .py files into your workspace by selecting them all at once in the Import dialog. Each one becomes its own tab.
• Keep names unique — Import auto-renames duplicates so it never overwrites an existing tab. If you preferred the imported file’s name, rename or delete the previous one and import again.
• For full configuration (UI prefs, accounts, packages list, etc.) use the global Export Config… / Import Config… items from the top app menu — those handle everything outside of the IDE editor itself.