Before you start
Culon Cowork is a 64-bit Windows desktop application. The application contains its document tools, OCR resources, Chromium and an embedded Node.js runtime, but it does not include a language model.
You need
- A Windows x64 computer. Windows 10 or 11 is recommended.
- About 131 MB for the installer and additional space for the installed application.
- One model connection: Ollama, LM Studio, a company OpenAI-compatible endpoint, OpenRouter or DeepSeek.
- A separate test folder for the first run. Do not begin with your only copy of critical documents.
Run a model in Ollama, LM Studio or your company network, leave web search off and do not enable external MCP servers. In this configuration, document processing can stay inside the local machine or network.
Download and install
- Download the installer only from this page. Culon-Cowork-Setup-0.1.0.exe
- Optionally verify the SHA-256 before running it.
- Run the installer, choose English or Russian, accept the license and select the installation folder.
- Keep the Start menu and desktop shortcuts enabled if you need them.
- Launch Culon Cowork after installation.
Verify the installer in PowerShell
Get-FileHash "$env:USERPROFILE\Downloads\Culon-Cowork-Setup-0.1.0.exe" -Algorithm SHA256
The result must be exactly:
BB320F39BE863F5A127F8CD4BB6D63BED7709997C6308F1363662C122EB8DCB9
Culon Cowork does not replace a proven working version automatically. Download a new release from the official page, validate it on a test workspace and roll it out at a convenient time.
Connect a model
Open Settings → Model. Choose a preset, fill in the model id and use the connection test. Cowork attempts to discover the context window and image-input capability from provider metadata.
Ollama
- Install Ollama and download a tool-capable model.
- Make sure Ollama is running.
- In Culon Cowork choose Ollama and enter the exact model id.
ollama pull qwen2.5
ollama list
| Field | Value |
|---|---|
| Base URL | http://localhost:11434/v1 |
| Model | The id from ollama list |
| API key | Not required |
LM Studio
- Load a model in LM Studio.
- Open the Developer / Local Server screen and start the OpenAI-compatible server.
- Choose LM Studio in Cowork and copy the model id shown by LM Studio.
| Field | Value |
|---|---|
| Base URL | http://localhost:1234/v1 |
| Model | Model id from LM Studio |
| API key | Usually not required |
Company or custom OpenAI-compatible endpoint
Choose “OpenAI-compatible endpoint”. Enter the base URL that exposes /chat/completions, the exact model id and a key if your gateway requires one. Examples include vLLM, TGI and LiteLLM.
OpenRouter / DeepSeek
Select the provider preset, paste your own API key and choose the model id. The key is returned to neither the renderer nor the settings form; on Windows it is stored through Electron safeStorage when OS encryption is available.
For office automation, choose a model with reliable tool calling, a context window large enough for your documents and vision support if screenshots or images are important. A very small local model may chat well but fail on long multi-step document work.
Run the first task
- Create a test folder and put copies of two or three documents into it.
- Click New task and choose that folder.
- Keep the permission mode at “In folder”.
- Describe a concrete output, not a vague conversation topic.
- Review permission cards on the right and approve only expected actions.
- Open the ready file from the result panel.
Good first prompts
Read all PDF files in the folder, create a one-page summary with a source table, and save the result as Summary.pdf.
Compare Contract-v1.docx and Contract-v2.docx. List all substantive differences and save a review-ready DOCX with tracked changes.
Use Quick chat only for short disposable questions. Its history is cleared when you leave the section, and it has no workspace or MCP access.
Permission modes
| Mode | Behavior | Use when |
|---|---|---|
| Every step | The application asks before actions. | First run, unfamiliar files or tools. |
| In folder | Safe inspection stays inside the workspace; writes and commands remain controlled by their classification. | Normal interactive document work. |
| Everywhere | External and MCP actions can run without interactive prompts. | Trusted autonomous or scheduled workflows. |
A confirmation card shows the intended action, path or command. Operations outside the selected workspace and unknown tools are classified conservatively. If the action does not match your task, reject it and clarify the request.
Documents and images
Plain reading uses the built-in PDF extractor. If a valid PDF has no text layer, Cowork automatically attempts offline Russian and English OCR. Advanced tasks can inspect form fields, fill and flatten forms, analyze text geometry, create print-ready PDFs and perform PDF transformations.
DOCX / XLSX / PPTX
Cowork uses format-specific playbooks. It can read Office files directly, reuse company templates, unpack OOXML for precise edits, validate and repair common package errors, and rebuild the final file. New documents are generated with the embedded Node runtime and bundled libraries.
Images and screenshots
Paste or drag up to five PNG, JPEG or WebP images into a message. A vision-capable model receives the images directly. With a text-only model, Cowork attempts offline OCR and sends the recognized text instead.
Checkpoints make result rollback possible, but a separate test copy remains the safest way to validate a new model, template or MCP tool.
Projects and durable memory
Create a project for work that continues across several tasks: a client, contract, tender, rollout or internal process. A project binds its workspace, tasks, history and context.
CULON.md — project rules
Write stable instructions that should apply to every task: tone, templates, approval rules, naming conventions and required sections. Cowork creates a comment-only starter file without overwriting existing content.
# Project rules
- Use the corporate template template.docx.
- All dates use YYYY-MM-DD.
- Never overwrite source files; save results under Results/.
memory.md — durable facts
Cowork can save facts useful in future tasks: requisites, signers, formatting preferences and recurring constraints. You can edit or delete this plain-text file at any time.
.culon/skills/<name>/SKILL.md — reusable workflows
Store a specialized workflow as a project skill. Cowork discovers it in the workspace and loads it only when the task requires it or when the request starts with /skill-name.
Scheduler
A scheduled task is a regular Cowork task with a workspace, permission mode, reasoning and optional web search, launched at a specified time.
- Open Scheduler.
- Choose Once, Every day or Every N minutes.
- Select the workspace and describe the output.
- Choose “In folder” for file work or “Everywhere” only when trusted MCP/external actions are required.
- Enable web search only if the report needs current online data.
- Keep Culon Cowork running in the background or tray and keep the model endpoint available.
The scheduler cannot wait for interactive permission prompts. Use a scope that is safe for the exact scheduled workflow and test it manually with copies first.
Web search and downloads
Turn on the globe toggle for tasks that need current information. Cowork can search with its built-in hidden Chromium, read selected pages without navigation boilerplate and download a file into the selected workspace.
Find the current prices and technical specifications for the three listed products. Use primary sources, include URLs and the access date, then update Report.docx.
Web search is read-only. A separate web download action writes a file and therefore follows file permission rules. The download limit is 50 MB per file.
MCP extensions
MCP connects Culon Cowork to external tools. Local servers use stdio; remote servers use Streamable HTTP. Open Settings → Extensions (MCP), click Add and paste one or more mcpServers entries.
Local stdio example
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "C:\\Work"]
}
}
}
Remote Streamable HTTP example
{
"mcpServers": {
"company-tools": {
"url": "https://mcp.example.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_TOKEN"
},
"timeout": 30000
}
}
}
- Paste the JSON and add the server.
- Enable its card.
- Start a new task so the available tools are refreshed.
- Use “Every step” while validating an unfamiliar server.
Culon Cowork cannot infer whether an arbitrary MCP tool is read-only. Every MCP call requires approval unless “Everywhere” is selected. Install only trusted servers and review their commands, environment variables, network access and data policy.
History, archive and rollback
Normal tasks are saved locally and appear in Task history. The timeline includes requests, answers, reasoning status, tool calls, permission decisions, terminal state and token usage.
Return to a completed point
Use the rollback action on a completed response. Cowork validates its checkpoint first, restores files that existed before the step, deletes result files created by that step and removes later conversation entries.
Archive versus delete
Archive hides a task or project from active lists and allows restoration. Delete removes the saved history permanently. Deleting a project also removes its linked tasks.
Troubleshooting and privacy
The model test fails
- Confirm that Ollama or LM Studio is running and that the Base URL includes the correct port and /v1 when required.
- Copy the exact model id from the provider. Display names and file names may not be valid ids.
- Check the API key for a cloud provider and the firewall for a company endpoint.
The model answers but does not create files
- Select a workspace folder; file creation and commands are blocked without it.
- Use a model with reliable tool calling and enough context.
- Ask for a specific output format and file name.
- Review pending permission cards on the right.
OCR is weak
- Use a higher-resolution scan with a straight page and strong contrast.
- Ask Cowork to mark low-confidence fragments instead of guessing them.
- For diagrams or photos, select a model with verified vision support.
Scheduled tasks do not run
- Keep the application running in the tray.
- Keep the model endpoint and required network connection available.
- Do not use “Every step” for an unattended task.
Where data goes
| Feature | Data path |
|---|---|
| Local model | To the local or LAN endpoint you configured. |
| Cloud model | To the selected provider according to its policy. |
| Web search | Search queries and page requests go to public websites/search engines. |
| MCP | Arguments and selected data go to the enabled MCP server. |
| Task history | Stored locally in the Culon Cowork application data directory. |
AI Platforms can help select the local model, deploy a compatible inference endpoint, define the access boundary and adapt project rules, templates and MCP tools to your workflow. Discuss deployment →