Standard Mode

Standard Mode is the manual flow of Qodo Gen Chat, allowing you to set certain behaviors and preferences yourself and call Commands.

Qodo Gen supports two modes: Standard mode and Agentic mode.

Standard mode offers a manual Qodo Gen experience, letting you choose exactly what the AI models focus on and what context they have.

Agentic Mode enables Qodo Gen to have context on your entire project and to use services and Agentic Tools behind the scenes. This enables Qodo Gen to understand your code better and help you perform various actions.

What is Standard Mode?

Standard Mode follows a traditional command-response structure, where Qodo Gen executes user instructions exactly as given.

This mode offers a more predictable and controlled experience, making it ideal for users who prefer direct command execution without additional processing or tool integration, or for users who want to manually control what Qodo Gen uses as Context.

While it does not dynamically select tools like Agentic Mode, it still provides accurate and efficient responses based on the given input.

Standard Mode Usage

1. On the bottom right of Qodo Gen, find the buttons that say Standard and Agentic.

2. Choose Standard. The look of Qodo Gen will change to indicate you're now using Qodo Gen in Agentic Mode.

Example Usage

Code Search & Refactoring

• "Find all functions related to user authentication in our codebase."

• "Where is the logic for calculating subscription billing?"

Best Practices & Documentation

• "List all places where legacy_api_call() is used and suggest replacements."

• "Find any duplicate or similar functions that could be merged."

• "Check if there are any TODO comments left in the codebase."

Code Writing & Autocompletion

• "Write a helper function to validate email addresses using our existing utilities."

• "Generate a unit test for processOrder() based on our testing framework."

• "Refactor this function to improve readability without changing its behavior."

Debugging & Issue Detection

• "Analyze this file for potential bugs or edge cases."

• "Find all functions that don’t have error handling in this module."

• "Are there any security risks in this code?"