YouTip

Quest Mode is Qoder's autonomous coding feature, enabling AI agents to complete development tasks end-to-end. We only need to describe your goal, and Quest will autonomously perform requirement clarification, solution planning, code execution, and result verification—with almost no human intervention throughout the process. Qoder's core philosophy can be summed up in two sentences: Define the goal, review the results. Unlike Agent Mode, Quest Mode is designed for complex, long-running tasks—such as implementing a new feature or fixing deep bugs. We provide clear requirement descriptions, and AI handles all the how-tos. * * * ## Register and Install Qoder **First, click to visit (https://qoder.com/users/sign-up?referral_code=whhACoCj9WryAtAh2HAqjvE2ppbzwWtz) to register for a Qoder account** — Free Pro trial + 300 Credits !(#) **After registration, click the Download button in the top-right corner, and download the installer based on your computer's operating system.** !(#) After downloading, double-click the file to begin installation, then double-click the Qoder IDE icon to launch Qoder. ### Agent Mode vs. Quest Mode: How to Choose? Qoder provides two working modes, suitable for different scenarios: | Comparison Dimension | Agent Mode (Editor Mode) | Quest Mode (Task Mode) | | --- | --- | --- | | Interaction Style | Real-time conversation, step-by-step confirmation | Delegated execution, autonomous completion | | Suitable Tasks | Short-cycle debugging, learning, small refactoring | Complex feature development, long-running tasks | | Human Intervention | Full participation | Minimal intervention | | Result Delivery | Iterate and review as you go | Review after complete delivery | * Agent Mode is more like an intelligent pair programming partner, suitable for scenarios where you want to maintain control over the pace—such as quick refactoring, bug fixing, and exploring new libraries. * Quest Mode turns Qoder into an autonomous expert—you define what to do, and AI handles how to do it. * * * ## Switch to Quest Mode Click the Editor / Quest toggle button in the top-left corner of the interface to switch between the two modes: !(#) The interface is shown below: !(#) The Quest Mode interface is shown below: If you want to set Quest Mode as the default mode, go to Settings > Quest Mode, and enable "Quest Mode Layout". !(#) * * * ## Create Your First Quest Task ### Click Create Quest At the top of the left task list, click the **Create Quest** button to create a new task. !(#) ### 2. Select Scenario Quest provides three scenarios, choose based on your needs: | Scenario | Suitable Scenarios | Quest Behavior | | --- | --- | --- | | **Spec-Driven** | Complex features, refactoring, strict quality control | First align on scope, design implementation plan and acceptance criteria, then execute | | **Prototype Exploration** | 0-1 website building, rapid prototyping | Describe your website, and Quest will automatically set up the page structure | | **Create Tool** | Quick idea validation, creative experimentation | Start from an idea, and Quest will turn it into a working prototype | !(#) > **Tip**: Not sure which to choose? Leave it blank, and Quest will automatically determine the most suitable approach. Once a task starts, the scenario cannot be switched. * * * ## Spec-Driven Mode This is the most suitable mode for formal development tasks, with the complete flow as follows: ### Step 1: Requirement Clarification After entering the task, Quest may ask clarification questions in multiple-choice format. You can let Quest automatically choose the default answers, or manually select and continue, or skip directly to conversation. ### Step 2: Generate Spec Document Quest will automatically generate a structured Spec document, including: requirement description, design solution, task breakdown, acceptance criteria. The Spec document is displayed in the Spec Tab of the right output area, supporting streaming output and download. ### Step 3: Review and Modify Spec View the complete document in the right Spec Tab, and you can modify the Spec through conversation (adjustments can be made before clicking Run). When satisfied, click **Run Spec** to start execution. ### Step 4: Execute and Monitor During execution, the conversation area will update the todo list in real-time, and the Changed Files Tab in the output area allows you to view code changes. You can even add new requirements directly in the input box during execution, and Quest will dynamically adjust the plan. ### Step 5: Review Results After execution completes, the following operations are available depending on the environment: * **Local mode**: Accept (apply all changes) or Reject (discard all changes) * **Parallel mode**: Apply (merge to main branch) * **Remote mode**: Create PR (create Pull Request) * * * ## Prototype Exploration/Create Tool Mode These two modes are designed for rapid output, completely skipping the Spec document and going directly to execution. ### How to Describe Your Idea? Simply describe the effect you want in natural language, for example: * **Website**: Create a travel blog website, including home page, article list, and detail pages, using modern design style and responsive layout * **Prototype**: Build a Todo app that supports add, delete, and mark as complete, using card design and priority tags ### Subsequent Flow Quest will automatically select the technology stack, and after code completion, automatically run the preview. The Preview Tab in the output area will display the running results in real-time. If the page has errors, Quest will automatically check and fix. You can continue the conversation to iterate and adjust, for example: Change the main color to blue, add a search box, optimize mobile display. * * * ## Execution Environment Selection Quest supports three execution environments: | Environment | Characteristics | Suitable Scenarios | | --- | --- | --- | | **Local** | Directly modify main workspace, zero startup cost | Simple tasks, quick validation | | **Worktree** | Create hidden workspace in background, keep main branch clean | Medium complexity tasks, parallel multi-tasks | | **Remote** | Remote container execution, machine can be shut down | Complex long-running tasks, resource-intensive operations (requires GitHub repository configuration) | !(#) > Without a Git repository, only Local environment is supported by default. * * * ## Interface Layout Overview Quest Mode uses a three-column layout: * **Left Column (Task List)**: Manage all Quest tasks, status divided into Running / Action Required / Ready / Error * **Middle Column (Conversation Area)**: Display conversation history, update todo list in real-time during execution * **Right Column (Output Area)**: Contains Spec Tab (view/download Spec), Changed Files Tab (code changes and Accept/Reject), Preview Tab (real-time preview of website/prototype) * * * ## Related Links * Qoder Official Website: [https://qoder.com/](https://qoder.com/users/sign-up?referral_code=whhACoCj9WryAtAh2HAqjvE2ppbzwWtz) * Qoder Documentation: [https://docs.qoder.com/zh/quick-start](https://docs.qoder.com/zh/quick-start?referral_code=whhACoCj9WryAtAh2HAqjvE2ppbzwWtz) * Qoder Quest Mode: [https://docs.qoder.com/zh/user-guide/quest-mode](https://docs.qoder.com/zh/user-guide/quest-mode?referral_code=whhACoCj9WryAtAh2HAqjvE2ppbzwWtz)