Skip to content
| Marketplace
Sign in
Visual Studio Code>Linters>DayNew to Visual Studio Code? Get it now.
Day

Day

daybrite

|
16 installs
| (1) | Free
Build, launch, script, and package Day apps from VS Code: native apps for every platform from one Rust codebase, with the day CLI's whole pipeline behind the editor.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Day
Day for VS Code

Latest release Build status VS Code Marketplace version VS Code Marketplace installs

Install from the VS Code Marketplace
or code --install-extension daybrite.day-vscode

Install  —  Get started  —  Troubleshooting  —  Screenshots  —  Day docs


Day is a complete application framework in Rust. One codebase ships as a real native app on macOS, Windows, Linux, iOS, Android, HarmonyOS, and the web, each one drawn with that platform's own widgets, and the CLI, CI workflows, localization, accessibility, and dayscript automation come with it. This extension is the framework's editor half: pick the platforms, press Run, and watch them build and launch side by side; run dayscript walkthroughs; and open the host project in Xcode or Android Studio after the extension prepares it.


Run it on every platform at once

The Day view listing a project, its targets and its devices, beside a Rust file

The Day view lists every project in the window and the platforms each one ships to. Tick the ones you want and press Run.

  • Each target builds in its own terminal, and stops and restarts on its own.
  • Targets your machine cannot build are shown greyed, rather than hidden.
  • The + on a project's Targets row adds another platform to the app.
  • Mobile targets expand to a Device row — a booted simulator, a plugged-in phone, an emulator, or every one at once. Right-click one to start or stop the simulator or emulator itself.
  • Open a dozen apps together: each keeps its own targets, build mode, locale and log level.

Start a project without leaving the editor

Choosing platform-toolkits in the New Project wizard

Day: New Project scaffolds an app, a piece or a part, one question at a time, with Back at every step.

  • The questions come from the CLI itself, so the platforms offered are exactly the ones your day supports.
  • Your own machine's platform arrives preselected.
  • New to Day? The Get started with Day walkthrough on VS Code's Welcome page takes it from the top.

Catch problems where they happen

day doctor reporting the toolchains installed on this machine
  • Day: Doctor checks the toolchain for every platform and prints the command that installs whatever is missing.
  • Day: Lint Project draws findings on the lines they name — a missing translation, a route nothing declares, an undeclared permission — with quick fixes where the repair is unambiguous.
  • Day: Clean Project removes every build artifact — build/, target/, and the platform scaffolds' generated outputs — via day clean, confirming first and reporting the space it reclaimed.
  • F5 builds a desktop target and hands the binary to a Rust debugger you already have, so breakpoints in .rs files are real ones.

Built for agent mode

In a Day workspace the extension registers the Day MCP server with VS Code's agent mode, so an agent can inspect the project, build and launch it, then drive the running app and take screenshots — on every platform it targets. Ask for something like:

Add a configuration page, relaunch on all targets, and show me screenshots.

Requirements

VS Code 1.101 or newer, and the day CLI:

cargo install day-cli

Each platform needs its own SDK — Xcode, a JDK and the Android SDK, GTK 4 or Qt 6. Run Day: Doctor and it will name what is missing for the platforms you picked, with the command to install it.

Learn more

  • Installing and updating — including how to point the extension at a particular day binary or a local checkout.
  • Getting started — a first app, from scaffold to a running window.
  • Reference — every command and setting, including the per-project ones and the toolchain paths.
  • Troubleshooting — when a build or a launch does not go as planned.
  • Day documentation — the framework itself: pieces, layout, navigation, localization and packaging.

Contributing

Bugs and ideas are welcome in issues. CONTRIBUTING.md covers building the extension from source and running its tests.

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