What Is CodeBuddy: Getting Started with Tencent AI Coding Assistant

CodeBuddy in One Sentence

CodeBuddy is Tencent's AI coding assistant. It helps you complete, explain, modify and generate code while you write it. It isn't a single product but a set of tools across plugin, IDE and CLI forms, so you can pick whichever fits how you already work.

Three Forms: Plugin, IDE, CLI

• Plugin: installs into VS Code or the JetBrains family, so you keep your current editor and plugin ecosystem. Lowest switching cost.
• IDE: CodeBuddy IDE is a standalone editor that puts AI at the center. Best if you want something that works out of the box.
• CLI: CodeBuddy Code runs in the terminal, suited to people who live on the command line and need scripts or batch jobs.

The three aren't mutually exclusive — you can combine them as needed. Starting with the plugin, then deciding whether to switch IDEs or add the CLI, is the safer order.

Three Modes: Ask, Craft, Plan

This is the design most worth understanding before you start: one input box, different modes depending on the size of the task.

• Ask: conversational Q&A. Explains code, analyzes errors, compares approaches — without touching your files.
• Craft: agent mode. Generates code or makes local edits from the current context. Fast, and suited to single-file or narrow tasks.
• Plan: planning mode. Built for cross-file and complex features — it gives you a task list to approve first, then executes on its own.

Core Capabilities: More Than Autocomplete

• NES in Completion Pro: Next Edit Suggestions predicts where your next edit should land based on the change you just made. On by default; trigger it manually with Ctrl+Shift+Enter.
• Figma to code: import a design file and generate page code directly.
• Smart diagnostics: finds potential bugs and performance bottlenecks, with one-click fixes.
• Smart document generation: produces documents such as a PRD from a requirements description.
• Backend and deployment integrations: connects to CloudBase, Supabase and CloudStudio.

How It Differs from a Plain Autocomplete Plugin

A typical autocomplete plugin answers "what goes on the next line". CodeBuddy is more concerned with "how does this task get done". Three differences: it reads context across files and executes multi-step changes against a plan; it treats design files, screenshots and documents as valid input; and it pulls team conventions in through Rules, Skills and MCP. Autocomplete is one part of it, not the whole story.

Who It's For

• People who don't want to switch editors and only want to strengthen their current setup — take the plugin.
• Frontend developers who work from design files and need pages fast — Figma-to-code saves the most time.
• Teams that need bulk refactors, scripts or automation — the CLI fits better.
• Beginners who want line-by-line explanations — Ask mode has the lowest barrier.

Where to Go Next

The recommended order is: get it installed, get comfortable with the three modes, then think about customization. Start with the installation guide to get the plugin running, then use a few real, small tasks to learn how Ask / Craft / Plan divide the work. To compare other tools, browse the tool library; for more hands-on walkthroughs, head to the tutorials. Information here is current as of 2026-11; check the official docs for the exact feature set and availability.