Operating ProcedureExecution layer

wcagent Client Workspace Setup (Onboarding)

A sequence with 7 steps: Install the wcagent extension in desktop VS Code on the delivery machine.

By InnovaAI ResearchPublished Updated

What are the steps?

sequence

wcagent Client Workspace Setup (Onboarding)

  1. 01

    Install the wcagent extension in desktop VS Code on the delivery machine.

    Confirm the seat is billed at $4.99 USD per month (or $4.17 USD per month on annual billing) before adding it to a client retainer line item. The extension does not bundle model access, so the client or agency must hold a separate ChatGPT, Claude, Gemini, Grok, or DeepSeek account.

  2. 02

    Connect at least one eligible third-party AI service account through the authorized provider connection flow.

    Record which provider was linked and whose account pays for it. If the client supplies the key, note the renewal date so the retainer does not silently depend on a subscription the client can cancel.

  3. 03

    Set local developer approval gates before opening any client repository.

    Configure the approval settings so commands, file edits, and tool execution all require a human click. This is the control that keeps an agency from shipping unreviewed AI edits into a client codebase.

  4. 04

    Open the client repository and let the context engine rank task-relevant files, symbols, and diagnostics.

    Verify the ranking pulls the right modules before the first real task. A context engine pointed at the wrong package will produce confident diffs in the wrong place.

  5. 05

    Author an AGENTS.md file at the repository root with project-level instructions.

    Spell out build commands, test commands, coding conventions, and files the agent must never touch. This file is what makes the same wcagent seat behave differently across two client repos.

  6. 06

    Run one throwaway task end to end and inspect the evidence history.

    Confirm the completion gate actually captured test results, a successful build, and a recorded diff. If any of the three is missing, the gate is not doing its job and the client audit trail will have holes.

  7. 07

    Hand the client a written scope note covering seat cost, provider cost, and what evidence they will receive.

    State plainly that wcagent gates completion on tests, builds, and diffs rather than model confidence. Clients who expect a bundled AI subscription will push back at invoice time if this is not set at onboarding.