Choose a working mode and complete your first verifiable task in Qoder CN.
This guide uses a small change in a local project to walk through the full workflow from choosing how to work to verifying the result.
Prepare a local folder that contains the files you want Qoder CN to use. For a coding task, a small Git repository with a known test command is easiest to verify. Sign in to Qoder CN, then confirm that the task does not contain secrets or unrelated files that the Agent does not need.
Launch Qoder CN and sign in, then select Coding or General in the upper-left corner. Choose Coding when you need to edit code, run project commands, or use Git and Worktrees. Choose General for research, document handling, content work, and other folder-based tasks. Both modes provide the Agent and tools; Coding organizes tasks by workspace and exposes execution-mode and branch controls, while General organizes them by folder.
In Coding, select an existing workspace or add a local project as a workspace. After selecting one, confirm Local mode or Worktree mode and the current branch in the composer. Local mode works directly in the selected workspace. Worktree mode creates a separate copy of a supported Git workspace so that the task can run in parallel without occupying the current working tree. In General, select or add a folder. When local files are not required, continue without selecting a folder.
In the composer that is already open, describe:
Before you start
Prepare a local folder that contains the files you want Qoder CN to use. For a coding task, a small Git repository with a known test command is easiest to verify. Sign in to Qoder CN, then confirm that the task does not contain secrets or unrelated files that the Agent does not need.
1. Choose how you want to work
Launch Qoder CN and sign in, then select Coding or General in the upper-left corner. Choose Coding when you need to edit code, run project commands, or use Git and Worktrees. Choose General for research, document handling, content work, and other folder-based tasks. Both modes provide the Agent and tools; Coding organizes tasks by workspace and exposes execution-mode and branch controls, while General organizes them by folder.
2. Select the task scope
In Coding, select an existing workspace or add a local project as a workspace. After selecting one, confirm Local mode or Worktree mode and the current branch in the composer. Local mode works directly in the selected workspace. Worktree mode creates a separate copy of a supported Git workspace so that the task can run in parallel without occupying the current working tree. In General, select or add a folder. When local files are not required, continue without selecting a folder.
3. Create a task
In the composer that is already open, describe:
- Goal: what must be completed.
- Scope: which directories, files, or interfaces may be changed.
- Result: code, tests, documentation, or analysis only.
- Constraints: compatibility, coding conventions, excluded areas, and validation commands.
4. Select a model and access mode
- Model: use Auto to let Qoder CN choose, or select a model tier based on complexity and cost.
- Access permissions: choose Ask for approval, Auto approve, or Full access according to your risk tolerance. Keep approvals enabled when first working with real code. See Access Permissions.
5. Review and validate
- Confirm that the Agent used the intended workspace and files.
- Review the diff and inspect every material change.
- Run tests, builds, or static checks instead of treating the final message as the only proof of completion.
- Add missing requirements in the same conversation, or start a new task for an independent goal.
6. Organize the outcome
- Keep active tasks in Recent tasks.
- Archive sessions that no longer need attention.
- Use Automations for recurring work.
- Store durable project knowledge in a Knowledge Base or Repo Wiki when Knowledge Center is available.