File generation

Ask a model to produce a file — a report, a spreadsheet, a chart, a slide deck — and it writes that file inside the Open Terminal sandbox using Python. It then opens the finished file in your file viewer and confirms the filename; the file also stays reachable through the terminal panel's file browser.

You do not need to write or read any code to use this. Describe the document you want and let the model produce it.

Requirements

File generation runs on the same code-execution path as Coding / Software Development, so it inherits that path's constraints: it works only with plain LLM models that support function (tool) calling, Native Function Calling must be enabled for the model (Admin → Settings → Models → the model's advanced params), a terminal has to be selected in the chat — the sandbox tools are resolved only then — and AI-Hub agents are not supported yet. See that page for the sandbox mechanics, the per-user isolation model, and the fact that generated files are kept indefinitely.

Recommended model — Workspace → Kimi-K2.6

Select Kimi-K2.6 in the model picker (under Workspace) when you want the model to produce a file.

File generation is a multi-step tool-calling loop: the model has to write correct Python, run it with run_command, read the result back, and then hand the file over with display_file. Reliability on that loop varies far more between models than the list of supported formats does — every AI-Hub text-generation model declares function-calling support, but declaring it is not the same as carrying a multi-step build through to a finished file. Kimi-K2.6 is the model the format matrix below was verified against. If another model answers without producing a file, try Kimi-K2.6 before concluding that the format is unsupported.

Native Function Calling still has to be switched on for the chosen model — it is not enabled by default.

Supported output formats

What you can ask for. Verified against the open-terminal-office:0.11.34 sandbox image — "Yes" means you get a real, working file; "Source only" means you get the diagram's text source rather than a picture; "No" means it cannot be done. This says nothing about whether the same format can be read back in as an upload.

Category	File formats	Can be generated
Text documents	DOCX, RTF, TXT, Markdown (.md), HTML	Yes
Portable documents	PDF	Yes
Spreadsheets	XLSX, XLS, CSV	Yes
Presentations	PPTX, PDF	Yes
Images (raster)	PNG, JPG/JPEG, TIFF, WebP, BMP	Yes
Video	MP4, WebM, MOV, GIF	Yes
Audio	MP3, WAV, OGG, FLAC	Yes
Source code	py, cs, java, ts, js, go, rs, cpp, sql, yaml, json, xml	Yes
Data exchange	JSON, XML, YAML, CSV	Yes
Knowledge bases	Markdown, HTML, Confluence storage format, MediaWiki	Yes
Diagrams (source)	SVG, Draw.io (.drawio), Mermaid, PlantUML	Source only
Diagrams (Visio)	Visio (.vsdx)	No

Known limitations

WARNING

• Diagrams are generated as source, not as pictures. SVG, Draw.io, Mermaid and PlantUML files are text or XML, so the sandbox writes them without trouble — but it ships no renderer for them (no cairosvg, mmdc, plantuml, Graphviz or Inkscape), so it cannot turn them into an image file. Ask for a raster image via matplotlib instead when you need a picture rather than a source file. Note that Mermaid returned in a chat response is a separate path: the chat UI renders that inline as a diagram, which is why a Mermaid answer can look rendered while a Mermaid file stays source.
• Visio (.vsdx) cannot be generated. There is no Visio library in the sandbox and no LibreOffice to convert through. Ask for .drawio or SVG source instead.
• Reading a format is not the same as writing it. TIFF and Visio files could not be read back into the sandbox as input during capability testing, even though TIFF generation works.
• The format list is tied to the sandbox image. It reflects open-terminal-office:0.11.34. Bumping that tag can add or remove libraries, and therefore formats, without any other visible change.