Connect AIWG to Devin Desktop

Prompt-first procedure: Describe the outcome you want in your agent conversation. The agent should select and load the appropriate AIWG assets, explain material changes, request any needed approval, and report verification evidence. Exact commands and flags appear only in the CLI reference.

For the complete first-time journey, start with Install, Connect, and Verify.

Devin Desktop is the provider in this guide. Open a terminal in the project folder you use with Devin Desktop:

Use AIWG to complete this documented outcome: Devin Desktop is the provider in this guide. Open a terminal in the project folder you use with Devin Desktop
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

The deployment command refreshes AIWG's shared project context and prints a verification result. Reload Devin Desktop if the output says a reload is required, then ask it to verify the project root, `.windsurf/` context, installed frameworks, and one useful next action.

Try one small task immediately after verification:

Review this project's README and getting-started docs for unclear positioning,
missing setup steps, or unsupported claims. Return the three highest-priority
fixes with file references and a recommended next edit.

Success means Devin Desktop names the intended project, follows the AIWG bootstrap into `WORKSPACE.md`, `AIWG.md`, and the compatibility adapter, and produces a concrete review you can inspect.

If Node.js/npm are not working, follow Install Node.js and npm Safely. Agent/operator details live in the Devin Desktop operational reference.

AIWG intentionally retains the `.windsurf/` paths used by the compatibility adapter. The older `the provider option windsurf` selector still works with a deprecation notice. The separate `devin-cli` provider is not yet supported.