Skip to main content
Features

Start a new task

Choose Coding or General, associate a project, and start a Qoder task.

Qoder provides two work modes: Coding and General. Both provide the Agent, models, access permissions, context, and attachments. The main differences are whether tasks are organized by workspace or folder and whether the composer provides engineering options such as the execution mode and branch.

Choose a work mode

ComparisonCodingGeneral
Task organizationGroups tasks by WorkspacesGroups tasks by Folders
Project entrySelect or add a workspaceSelect or add a folder
ComposerAfter selecting a workspace, confirm Local mode or Worktree mode and the current branchSelect a folder, or continue without one when local files are not required
Use Coding when you need to edit code, run project commands, work on a Git branch, or isolate parallel work in a Worktree. Use General for research, document handling, content work, and other tasks whose natural boundary is a folder. A mode does not restrict what you can ask; switch modes and select a more suitable workspace or folder when the nature of the work changes.
Go to Settings → Mode Configuration to change each mode's bound theme and the visibility of run locations, environment labels, task-card details, Browser local services, and file-change cards.

Choose an execution mode in Coding

  • Local mode runs the task in the selected workspace and uses its current file state. Choose it when you want Qoder to work with the files already open on your machine.
  • Worktree mode creates a separate copy of a supported local Git workspace. Choose it when you want to isolate the task or run work in parallel. The workspace must be a Git repository with a commit and Worktree support.
The execution mode belongs to the task's working boundary. If Worktree mode is unavailable, check that the selected workspace is a local Git repository with at least one commit, or continue in Local mode.

Create a task

1

Choose a mode

Select Coding or General in the upper-left corner. The project area in the sidebar changes to Workspaces or Folders.
2

Associate a project

In Coding, select an existing workspace or add a local project. After associating the workspace, confirm Local mode or Worktree mode and the current branch in the composer. In General, select or add a folder; continue without a folder when local files are not required.
3

Describe the outcome

In the New Task composer, state the expected result, allowed scope, constraints, and validation method. Use Add context or Add attachment when files, images, or other evidence are needed.
4

Confirm run settings

Select a model and review Access permissions for the operations this task may perform. Start voice input or Live voice when needed.
5

Send and review

After sending, review the Agent response, tool calls, and file changes. Continue with specific feedback, then run the agreed validation and review the Diff.

Write an effective instruction

Start with the outcome, then add success criteria, relevant files, constraints, and validation. Specify detailed steps only when the exact execution path is required.
Add a responsive project gallery to the existing website.
Reuse the current colors and components. Include a project list, filters, and detail links. Do not change sign-in or payment flows.
Check wide and narrow layouts, run the existing tests, and report the changes and validation results.

Continue or separate the work

Use the same task when you are refining the same outcome and the existing context still applies. Start a separate task when the goal, workspace, execution boundary, or success criteria change. This keeps each task easier to review, search, and archive. After a task starts, use Code review and commit to inspect changes and Task management to search, sort, filter, or archive tasks.