The outcome

Finish a scoped coding task without confusing repository trust, tool approval, and operating-system isolation.

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

    Create a clean branch or disposable checkout, inspect repository settings and hooks, and capture the starting status and baseline tests.

  2. 02

    Start in plan or default mode, add deny rules for secrets, Git metadata, pushes, deployments, and unrelated paths, then enable a restricted shell sandbox.

  3. 03

    Provide the outcome, acceptance criteria, relevant files, architecture constraints, non-goals, validation commands, and a clear stop condition.

  4. 04

    Review the plan and every consequential tool call, rejecting extra directories, network domains, unsandboxed retries, dependency drift, or parallel tasks without need.

  5. 05

    Run trusted tests independently, inspect artifacts and the complete diff, clean temporary credentials, and use the normal human-reviewed commit and release process.

Working standard

What good use looks like.

  • Use deny rules for hard boundaries.
  • Keep shell work sandboxed.
  • Treat directory trust and tool approval separately.

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.