Qodo Documentation
HomepageBlogCommunityGet Started
  • Overview
  • Qodo Gen
  • Qodo Portal
  • On Prem
  • Introduction
  • Quickstart
  • Setup and Installation
    • VSCode Installation
    • JetBrains Installation
    • Sign In
    • Extension Settings
    • Uninstall
  • Qodo Gen Chat
    • Agentic Mode
      • Agentic Tools (MCPs)
      • Built-in Tools (MCPs)
    • Standard Mode
      • Focus
        • Current File Focus
        • Git Diff Focus
      • Context
        • Add Entire Folder or Project as Context
        • Add Image as Context
      • Commands
        • /ask
        • /changelog
        • /commit
        • /describe
        • /docstring
        • /enhance
        • /explain
        • /find-on-github
        • /generate-best-practices
        • /help
        • /improve
        • /issues
        • /recap
        • /review
    • Inline Context
    • Chat History
    • Model Selection
    • Chat Preferences
  • Qodo Gen CLI
    • Setup and Quickstart
    • Creating and Managing Agents
    • CI and Automation
    • List of CLI Commands and Flags
    • Use Cases and Examples
  • Company Codebase (RAG)
    • Tagging
    • Configuration File
  • Code Completion
  • Test Generation
    • Configuring Your Test Setup
  • Data Sharing
  • Release Notes
Powered by GitBook
LogoLogo

Terms and Privacy

  • Terms of Use
  • Privacy Policy
  • Data Processing

© 2025 Qodo. All Rights Reserved.

On this page
  • Autonomous CI Mode
  • Webhook Mode
  • Run Agent in MCP Mode
  • GitHub Action

Was this helpful?

  1. Qodo Gen CLI

CI and Automation

Autonomous CI Mode

Run Qodo Gen CLI in CI environments with the --ci flag:

qodo <command> --ci

The output logs from Qodo Gen CLI will be simplified and fit for CI environments and build pipelines.

This mode runs Qodo Gen CLI in an autonomous mode that doesn't require the user to provide any answers to the agent.

Webhook Mode

Run Qodo as an HTTP server to receive POST requests for each command.

qodo --webhook

This flag will make Qodo Gen CLI:

  • Expose each of your configured agents as a separate POST endpoint.

  • Open a server.

  • Listen to POST requests that come in through the URLs.

The POST requests are validated according to the arguments available in the configured agent, and return the same return value that's set in the agent.

POST Example:

POST http://localhost:4000/webhook/explain

Returns results at end of execution.

SSE Mode (Live Streaming Logs)

If you add the parameter sse=true to the URL, a session ID will be returned. That enables you to run a GET request with the session ID.

Running a configured agent like so, you can see all the actions the agent is running behind the scenes, not just the return value.

POST http://localhost:4000/webhook/explain?sse=true

-> returns sessionId

GET http://localhost:4000/webhook/sse/explain?sessionId=<ID>

Run Agent in MCP Mode

When you run Qodo Gen CLI in MCP mode using the --mcp flag, it transforms into a server that exposes all configured agents (only those with a description) as callable tools.

qodo --mcp

Each of the configured agents becomes accessible through a streamable HTTP URL, allowing external systems to trigger them easily.

As the server processes a request, it can send real-time progress notifications and eventually returns the final result of the execution.

This allows you to seamlessly integrate your agents with other tools or platforms without the need to share API keys, as all execution and access are handled securely through the Qodo Gen CLI server itself.

GitHub Action

You can utilize Qodo Gen CLI's GitHub Action for your CI needs.

PreviousCreating and Managing AgentsNextList of CLI Commands and Flags

Last updated 1 day ago

Was this helpful?