Skip to main content
Your workspace is a real Linux computer with 100GB of storage. Files, databases, and projects survive across sessions. It’s not a sandbox that resets — it’s your agent’s permanent home.

​
What’s in a workspace

Files & folders

Browse, upload, and download files through the built-in Computer tab. Code gets syntax highlighting, notebooks render beautifully, and images preview inline.

Multiple projects

One workspace can hold many projects. Build a dashboard, a landing page, and an internal tool — all in the same place.

Connections

Each workspace has its own set of integrations — databases, SaaS tools, and APIs that the agent can use in any project.

Chat history

Every conversation is saved and resumable. Come back to any thread and pick up where you left off.

​
The Computer tab

The Computer tab is your file browser. From here you can:
  • Browse your workspace filesystem
  • Preview source code with syntax highlighting
  • View rendered notebooks, charts, and data tables
  • Preview images and markdown files
  • Upload and download files

​
Multiple chats, one computer

This is the key difference between camelAI and other AI coding tools. camelAI is computer-based, not project-based. Your workspace is the container — chats are just conversations about what’s in it.
  • Start a new chat anytime without losing your work
  • Work on different projects from different chats
  • If a conversation goes sideways, start fresh — your files are still there
Think of chats as conversations, not containers. You can always start a new chat and say “look at the project in /my-app and fix the login page” — the agent will find it.

​
Workspaces and organizations

  • One organization can have multiple workspaces (no limit during beta)
  • Team members share workspace access — multiple people can chat with the same agent
  • Each workspace has its own files, connections, email address, and published apps
  • In multiplayer chats, messages show author signatures so the agent knows who it’s talking to
Your workspace container sleeps after a period of inactivity to save resources. When you return, it wakes up automatically — you may notice a brief startup delay. Your files are always preserved regardless of container state.