> ## Documentation Index > Fetch the complete documentation index at: https://aspect.build/llms.txt > Use this file to discover all available pages before exploring further. # Shipped > New features and launches on Aspect Workflows, Aspect Cloud, and the Aspect CLI. What's new in Aspect Workflows, Aspect Cloud, and the Aspect CLI. ## [Selective delivery on Aspect Cloud](https://aspect.build/shipped/selective-delivery-aspect-cloud) ![Selective delivery pushes only the targets whose outputs changed](https://mintcdn.com/aspectbuild/x1L7Iep716jCyJVo/images/marketing/illustrations/aspect-delivery.svg?fit=max\&auto=format\&n=x1L7Iep716jCyJVo\&q=85\&s=cf41f5d900ae4230bf53b295c1693765) `aspect delivery` now keeps its state in Aspect Cloud, so a release job on any CI pushes only the targets whose output digests changed since their last delivery. [Read more →](https://aspect.build/shipped/selective-delivery-aspect-cloud) ## [Aspect Cloud is generally available](https://aspect.build/shipped/aspect-cloud-ga) ![Sign in to Aspect Cloud and see your builds in the Build Results UI](https://mintlify.s3.us-west-1.amazonaws.com/aspectbuild/images/marketing/illustrations/aspect-cloud-hero.svg) A hosted Bazel remote cache shared by CI and every developer, with every build in the Build Results UI. Sign up, log in, add `--remote`. [Read more →](https://aspect.build/shipped/aspect-cloud-ga) ## [Warm Bazel worktrees for parallel agents](https://aspect.build/shipped/aspect-worktree) ![Pooled worktree slots, each holding a warm Bazel output base](https://mintlify.s3.us-west-1.amazonaws.com/aspectbuild/images/marketing/illustrations/shipped-aspect-worktree.svg) `aspect worktree` hands each branch or coding agent a pooled git worktree at a path Bazel has already built in, so it starts with a warm output base instead of a cold build. [Read more →](https://aspect.build/shipped/aspect-worktree) ## [Reclaim the disk Bazel never collects](https://aspect.build/shipped/aspect-gc) ![aspect gc removes orphaned and idle output bases and reclaims their disk](https://mintlify.s3.us-west-1.amazonaws.com/aspectbuild/images/marketing/illustrations/shipped-aspect-gc.svg) `aspect gc` removes Bazel output bases whose workspace is gone or that have sat idle, and prunes the download cache. `aspect output-bases` shows what's on the machine first. [Read more →](https://aspect.build/shipped/aspect-gc) ## [Watch mode for aspect run and aspect gazelle](https://aspect.build/shipped/run-watch) ![An edit rebuilds the target and reloads the running process](https://mintlify.s3.us-west-1.amazonaws.com/aspectbuild/images/marketing/illustrations/shipped-run-watch.svg) `aspect run --watch` rebuilds a binary as you edit and restarts it only when its runfiles change. Dev servers can take the change in place over the ibazel protocol or the Incremental Build Protocol, and `aspect gazelle --watch` keeps BUILD files current. [Read more →](https://aspect.build/shipped/run-watch) ## [Run AXL before and after any task](https://aspect.build/shipped/axl-task-hooks) ![Pre-task and post-task hooks around a task body](https://mintlify.s3.us-west-1.amazonaws.com/aspectbuild/images/marketing/illustrations/shipped-axl-task-hooks.svg) `ctx.hooks.pre_task` and `ctx.hooks.post_task` run AXL around every Aspect CLI task. Post-task hooks receive the task's `TaskConclusion`, even when the task exits early or errors. [Read more →](https://aspect.build/shipped/axl-task-hooks) ## [Aspect docs in your AI assistant](https://aspect.build/shipped/docs-mcp-server) ![An AI assistant's answer citing a section of an Aspect docs page](https://mintlify.s3.us-west-1.amazonaws.com/aspectbuild/images/marketing/illustrations/shipped-docs-mcp-server.svg) The Aspect docs are served over MCP at `https://aspect.build/mcp`, so Claude, Codex, Cursor, and VS Code can search and cite them while they work in your repository. [Read more →](https://aspect.build/shipped/docs-mcp-server) ## [Build results for AI agents, over MCP](https://aspect.build/shipped/build-results-mcp) AI assistant · aspect mcp Why did last night's main build fail? Is it flaky? list\_invocations tail\_build\_log get\_target\_stats It failed on `//app/server:integration_test`, a timeout on the log's last page. That test has failed intermittently across recent main builds, so it's flaky, not broken by this change. `aspect mcp` gives Claude Code, Codex, Cursor, and other MCP clients read-only access to your builds, logs, targets, and flake rates, using your existing Aspect login. [Read more →](https://aspect.build/shipped/build-results-mcp) ## [Aspect Workflows 6.0, with a rebuilt Build Results UI](https://aspect.build/shipped/workflows-6-0) ![Two builds compared side by side in the Build Results UI](https://mintcdn.com/aspectbuild/mPlChZw_LzKUv7Pq/images/marketing/web-ui/build-compare.png?fit=max\&auto=format\&n=mPlChZw_LzKUv7Pq\&q=85\&s=81a8f96973b38cd0fc5a99c80e4a423a) Workflows 6.0 brings Aspect Enterprise a rebuilt Build Results UI with build search, target trends, and build comparison, on a new build event stack. [Read more →](https://aspect.build/shipped/workflows-6-0) ## [macOS remote execution on Aspect Enterprise](https://aspect.build/shipped/macos-remote-execution) ![Bazel routes Linux actions to the Linux pool and Apple actions to a Mac pool in the same cluster](https://mintlify.s3.us-west-1.amazonaws.com/aspectbuild/images/marketing/illustrations/shipped-macos-remote-execution.svg) Mac workers join the same remote execution cluster as your Linux pools, so Apple-platform actions request `OSFamily = Darwin` and one `bazel test //...` covers both. [Read more →](https://aspect.build/shipped/macos-remote-execution) ## [Target trends in the Build Results UI](https://aspect.build/shipped/target-trends) ![Targets page with sparklines and a ranked target table, including P90 artifact size](https://mintcdn.com/aspectbuild/mPlChZw_LzKUv7Pq/images/marketing/web-ui/target-trends.png?fit=max\&auto=format\&n=mPlChZw_LzKUv7Pq\&q=85\&s=a39e3372b301bcbd7b67645603dcd773) The Targets page follows every target across builds for up to a year, ranked by wall time, critical-path share, artifact size, cache hit rate, or flake rate. Trend view sorts by how much each one changed. [Read more →](https://aspect.build/shipped/target-trends) ## [The Bazel profile timeline, in the browser](https://aspect.build/shipped/profile-timeline) ![Timing tab showing the critical path, main thread, and evaluator threads](https://mintcdn.com/aspectbuild/mPlChZw_LzKUv7Pq/images/marketing/web-ui/build-timeline.png?fit=max\&auto=format\&n=mPlChZw_LzKUv7Pq\&q=85\&s=1ac2f5f8aa49aa7d30e884f4d3f94e7f) The Timing tab renders each build's Bazel profile in place, with the critical path on top, zoom, shift-drag to measure a span, and search by target or mnemonic. [Read more →](https://aspect.build/shipped/profile-timeline) ## [Spot instances for remote execution workers on AWS](https://aspect.build/shipped/spot-rbe-workers) ![A worker pool with one on-demand instance and several Spot instances, writing to cache storage that stays on-demand](https://mintlify.s3.us-west-1.amazonaws.com/aspectbuild/images/marketing/illustrations/shipped-spot-rbe-workers.svg) AWS remote execution worker pools can run on EC2 Spot, per pool and off by default. Set `ec2.use_spot = true` and tune the mix with `ec2.instance_policy`. [Read more →](https://aspect.build/shipped/spot-rbe-workers) ## [aspect cache diff: affected tests, from the remote cache](https://aspect.build/shipped/cache-diff) ![A cache miss in the dependency graph marks the two tests that depend on it, and aspect cache diff prints them](https://mintlify.s3.us-west-1.amazonaws.com/aspectbuild/images/marketing/illustrations/shipped-cache-diff.svg) `aspect cache diff` lists the test targets your working tree affects by probing the remote cache, and runs no tests. Pipe the result into `bazel test`. [Read more →](https://aspect.build/shipped/cache-diff) ## [Start a Bazel workspace with aspect init](https://aspect.build/shipped/aspect-init) ![aspect init my-app --preset js produces a workspace with MODULE.bazel, BUILD.bazel, a lockfile and tools/repin](https://mintlify.s3.us-west-1.amazonaws.com/aspectbuild/images/marketing/illustrations/shipped-aspect-init.svg) `aspect init` is now a native Aspect CLI command. Pick a language preset and it renders a workspace that builds, with toolchains, Gazelle, format, lint, and real lockfiles. [Read more →](https://aspect.build/shipped/aspect-init) ## [Keep typing bazel with the tools/bazel wrapper](https://aspect.build/shipped/tools-bazel-wrapper) ![bazel commands pass through tools/bazel, which routes build, test and lint to aspect and query, info and clean to Bazel](https://mintlify.s3.us-west-1.amazonaws.com/aspectbuild/images/marketing/illustrations/shipped-tools-bazel-wrapper.svg) `aspect setup tools-bazel-wrapper` installs a `tools/bazel` script that sends `build`, `test`, `lint`, and the other Aspect verbs to `aspect` and everything else to Bazel, so your team keeps typing `bazel`. [Read more →](https://aspect.build/shipped/tools-bazel-wrapper) ## [Bazel results on GitLab merge requests](https://aspect.build/shipped/gitlab-support) ![A GitLab merge request with a commit status per Aspect task and a rolling summary note](https://mintlify.s3.us-west-1.amazonaws.com/aspectbuild/images/marketing/illustrations/shipped-gitlab-support.svg) The Aspect CLI posts a commit status per task, one live summary note, and inline `aspect lint` findings to GitLab merge requests, on gitlab.com or your own instance. [Read more →](https://aspect.build/shipped/gitlab-support) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.