CloudVerse AIX Dev Workbench

Your enterprise AI developer surface for chat, code, QA, review, docs, approvals, and runtime diagnostics through AIX Brain.

The extension is intentionally not a chat toy. Every normal turn runs through the local AIX agent loop and AIX Brain gateway, so the developer gets one IDE surface while the enterprise gets routing, policy, cost tracking, and audit.

Commands

• AIX: Start Workbench Task
• AIX: Ask in Dev Workbench
• AIX: Continue in Dev Workbench
• AIX: Run Dev Workbench
• AIX: Resume Workbench Run
• AIX: Open in Dev Workbench

Install

Marketplace:

• cloudverse-aix.aix-dev-workbench

Current published version:

• 1.0.3

Auth

Uses AIX device login:

1. Open the AIX Dev Workbench sidebar or run AIX: Start Workbench Task
2. Click login when prompted
3. Approve in browser

The extension uses the neutral AIX device-auth flow rather than the CLI-branded auth page.

The extension stores tokens in VS Code secret storage.

Users can sign up directly in AIX before using the extension:

• email and password
• Google
• Microsoft
• GitHub

Workbench behavior

The extension follows the AIX Dev Workbench model:

• route every turn through AIX Brain
• infer the right execution class without manual mode selection
• show the current AIX response and next useful move
• show only true artifacts as artifact cards
• keep approvals, tool status, and errors inline in the conversation

Enter sends. Shift+Enter inserts a new line. Up recalls the previous user message when the prompt is empty. Esc clears the prompt or stops the visible turn.

New tasks default to Brain-routed execution, with read/search tools auto-approved and writes/commands requiring approval.

Source access

The extension starts the bundled local AIX agent automatically when the sidebar loads for an authenticated workspace. The agent stays inside the workspace boundary.

• Read/search/status tools can run automatically.
• File writes, patches, shell commands, and git mutations require approval.
• Credential access and destructive actions are blocked by policy.

When source context is not available, use Connect workspace to attach the current local folder or Import source archive to provide a bounded source snapshot.

Recommended onboarding flow

1. Open a repo in VS Code.
2. Ask anything: Review this repo, Write tests, Explain this file, or Prepare a PR.
3. Attach FDDs/docs/files when needed.
4. Approve writes or commands inline when AIX asks.
5. Continue the same session after reload from the persisted local loop state.

Public onboarding docs

• Getting Started
• User Guide
• VS Code Onboarding Runbook