The outcome

Get into the official CodeBuddy experience with the right account and a setup you understand.

CodeBuddy is a AI coding environment from Tencent Cloud with IDE, agent, and command-line workflows. Running complex coding tasks with visible artifacts and diffs while combining layered allow, ask, and deny rules with directory trust and OS-level shell sandboxing. This guide narrows that broad capability into one repeatable outcome, with checkpoints that keep the source material and your judgment in the loop.

Before you begin

Set the boundary before the tool starts.

Choose one real task, identify who will use the result, and decide what evidence or test will make the result acceptable. Gather only the source material needed for that task. If the work contains confidential, personal, regulated, or client-owned information, confirm that the platform and account are approved before sharing it.

Troiana principle

AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.

Step by step

A workflow you can repeat.

  1. 01

    Start at https://www.codebuddy.ai/ and confirm the domain before entering account or payment information.

  2. 02

    For desktop use, follow the official download link. Current availability: CodeBuddy provides a standalone AI IDE and CodeBuddy Code CLI with agent tasks, parallel work, model selection, subagents, permission modes, hooks, MCP tools, and optional shell sandboxing..

  3. 03

    A supported desktop or terminal environment, a CodeBuddy account or approved provider configuration, a trusted repository, and reviewed file, command, network, model, and data boundaries.

  4. 04

    Sign in with the account you intend to keep using, then review plan, data, notification, and permission settings.

  5. 05

    Run one low-risk test task before connecting sensitive files, repositories, or workspace data.

Working standard

What good use looks like.

  • Use official download pages.
  • Review permissions during setup.
  • Keep installers and applications updated.

Directory trust, tool permissions, permission mode, and shell sandbox are separate controls. Use explicit deny rules as hard boundaries, keep bypass permissions disabled, prevent unsandboxed retries where not needed, restrict additional directories and network domains, review project settings before trusting a clone, cap parallel agents, keep credentials short-lived, and independently verify all code, tests, commands, commits, pushes, and deployments.

Official references

Check the current product documentation.

Features, plan limits, availability, and data controls change. These official pages are the starting points used for this collection.