The outcome

Learn the interaction loop using a small task with a clear outcome.

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

    Install the official IDE or CLI and open a clean branch in a repository you have explicitly reviewed and trusted.

  2. 02

    Start in plan or default permission mode, add deny rules for secrets and release actions, and enable sandboxing for shell work.

  3. 03

    Give one agent task explicit acceptance criteria, relevant paths, non-goals, and validation commands.

  4. 04

    Inspect the artifact, command history, changed files, tests, and final diff before any commit or external action.

Working standard

What good use looks like.

  • State the outcome before the background.
  • Provide the real source material.
  • Review the result before expanding the task.

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.