self-customize

To customize your agent, a guided decision workflow determines whether changes require workspace edits, admin package installs, MCP server wiring, or builder delegation, ensuring safe feature additions. It automates these end-to-end agent customization tasks while enforcing governance.

Wiring up an MCP server is handled through a guided workflow that separates workspace edits from container-level alterations and enforces admin approvals for system changes. This process includes safety checks to prevent unsafe operations during the server installation.

Admin approval is required for agent customization whenever system-level changes are necessary, such as installing system packages or altering container configurations. The workflow clearly separates these from standard workspace edits to enforce governance and safety checks.

Yes, a builder-agent workflow is available for safe and auditable code changes with explicit acceptance criteria. This delegates complex code modifications during agent customization, ensuring changes are reviewed and applied correctly within your workspace.

Editing CLAUDE-related files is constrained by safety checks that prevent unsafe operations and separate workspace edits from container-level alterations. If changes require system-level access, the workflow enforces admin approvals before proceeding with the modification.

Yes, installing system packages is supported through an admin approval process that separates these container-level alterations from standard workspace edits. The guided workflow ensures package installations are auditable and safe before applying changes to your agent.