DevWorkspace Pro

One workspace for your Rust crates

Create Cargo binaries and libraries, run cargo run, test and build from one card, and manage Rust crates with GitHub Actions and AI agents in one app.

Updated 3 min read
On this page
  1. Core features every project gets
  2. Extras for Rust
  3. Your first day
  4. What Rust developers get out of it
  5. Your toolchain stays yours

Rust builds are long, and you rarely work on one crate at a time. DevWorkspace Pro gives each crate its own place: a Run card with cargo run, cargo test and cargo build, terminal tabs that survive a restart, and an AI agent you can point at the code while the compiler works.

The app finds a crate from Cargo.toml and can create new binaries and libraries with cargo init. On top of that, every Rust project gets the same core features as any other folder.

Core features every project gets

  • Files editor, ⌘+P and project search
  • Git Changes, GitHub issues and Actions
  • Send to AI and AI sessions with resume
  • Terminal tabs, Focus Pad and the ⌘+K switcher
  • Uptime monitoring and Remote SSH
Projects Import
ledger-core ~/code/ledger-core Rust
acme-shop ~/code/acme-shop Laravel
acme-web ~/code/acme-shop/web Node.js
billing-api ~/code/billing-api Go
data-jobs ~/code/data-jobs Python
Shop.Api ~/code/shop-api .NET
[Projects] The app finds Rust from Cargo.toml and shows the Rust badge.

Extras for Rust

  • Rust badge from Cargo.toml
  • A Rust create flow with Binary and Library templates
  • A Run card with Cargo commands and Makefile targets
  • Cargo runs natively, and a folder with compose.yaml also gets Docker Compose services

Your first day

Create or import a crate

Click New Project, select Rust and pick Binary or Library in Template. In step 2, select Cargo. The app checks that cargo is installed and shows its version, then runs cargo init --name <name> (with --lib for a library) and saves cargo run as the run command.

Already have a crate? Drag the folder onto the window. The app also finds a Cargo.toml in a direct subfolder, such as server/Cargo.toml.

Run, test and build

On the Overview tab, the Run card shows Run (cargo run) when src/main.rs or a [[bin]] section exists, along with Test and Build. A Makefile adds a tab with its targets.

Each command runs in a headless terminal. Minimize the window during a long cargo build and it keeps going, with its status in the status bar. If the command fails, the window comes back to the front.

Hand a task to an AI agent

Press ⌘+J and type the task, for example "Replace the unwrap calls in the parser with proper error types". Claude Code, Codex or OpenCode starts in the crate folder.

Working across a workspace of crates? Start one agent per crate from the ⌘+K switcher: select the project and press Tab. Each session can resume after a restart.

Ship through GitHub

Review each diff in Git › Changes, commit, and push from the terminal. In Git › Actions, filter runs by branch, open a job and read its log. When cargo clippy or cargo test fails in CI, Send failure to AI passes the failed step and its log to your agent.

What Rust developers get out of it

Cargo on the Run card. The card reads Cargo.toml and the src folder, and reads them again only when a file changes. On a large workspace, the card still opens fast.

Makefile targets as buttons. Keep fmt, clippy and audit in a Makefile. Each target becomes a button, with its ## comment as the description.

Terminal tabs with history. Open one terminal for cargo watch, one for a shell and one for benchmarks. After a restart, each shows its saved output and starts a new shell in the last folder you used.

Focus Pad. Keep your task list on top of the editor with ⌃+⌥+⌘+T, with one collection per crate.

Remote SSH and uptime. Open a shell on your Linux server from the Remote SSH tab, and add your service's public URL in Health › Uptime.

Your toolchain stays yours

The app runs the cargo on your PATH, whether rustup installed it or something else did. It does not touch Cargo.toml, and your Git hooks still run on commit.

Keep RustRover, VS Code with rust-analyzer, or Zed. Click IDE to open the crate with your editor command.

Other compiled stacks: /for/go and /for/dotnet. Docs: Projects, Terminal, AI Sessions, Focus Pad.

FAQ

Frequently asked questions

Which commands does the Run card show for Rust?

cargo run when src/main.rs or a [[bin]] section exists, cargo test and cargo build. It also shows your Makefile targets.

Can I create a library crate?

Yes. Select Rust in New Project and pick Binary or Library. The app runs cargo init, with --lib for a library.

Does the app check Cargo.lock for advisories?

No. The dependency scan covers Composer, npm, pnpm, Yarn, Bun and NuGet. Run cargo audit from the terminal tab, or add it as a Makefile target so it shows on the Run card.

Related

All stacks

DevWorkspace Pro

One workspace for every project

Files, Git, GitHub, AI agents, the terminal and your runtimes in one desktop app. Works with every project folder.

macOS Windows Linux