Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.qoder.com/llms.txt

Use this file to discover all available pages before exploring further.

Agent Mode is the autonomous programming capability within Quest. The Agent completes development tasks end-to-end — autonomously clarifying requirements, planning solutions, executing code, and verifying results, without continuous manual intervention.

​
Use cases

  • Feature development and refactoring: Ideal for developing new features, fixing tough bugs, or refactoring code. For tasks requiring clear technical plans, we recommend the Spec-driven scenario. The Agent will review the project context and generate a structured Spec document first, ensuring the overall direction aligns with your expectations before coding begins.
  • Rapid prototype validation: Best for validating product ideas or building demo prototypes from scratch. Choose the Prototype exploration scenario to skip the Spec and jump straight into coding. You can see the actual running results immediately using the real-time preview capabilities in the Summary Files area.
  • Automated tool building: Great for writing batch processing scripts, data cleaning tools, or custom CLI scripts. By choosing the Tool creation scenario, the Agent will automatically evaluate your environment and select the most appropriate tech stack to build the tool end-to-end.
  • Rapid iterative optimization: Perfect for exploratory adjustments. You can let the Agent deliver a basic MVP version first, and after reviewing the initial results, continue to rapidly iterate by adding natural language requirements in the chat (e.g., “make the button larger” or “switch to a dark theme”).

​
User guide

​
Create a task

Click the New Quest button at the top of the left task list, and select Agent mode in the popup panel. Here, you can specify your initial requirements and choose whether to enable Spec-driven execution.

​
Edit sent messages

If you realize you missed crucial context or gave incorrect instructions during a conversation, you can click a sent message bubble to enter edit mode. In edit mode, you can:
  • Modify prompts: Re-edit your input text to make it more precise.
  • Modify attached context: Add, remove, or replace files, code snippets, and screenshots attached to the message.
  • Switch models and modes: Switch to a more powerful model based on task difficulty or change the conversation mode.
After resubmitting your modifications, the workspace files will safely roll back to the state prior to that conversation turn. All file changes generated from that message onwards will be automatically discarded, allowing you to correct the course without any burden.
Context compression and one-click prompt optimization features are not supported in edit mode; manual adjustments are required.

​
Revert

During the Agent’s autonomous execution, if it takes a technical approach you don’t like or you’re unsatisfied with the code generated in the current turn, you can click the Revert button in the chat stream. The workspace will immediately be restored to the state before that turn’s operations, and the reverted content can be viewed and compared in the Diff View. This gives you a perfectly safe space for trial and error.
Experts mode currently does not support Revert.

​
Best practices

​
Write good task descriptions

Avoid vague instructions like “fix the code.” Clearly specify your specific goals, preferred tech stack, and acceptance criteria (e.g., “Write a React table component with pagination”). Use @ to reference related files or code snippets, which greatly helps the Agent accurately understand the project context.

​
Choose the right scenario and environment

  • By complexity: For complex feature development involving multiple files, use Spec-driven mode to ensure a clear plan. For quick validations of small ideas, use Prototype exploration to skip the Spec.
  • Environment isolation: For simple local tweaks, use the Local environment for quick feedback. For heavy development involving many files, we strongly recommend using the Worktree environment to fully isolate changes and keep your main branch safe.

​
Utilize iteration effectively

Don’t expect AI to deliver a perfect, complex system on the first try. Let the Agent complete an MVP version first, confirm the general direction, and then continuously add detailed requirements through multiple conversation turns. In Spec-driven mode, rely on conversation to let the Agent modify the Spec rather than editing it manually, ensuring the Agent maintains the best context understanding. The Agent supports unlimited iterations, allowing you to collaborate with it just like guiding a real engineer until you are completely satisfied.