# OneAgent for VS Code support

The `0.5.x` pre-release supports invited Ampacs pilot users on Windows 11 and
VS Code Stable. Other operating systems, Remote SSH, WSL, Dev Containers, and
virtual workspaces are not supported by this preview.

## Before requesting support

1. Run `OneAgent: Show Runtime Logs` and review the output for secrets or local
   information before sharing it.
2. Record the extension version, VS Code version, Windows version, tenant name,
   approximate failure time, and request ID if one is shown.
3. Do not send passwords, OAuth tokens, provider keys, complete prompts, source
   files, or unrestricted command output.
4. Retry once after `Developer: Reload Window`. Do not delete Agent Home as a
   generic recovery step.

## Host digest verification recovery (0.5.33 and later)

A Host digest error means the selected Host file is not authorized by the
packaged release policy. It is separate from the installer download checksum.

1. Update to the latest OneAgent Preview and reload the VS Code window. A missing
   or rejected custom Host path can recover automatically to the verified managed
   Host. The saved custom path is retained; trusted custom Hosts remain selected.
2. If recovery still fails, use **Install OneAgent Runtime** and complete Windows
   UAC. Reinstalling the VS Code extension alone does not reinstall machine Host
   files or reset `oneagent.hostPath`.
3. If an approved old custom pair cannot satisfy the tenant's minimum Runtime,
   reset **OneAgent: Host Path** to its empty default, then install/repair Runtime.
4. If the managed file still fails verification, share the selected path, actual
   SHA-256, approved SHA-256 and extension version from Runtime Logs with support.
   Keep tokens and personal project details private. Do not disable hash checks
   or delete profiles, Skills, memory or threads to bypass the error.

The Host version is 0.6.1 and managed Codex is 0.162.1 in this release; 0.5.23 is
an extension-compatibility release label and does not identify the installed Host.

## Contact and severity

Use the Marketplace Q&A entry for ordinary product questions. For pilot
incidents, contact `charles@one-agent.ai`.

- P0: suspected tenant escape, credential exposure, destructive data loss, or
  a broadly unusable signed release. Target initial response: 4 hours.
- P1: widespread activation, sign-in, turn-start, Review, Undo, or upgrade
  failure without data exposure. Target initial response: one business day.
- P2: bounded defect with a workaround. Target initial response: three business
  days.

OneAgent may stop a rollout, unpublish an affected release, or publish a higher
fixed version. Marketplace Remove is not used as a normal rollback mechanism.