Authenticate the Turborepo CLI to a remote cache provider: for Vercel Remote Cache run `npx turbo login` and `npx turbo link`, or configure a self-hosted Turborepo Remote Cache server and set `TURBO_API`, `TURBO_TOKEN`, and `TURBO_TEAM` environment variables
Confirm `turbo.json` has `pipeline` entries with correct `outputs` arrays for each task — only declared outputs are cached and restored
In CI, expose the cache environment variables as CI secrets so that runners can write to and read from the remote cache
Run `npx turbo run build test --team=YOUR_TEAM` — on a cache hit Turborepo replays terminal output and restores artifacts without re-executing; on a miss it runs and uploads the result
Verify cache hits locally by running the same command twice; the second run should show `>>> FULL TURBO` (all tasks cached) if inputs have not changed
Use `--filter` to scope runs to specific packages: `npx turbo run build --filter=@myorg/api...` to build a package and its dependencies only
Known gotchas
Cache keys are derived from input file hashes, environment variables listed in `globalEnv`, and the task's pipeline configuration — undeclared environment variables that affect build output cause cache poisoning (stale artifacts served as fresh)
Turborepo does not cache tasks where `outputs` is an empty array or omitted — explicitly list all file outputs (dist/, .next/, etc.) for every task that should be cached
Self-hosted remote cache servers must implement the Turborepo Remote Cache API spec; using an incompatible server results in silent cache misses rather than errors
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp