How to use
CodeBuddy.

1. 01

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

2. 02

   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.

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

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.

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

1. 01

   Restate the intended behaviour and the acceptance criteria before reading a single generated line.

2. 02

   Read the diff rather than the chat summary; the summary describes intent, the diff describes what actually changed.

3. 03

   Run the test suite, then write a test that would fail if the change were wrong, and confirm it passes for the right reason.

4. 04

   Check the edges the model tends to skip: error paths, null and empty cases, concurrency, and migration or rollback behaviour.

5. 05

   Trace every new dependency, network call, and file write, and confirm each one is genuinely required.

• Review the diff, never the description of the diff.
• A passing test suite proves the tests pass, not that the change is correct.
• Keep changes small enough that a human can actually review them.

1. 01

   Decide what the tool may read and what it may write before connecting a repository.

2. 02

   Scope tokens and integrations to the narrowest repository, branch, and permission set that still works.

3. 03

   Keep secrets out of the context window: use environment variables and secret stores, never inline credentials.

4. 04

   Require review before generated code touches authentication, payments, permissions, migrations, or deletion paths.

5. 05

   Audit what the integration retained after the session, and revoke access that is no longer needed.

• 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.
• Follow your organisation's approved-use policy.
• Never treat fluent output as authorization to act.

• CodeBuddy Agent Mode ↗
• CodeBuddy permission rules ↗
• CodeBuddy shell sandbox ↗
• CodeBuddy security guidance ↗

Working on something like this? See how we handle product engineering, or book a call.