Skip to main content
Everything you do in QoderWork happens inside a task. A task is a single AI work session with its own conversation, context, Task Monitor, and artifacts. Starting a New Task gives you a clean slate — anything you say there lives in that task’s history and doesn’t bleed into the rest of your work. This page walks through the New Task entry feature-by-feature: where to start one, what a task gives you, and what each control on the input bar does when you create one.

What a task includes

Every task carries its own:
  • Conversation history — the back-and-forth between you and the AI.
  • Working folder — the local folder bound via Work in a Folder (optional).
  • Workspace and model — the picker selections made for this task.
  • Attachments and context — files added through +, skills called through /.
  • Task Monitor — the live to-do list, tool calls, and used Skills & MCP for this run.
  • Artifacts — the concrete files (spreadsheets, docs, code, slides) produced by the run.
Two tasks never share any of these. That means you can run several tasks in parallel without one stepping on another, and you can come back to a finished task months later and find everything intact.

Where to start a New Task

QoderWork gives you two entry points; they all open the same empty composer.

Sidebar button

Click + New Task at the very top of the sidebar.

Empty state

When the window first opens with no task selected, the center area already is the New Task composer.

Creating a task

Once the composer is open, the input bar at the bottom exposes four controls and a send button. A complete task creation walks through them in order: describe → workspace → model → working folder → send.

Describe the task

The input box is the heart of the task. How well you write this single field caps the quality of the entire task. The most effective prompts are outcome-oriented — say what you want delivered, not the steps to get there. Brief it like a capable colleague: state the goal, the format, and any constraints.
QoderWork empty-state screen with the headline Beyond chat, get it done. above the subheading "Just tell QoderWork what you need - it plans, executes, and delivers, keeping you in the loop." The prompt input box below has the General workspace and Standard model selected, with Work in a Folder underneath
A more effective prompt:
Please research the current AI desktop assistant products on
the market, including QoderWork, Cursor, Windsurf, and GitHub
Copilot. For each product, summarize its core features, pricing
model, and target users. Then compile the findings into a
comparison table and export it as an Excel file.
A less effective prompt:
Research AI desktop assistant products.
The difference: the first one names the deliverable (comparison table + Excel), the scope (four specific products), and the columns (features / pricing / users); the second only names a topic and leaves QoderWork to guess — fine when it guesses right, wasted work when it guesses wrong.
When you’re stuck, structure the prompt as three blocks: Goal (what to deliver), Format (Excel / Markdown / PPT…), and Constraints (must include / must avoid).

Pick a workspace

The Workspace picker at the bottom-left of the input bar (default General) selects the workspace the task runs in. Each workspace comes with a tuned tool set and default prompt for its target use case.
Workspace picker menu with General, Design, Slides (Beta), and Writing (Beta) options
  • General — the default for everyday work; covers the broadest set of scenarios (file ops, data, research, automation).
  • Design — an AI-native design-as-code canvas; describe what you need in natural language and get a running, editable, deliverable design artifact on an infinite canvas.
  • Slides — use when you want QoderWork to produce a PPT directly.
  • Writing — for long-form documents and structured writing.
Keep General for most work; switch only when the task is clearly in one of the specialized lanes.

Pick a model

The Model picker at the bottom-right selects the model that powers the task. Models differ in capability, speed, and cost.
  • Standard — for everyday tasks; balances speed and quality.
  • Advanced — powerful and balanced for key tasks.
  • Premium — switch up when the task needs harder reasoning, higher quality, or has low tolerance for error (e.g. key reports, cross-file analysis).
  • Qwen series — best performance-to-cost ratio with a full leap in Agentic capability, able to complete long, complex tasks autonomously.
Model choice affects Credits — Premium consumes more. Most tasks succeed on Standard; only upgrade to Premium if you find the output isn’t good enough.

Pick a working folder (optional)

The Work in a Folder control binds the task to a specific local folder. Once bound, QoderWork reads and writes files there directly — no need to upload or export by hand.
Work in a Folder menu expanded, showing Select folder and Recent folders entries
  • Select folder — opens the system picker so you can browse to any local folder.
  • Recent folders — QoderWork remembers the last few you used, ready to reuse.
When it helps:
  • The task involves multiple local files (e.g. cleaning up every Word doc in a folder).
  • The output needs to land in a specific place (e.g. dropping a generated PPT into a project directory).
  • The task modifies existing code or design files.
When to skip it: conversational tasks (a single research question, a one-shot answer, a one-off draft). Artifacts will surface as download cards inside the conversation anyway.

Send

Once the prompt, workspace, model, and (optionally) working folder are set, click the send button at the right of the bar. The task is logged into the sidebar immediately, shows as Running, and the main area opens the Task Monitor panel on the right.
QoderWork already saves a draft while you type — switch away or close the window mid-prompt and you’ll find it again under Drafts in the sidebar.

New task or continue in the current one?

Both are useful. The simple rule:
  • Start a New Task when the next thing you want to do is unrelated to what’s on screen. A new task gets a fresh context window, doesn’t waste Credits replaying old history, and ends up in your Tasks list as a separately addressable item.
  • Continue in the current task when you’re iterating on the same outcome — re-sorting a table, asking a follow-up about the same research, or fixing one column of the spreadsheet that just got delivered. QoderWork keeps the full context, so it knows what “this table” means.
If you find yourself opening a new task just to “clear the screen,” you don’t have to — collapse the sidebar instead, and the existing task keeps running while you scroll. Save new tasks for genuinely new work.

Where your tasks live after they finish

Every task you start — submitted or not — is saved.
  • The Tasks tab in the sidebar lists every task, grouped under Recent, with a search box at the top.
  • A task that’s still running shows a live status; one that’s finished can be reopened to view the conversation, re-download artifacts, or send a follow-up.
  • Drafts you composed but never sent stay under Drafts in the sidebar.
That history is why you don’t have to “save” anything — tasks are the saved unit of work in QoderWork.

Next Steps

Expert Kits

Enable expert kits for domain-specific work

Connectors

Connect browser, calendar, Microsoft 365, DingTalk, and more

Models

Available models and how to pick one