Workspace.

What the workspace is

When you attach a file to a single chat, it exists only in that chat. The workspace is different: files you upload here are permanently stored and can be attached to any conversation without re-uploading.

Workspace files can be surfaced automatically when relevant. When you send a message that's clearly about working with a document - "update my marketing plan", "review my code", "what does my strategy doc say" - Continio finds the most relevant workspace file using semantic matching and includes it in the response without you having to attach it manually.

This only fires when your message is genuinely about a stored document. General questions, personal conversations, and anything unrelated to files don't trigger it. Workspace files are never silently injected into unrelated conversations.

Uploading files

Files can be added to the workspace in several ways:

• Settings → Workspace - upload from the workspace panel directly
• Drag and drop - drag a file onto the workspace panel
• ZIP upload - upload a ZIP file and Continio extracts the readable text content, making it accessible from the workspace. Call read_file to access the extracted contents.
• Automatically - when Continio creates a file during a coding session, it is automatically saved to the workspace and tagged to the current project

ZIP files

When you attach a ZIP to a conversation or upload it to the workspace, Continio extracts the readable text files inside and makes the combined contents available via read_file. The ZIP is stored as a single workspace entry - Continio reads from it on demand rather than injecting all the content at once.

This is the right way to share a codebase: attach the ZIP, ask Continio to audit or continue building, and it will call read_file to access the extracted contents. Large ZIPs are never injected inline automatically - this prevents context overflow on large codebases.

Attaching workspace files to a conversation

Click the + button in the message input, then select From workspace. You can:

• Hover over a file and click Attach to add it immediately in one click
• Check multiple files then click Attach to add several at once

Files are injected into the conversation context. The model can read them via read_file() calls without the full content being loaded upfront - this keeps responses fast for large files.

Automatic file surfacing

You don't always need to manually attach a file. When Continio detects that your message is about a document you have stored, it automatically finds and includes the most relevant one. This uses semantic matching across your workspace, not keyword search, so it works regardless of how you phrase the request or what language you're using.

Examples that trigger automatic surfacing:

• "Can you update my content plan for next month?"
• "What did we decide in the marketing brief?"
• "Fix the bug in main.py"
• "Revise my proposal draft"

Examples that don't trigger it (general questions, personal chat, anything not document-related):

• "How do I cook venison?"
• "What should I post on Instagram today?"
• "I'm feeling overwhelmed"

If Continio surfaces the wrong file or you want a different one, attach it manually using the + button. Explicit attachment always takes priority.

Project scoping

Files saved during a session are automatically tagged to the project of the current chat. Any chat in that same project automatically knows those files exist. Continio sees a lightweight index of project files on every message and can read any of them on demand.

This means when you start a new chat in a project, even after a heavy coding session in a previous chat - Continio already knows what files are available without you having to re-attach them.

Files from other projects are not visible unless manually attached.

Versioning

Continio keeps a rolling history of the last 3 versions of every workspace file. When a file is updated - by Continio writing to it, by you re-uploading, or by attaching an updated file to a message - the new version becomes the current one and the oldest version drops off. A brief "filename v2 saved" toast confirms each update.

You can view version history from the workspace panel by clicking on any file. The most recent version is always what gets used in conversations.

Versions are tracked per filename. Re-uploading a file with the same name always versions it up rather than creating a duplicate.

Archiving files

Files not accessed in 30 days are automatically archived. Archived files are hidden from the active workspace list but are still fully accessible - Continio can still read_file them if asked. You can also archive files manually from the workspace panel.

To restore an archived file, open the collapsed "Archived files" section at the bottom of the workspace panel and click Restore.

Archiving is not deleting. Archived files count toward your storage but don't appear in the active file list or get injected into conversations automatically.

Supported file types for upload

txt, md, py, js, ts, jsx, tsx, json, csv, html, xml, yaml, yml, pdf, xlsx, xls, zip

Maximum file size: 50MB per file.

Note on GitHub exports and .tar.gz files: The file picker accepts .zip, .tgz, and .gz archives. If you're uploading a GitHub codebase export (which downloads as .tar.gz), some systems may not surface it in the file picker. If that happens, rename the file from .tar.gz to .tgz before uploading -- they're the same format and it will work correctly.

See the Limits & formats page for full details including unsupported formats.

Workspace availability and storage by tier

Your current storage usage is shown in the workspace panel. A warning appears at 80% capacity. New saves are blocked at 100% - archive or delete files to free space. Archived files still count toward your storage.

If you downgrade to Basic, your workspace files are retained but not accessible until you upgrade or purchase the workspace add-on. They are not deleted.