Sign Up
Coding agency icon

Agency Domain

Coding Agency

Control how your agent writes, edits, and refactors code.

The Coding agency governs how your agent writes new code, edits existing files, and performs refactoring. For agents that work in development environments, this is one of the most active domains, and finding the right oversight level helps you balance speed with control.

What Coding Covers

Coding actions include writing new functions and modules, editing existing code, refactoring for clarity or performance, fixing bugs, adding tests, and adjusting configurations. When your agent writes a new API endpoint or restructures a utility function, that is a coding action.

Oversight Levels

Silent

Your agent writes and edits code freely. It implements features, fixes bugs, and refactors as needed without asking. This works well for experienced developers who review code through pull requests or other review mechanisms rather than approving each change individually.

For example, your agent might notice a duplicated utility function across two files and automatically refactor it into a shared module.

Report

Your agent writes code and notifies you about what changed and why. You get summaries like "I've added input validation to the signup form and wrote three test cases. Here's a summary of the changes." You can review the work and provide feedback without blocking your agent's flow.

Report is a comfortable default for many users. It keeps you aware of what is being changed while letting your agent handle implementation details.

Approval

Your agent proposes code changes and waits for your review before writing anything. You see messages like "I'd like to refactor the authentication module to use a strategy pattern. Here's the proposed approach. Should I proceed?" Your agent writes code only after you approve.

This is useful when working in sensitive codebases, during early collaboration when you want to closely guide your agent's coding style, or when changes could affect production stability.

When to Use Each Level

Code changes are generally reversible through version control, which makes this domain more forgiving than others. However, the volume of coding actions can be high, and Approval mode for every change can create significant bottlenecks.

A common pattern is to use Report as the default and switch to Approval for specific high-stakes changes like database migrations or security-related code. If your agent works in a repository with good test coverage and CI/CD checks, Silent mode becomes practical because automated safeguards catch problems before they reach production.