Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Workshop2D CompanionNew to Visual Studio Code? Get it now.
Workshop2D Companion

Workshop2D Companion

Workshop2D

|
6 installs
| (0) | Free
Windows companion for Unity metadata, AI usage, and universal AI completion overlays.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Workshop2D Companion

Features

  • Unity .meta file guardian
  • Claude and Codex usage display
  • Universal AI completion notifications

Feature details

  • Unity .meta file guardian — Safely moves, renames, deletes, validates, and reconciles C# files with their metadata through serialized AI tools.

  • Claude and Codex usage display — Shows the smallest remaining allowance across every limit each provider reports — 5-hour, weekly, Claude's spend limit, and Codex's additional named limits — from Claude's status-line data and Codex's app-server. A reading with no recent update is marked ?; an exhausted allowance turns the item red.

    Claude works with no setup: the extension reads the utilization Claude Code caches for itself. For live updates, run Workshop2D Companion: Install Claude Usage Bridge — but note that Claude only runs a status line in a terminal session, not in the VS Code extension, so the bridge refreshes only while you use claude in a terminal. Whichever source is newer wins, and a reading Claude has not refreshed recently is marked ?.

  • Universal AI completion notifications — Lets any Windows AI run workshop2d-notify "Task finished" -Source "Codex" for a centered fading completion overlay with sound.

Development

npm run check type-checks, npm test runs unit tests, and npm run test:integration launches VS Code against fixtures/unity-project — CI runs all three, so run the integration test before pushing. npm run package produces a local VSIX.

Releasing

Publishing goes through .github/workflows/publish-marketplace.yml:

  • Pushing a v*.*.* tag publishes a pre-release.
  • Running the workflow manually with channel stable publishes a stable release. A tag alone never does.

Bump package.json, commit, then tag and push: git tag -a vX.Y.Z -m "Workshop2D Companion X.Y.Z" && git push origin vX.Y.Z. The tag must be annotated — git push --follow-tags silently skips a lightweight one, so nothing publishes. The workflow fails if the tag and the package version disagree. It supplies the publisher from the VSCE_PUBLISHER variable and the token from VSCE_PAT in the vscode-marketplace environment, so leave publisher in package.json alone.

See AGENTS.md for the full contributor and agent guide.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft