Safe setup · project first · provider native

Give your agent the blueprint.

AIWG installation is an agent-guided flow with explicit inspection, approval, and verification gates. Paste one prompt into the coding agent that already has your project open.

Agent-guided install path Public instructions become verified project files.
01 Versioned instructions Setup YAML

Public, inspectable, and pinned to a release.

02 Your coding agent Inspect + plan

Checks the project, explains changes, and asks for approval.

03 Project-owned result Deploy + verify

Writes provider-native files, then proves AIWG is engaged.

INSPECT FIRST PRESERVE EXISTING WORK REPORT THE RESULT

Recommended path

Paste this into your agent—not your terminal.

The URL identifies a versioned setup flow. Your agent reads the YAML instructions, inspects your environment, explains the proposed changes, asks for approval, and then performs only the approved work.

AIWG complete-system setup prompt Claude Code · Codex · Copilot · Cursor · Factory · Warp · more
Install or repair AIWG for this project by following
https://aiwg.io/setup.aiwg.yaml
Explain the plan before changing anything, preserve my existing work, and ask
me only for choices you cannot safely determine.

Want to understand the instructions first? Review the complete setup manifest with line-by-line source and SHA-256 verification →

  1. 01InspectRead-only environment check
  2. 02ExplainSmallest safe plan
  3. 03ApproveYou authorize mutations
  4. 04DeployProvider-native project files
  5. 05VerifyOne structured readiness result

Optional runtime

Cockpit and Agentic Sandbox use their own setup flow.

Use this when agents need durable sessions, human approvals, containers or virtual machines, controlled networking, and an audit trail on infrastructure you operate.

Secure runtime setup prompt AIWG Cockpit + self-hosted Agentic Sandbox
Install or repair AIWG Cockpit and Agentic Sandbox by following
https://aiwg.io/agentic-sandbox/setup.aiwg.yaml
Install the required prerequisites, explain the plan before changing anything,
preserve my existing work, and ask me about the isolation, network, storage,
and access choices you cannot safely determine.

Inspect the secure-runtime instructions before using them. Review the Agentic Sandbox setup YAML with source and SHA-256 verification →

Agent bootstrap

A small orientation layer. Your provider stays in charge.

AIWG installs no daemon and modifies no operating-system components. It deploys a compact set of always-visible core skills and bootstrap instructions that orient your coding agent. The remaining capability library stays discoverable on demand.

One source AIWG corpus agents · skills · rules · flows
One-shot deploy aiwg use all selects the provider adapter
Project-owned Native files core skills + bootstrap context
Next session Your provider loads them no AIWG daemon required
Deployment copies plain Markdown and YAML into paths the selected provider already knows how to load.

Bootstrap layer

Always visible

Quick references, discovery guidance, status, doctor, refresh, regenerate, and other self-maintenance skills stay in the provider’s normal skill surface.

Standard tier

Loaded when needed

Hundreds of specialized capabilities remain under the AIWG installation. The agent finds them with aiwg discover and reads the match with aiwg show.

Project memory

Durable work products

The .aiwg/ tree holds project artifacts and decisions so later sessions can continue from reviewable files instead of private chat memory.

Session bootstrap

How a fresh agent finds the full system.

The generated bootstrap stays intentionally short. Each layer points to the next, giving the agent enough orientation to retrieve deeper instructions without flooding its initial context.

1Provider entryAGENTS.md · CLAUDE.md · WARP.md
2Workspace intentWORKSPACE.md
3AIWG routerAIWG.md + core quick references
4Discovery indexintent → stable capability ID
5Full capabilityaiwg show loads exact instructions
Short startup context routes into precise, on-demand capability loading.

Manual path

Three commands to a verified system.

Use Node.js 20 or newer. Project scope is the recommended default because it keeps one project’s agent setup from appearing in unrelated sessions.

  1. 01
    Install the complete local corpusnpm install -g aiwg
  2. 02
    Open the intended project rootcd /path/to/your/project
  3. 03
    Deploy, connect, and verify your provideraiwg use all --provider <provider>

Definition of done

Installed is not the same as engaged.

Setup finishes only when the executable, project root, provider adapter, context files, indices, and capability discovery all agree.

Quick inspection

Setup YAML

Loading and verifying the published YAML…

Open raw YAML Open full explainer →
Loading…