What workflows and tools can you keep in one CoCalc project?

A CoCalc project is a persistent shared Linux environment that can hold notebooks, terminals, code, documents, running services, discussion, history, and recovery in one place. That means the same project can support coding, data analysis, writing, and collaboration without splitting work across separate tools. It is a good fit when you need long-running work that multiple people (or AI agents) can return to, and less useful if you only need a one-off script in a disposable sandbox.

What one project can contain

According to CoCalc's own description, a single durable project keeps these elements together:

• Notebooks — interactive computational documents.
• Terminals — command-line access inside the project.
• Code — files and software the project runs.
• Documents — written material alongside the code.
• Services — running processes your collaborators already use.
• Discussion — conversation attached to the project.
• History and recovery — a record of changes plus the ability to restore earlier versions.

Because these live in one shared Linux project, collaborators see edits live and can open what an agent saves, or take over the work themselves.

Workflows this supports

Software build and use with AI

CoCalc's headline use case is building and using software with AI. You can run the integrated Codex agent or Claude Code, or run other command-line agents in project terminals. The agents work where the project lives, so they use the same files, tools, and running services your collaborators use. Note that Claude Code is described as an experimental preview on sites that enable it, and it works with your personal Claude Pro or Max subscription.

Multi-person collaboration

Since files and the running environment are shared, a team can work in the same project rather than syncing copies. Live edits and shared services reduce the "which version is current" problem.

Long-term maintenance

History and recovery matter when a project runs for months. You can trace what changed and restore an earlier version instead of rebuilding from scratch.

How CoCalc runs

You are not limited to one deployment style. CoCalc lists three paths:

Pricing and licensing details are on CoCalc's pricing page; support and sales are separate contact paths. The site does not state that any tier is free, so check the pricing page before assuming cost.

When this fits — and when it doesn't

Choose a single CoCalc project when you need persistent, shared, recoverable work with agents and collaborators in the same environment. Consider a lighter sandbox instead if your task is short-lived, single-user, and you don't need history or shared services. If you need a private deployment, the customer-operated path is the relevant option to evaluate.