sitdraw

How to install and use Qodo Gen (formerly Codium) in VS Code: tests, docstrings, chat

Install Qodo, sign in, run your first /test or /docstring on a function, then ask the codebase a read-only question in Chat.

To use Qodo Gen (formerly Codium) in VS Code for tests, docstrings, and codebase chat, finish four jobs: install the Marketplace Qodo extension, restart extensions, sign in, then run /test or /docstring in Qodo Chat.

Facts follow docs.qodo.ai VS Code setup and Chat docs plus Marketplace Qodo (formerly Codium) (Codium.codium). Queries: Qodo Gen VS Code install, Codium generate tests VS Code. For a short huddle see sitdraw and create and join a room.

Install extensionSign inTests · docs · Chat

Name change from Codium

Brand

CodiumAI rebranded to Qodo; the extension id remains Codium.codium. Docs refer to the IDE plugin as formerly Qodo Gen / formerly Codium.

What you get

Local change review, test generation, docstrings, contextual Chat, and slash workflows such as review-uncommitted, fix, docs, and unit-test.

/testUnit tests
/docstringDocumentation
ChatAsk the repo
GoalEntryFirst-hour check
Unit testsChat /test or unit-test workflowSelect a function → review diff → apply
Docstrings/docstring or docs workflowPick an undocumented symbol → match project style
Codebase Q&AActivity Bar Qodo ChatAsk what a change does—start read-only
Pre-commit reviewreview-uncommitted workflowRun with local diffs open

Install, sign in, first test and docstring

  1. 01
    Install the VS Code extension

    Extensions → search Qodo (publisher Qodo, formerly Codium) → Install → Restart Extensions. Quick Open: ext install Codium.codium.

  2. 02
    Sign in

    Open the Activity Bar Qodo panel → Sign in with Google, GitHub, email, or enterprise SSO per docs.qodo.ai. Confirm the panel shows an active session.

  3. 03
    Generate your first test

    In your repo, select a function. In Qodo Chat, run /test or the unit-test workflow. Read the proposed test diff before applying.

  4. 04
    Docstring plus chat

    Run /docstring or the docs workflow on a bare function, then ask Chat how the module is called—no secrets in prompts.

# First hour · Qodo Gen · VS Code · 2026-09
# Extensions → Qodo → Restart Extensions → Sign in
# /test or unit-test · /docstring or docs · Chat Q&A
# docs.qodo.ai/qodo-ide/getting-started/setup-and-installation/vscode-installation
# marketplace.visualstudio.com/items?itemName=Codium.codium
Which extension if I search Codium?
Install Qodo publisher, id Codium.codium—the CodiumAI brand moved into Qodo; avoid unrelated copycat extensions.
/test does nothing?
Confirm sign-in and a folder workspace (not a single loose file) with a valid selection. Reload Window; check Remote SSH network.
Compare Codeium or Tabnine?
Qodo emphasizes review plus tests/docs; Windsurf/Codeium and Tabnine emphasize inline completion. See our Codeium guide and Tabnine guide.
Does this replace a whiteboard?
No. For module diagrams open sitdraw or temporary meeting tools.

Sign in before /test

Most empty runs are an installed extension without an active Qodo account or a file-only workspace.

Start the picture