Day for VS Code

Build and run Day apps — cross-platform native UI in Rust — across one or more targets, straight from VS Code. It's a thin, conventional wrapper over the day CLI: each launch runs as a VS Code Task in its own integrated terminal, so output is native (ANSI colors intact) and filtered per target, and processes stop/restart through the standard task lifecycle.

Features

• Day sidebar — pick a project, tick one or more targets, and Run / Build. Targets your host can't build (e.g. windows-* on macOS) are shown disabled.
• Multiple simultaneous targets — each selected target launches in its own terminal and can be stopped / restarted independently (inline buttons, or the status bar).
• Build mode (debug / release), locale (--locale), and an optional dayscript (--script) — all editable from the sidebar or command palette.
• day task type — auto-detected day: build <target> / day: run <target> tasks integrate with the Tasks system, Ctrl+Shift+B, and key bindings. Build errors surface via the $rustc matcher.
• Doctor — run day doctor to check your toolchains.

Requirements

The day CLI:

cargo install day-cli

Set day.cliPath to your day binary. If it's left as day and isn't on PATH, the extension falls back to cargo run against a local day-cli — so it works with no installed binary in two layouts: when the workspace is inside the Day repository, and when a day/ checkout sits beside this extension's own day-vscode/ source (the dev-host case, resolved via --manifest-path, so a sibling project like Day-Games/ loads too).

Settings

Developing this extension

npm install
npm run compile   # or: npm run watch

Press F5 (Run → "Run Day Extension") to open an Extension Development Host. Open any Day project (a folder with a Day.toml — day new app my-app makes one); the Day sidebar lists the app and its targets — tick macos-appkit, click Run, and the app launches in a terminal. Tick a second target to run both at once; use the inline stop/restart buttons per target. npx @vscode/vsce package produces an installable .vsix.

Releases: pushing a v* tag builds, packages, and publishes to the Visual Studio Marketplace and Open VSX (see .github/workflows/ci.yml). The extension's release cycle is independent of day's — it drives whatever day CLI is installed.

License

MPL-2.0, like Day itself.

AI agents

In a Day workspace the extension registers the Day MCP server (day mcp-server) with VS Code's agent mode automatically (day.mcp.enabled, default on). Agents get tools to inspect the project (day_metadata, day_doctor, day_lint), build and run it (day_build, day_launch, day_relaunch, day_stop, day_running), and — through the dayscript engine inside every launch — drive the running app and see screenshots (day_drive, day_screenshot) on every platform the app targets. Try, in agent mode:

Add a new "configuration" page to the app and re-launch it on all targets, then show me screenshots.

Scaffolded projects include an AGENTS.md teaching agents the project's conventions (pages, localization keys, stable ids, and the relaunch→drive→screenshot verification loop).

Install (from GitHub)

Not on the Marketplace yet — grab the .vsix from the releases page and run code --install-extension day-vscode-<version>.vsix, or build it yourself: npm install && npx vsce package.

Publishing

CI validates Marketplace publishability on every push (strict vsce package + the documented requirements checklist). Tagging v* attaches the .vsix to a GitHub Release; actual Marketplace / Open VSX publication is fully wired but off until the repository variables flip. Marketplace auth is tokenless — Entra ID workload-identity federation via GitHub OIDC and vsce publish --azure-credential (Azure DevOps PATs retire Dec 1 2026); Open VSX keeps its own OVSX_PAT secret. The header of .github/workflows/ci.yml documents the one-time Azure/Marketplace setup, the MARKETPLACE_PUBLISH / AZURE_* variables, and a no-upload dry-run you can trigger from the Actions tab.