NeurionReference
Files, results & history
Attach local sources, inspect generated results, and preserve important work.
HydraLabs · Published
Open and review the output
Open the files, code changes, findings, and other results referenced by a task. Use the appropriate editor or viewer to inspect them, and review a diff before applying worktree changes.
A rendered artifact proves that a file can be displayed in that viewer. It does not establish that a model’s description is correct or that every operation mentioned in the response succeeded.
For code, check the actual changed files and validation. For a security report, retain evidence and scope. For a document or design, inspect the exported file in the application where it will be used.
Add documents, text, and images
Attach files with the composer’s file control or paste supported text and images. The local acceptance limits are 256 MiB per file and 1 GiB total per message. Images are limited to 20 per message and 20 MiB per image; supported image formats are PNG, JPEG, and WebP.
These are local file acceptance limits, not a promise to send 1 GiB in a single model request. Neurion keeps the original sources locally, processes documents on the device, and selects the relevant content for the model’s smaller working context.
PDF and DOCX documents support local text extraction. Scanned PDF pages use local OCR when text extraction is insufficient. OCR is text recognition, not a complete interpretation of diagrams, handwriting, tables, or page layout.
- Wait for document processing to finish before relying on its content.
- Use the page or section citations to inspect the source of a quoted passage.
- Provide an important chart or figure as a supported image when the visual meaning matters.
- If a source changes or is reported stale, attach the current version again.
- Split a selection that exceeds the message limit, and reduce an individual file that exceeds its own limit.
Encrypted, corrupt, unsupported, or over-limit files are rejected. Remove protection only when you have authority to do so, or provide the relevant content in another supported format.
Understand file viewers
Neurion provides viewers for supported code, diagrams, web content, and document formats. Available controls depend on the format. A viewer does not install the tools required to build or execute its source.
Notebook viewing does not provide an execution kernel. The small Python viewer is not a full Python environment. Use the project’s configured tools and approved command workflow when execution is required.
For DOCX, extracted paragraphs do not reproduce embedded images or the original page layout. For PDF OCR, verify critical numbers and wording against the original page.
Keep history and important files
Desktop conversations, project work, reports, and artifacts are stored on the device where they were created. The same account on another computer does not automatically receive these local files.
Use conversation search, pinning, and archiving to organize work. Save important outputs to a known project location and maintain your own backups. An account data export is not a backup of your entire computer or all local conversations.
Account and AI services still require online access. Local artifacts do not turn the entire application into an offline model service.