Build System

What is a build?

A build is a snapshot of your Claw's complete configuration at a point in time. It packages together the agent's skills, connections, operating instructions, identity, and personality into a single deployable artifact. Builds are immutable -- once created, they cannot be changed.

How are builds created?

Builds are created automatically when you trigger a deployment. WorkClaw resolves your current configuration, validates all skill dependencies, verifies connection credentials, and assembles the artifact. You can also create a build manually from Admin > Builds > New Build without deploying it immediately.

Each build receives a unique version identifier and is stored for rollback purposes.

What does a build contain?

A build artifact includes:

• Agent identity -- name, avatar, and personality settings.
• Skill manifest -- the full list of installed skills with their versions and configurations.
• Connection bindings -- references to active connections and their scopes.
• Operating instructions -- the instructions that guide agent behavior.
• Vault references -- pointers to Vault secrets the agent needs at runtime. Secrets themselves are fetched securely at deploy time, never baked into the artifact.

How do I troubleshoot a failed build?

When a build fails, the build detail page shows the error along with the phase where it occurred. Common causes include:

• Missing skill dependency -- a skill requires another skill or connection that is not configured. Check Skill Requirements.
• Invalid connection -- a connection token has expired or been revoked. Re-authenticate under Managing Connections.
• Instruction validation error -- operating instructions exceed length limits or contain unsupported directives.

Review the build log for the specific error message and follow the suggested remediation steps.

How long are builds retained?

WorkClaw retains the last 50 builds per workspace by default. Older builds are archived but can be restored for rollback if needed. Active builds -- those currently deployed to any runtime -- are never archived.