limrun-bazel — Claude Code skill for remote Bazel builds on Limrun
limrun-bazel — a skill that teaches coding agents to set up and run Bazel builds for iOS and Android on Limrun's shared build plane. Handy when a machine lacks Xcode or the Android SDK.
MIT 28,800 installs ★ 2 updated 2026-10-23
npx skills add limrun-inc/skills --skill limrun-bazel -a claude-codeWhat limrun-bazel does
The skill covers moving a Bazel workspace to remote builds on Limrun. Apple targets run on Limrun's Mac workers, Android targets on Linux workers, and every build in the organization shares one remote cache. Without --config=limrun, Bazel behaves exactly as before.
Setup has two parts: install the lim CLI via npm, then run lim bazel setup inside the workspace. Setup walks up to the directory containing MODULE.bazel, writes a gitignored .limrun/ config, and adds a try-import to .bazelrc. It requires Bazel 8 or newer plus rules_apple or rules_android in the root MODULE.bazel. For Android it asks to add rules_cc, rules_java, protobuf and hermetic_android_toolchains.
Auth goes through lim login or a LIM_API_KEY variable. Only the npm install puts the credential helper lim-bazel-credentials on PATH; the standalone tarball and DotSlash builds skip that, so Bazel cannot authenticate with them. Built apps go to a Limrun simulator or emulator via lim ios sync or lim android install-app. In CI you set LIM_API_KEY as a secret and run lim bazel setup --yes.
What it helps with
- build an iOS Bazel target without local Xcode
- build an Android Bazel target without a local Android SDK
- share one build cache across an organization
- set up Bazel remote execution in CI
- debug a
--config=limrunbuild that fails on auth or worker capacity
Example prompts for the agent
- Set up this Bazel project for remote builds on Limrun and build the
//app:apptarget. - My build with
--config=limrunfails with an authentication error. What should I check? - Install the built
.ipaon a Limrun simulator.
How to install limrun-bazel
1Skills CLI (Vercel)
npx skills add limrun-inc/skills --skill limrun-bazel -a claude-code2Manually: put the files in place
~/.claude/skills/limrun-bazel/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/limrun-bazel/
1Skills CLI (Vercel)
npx skills add limrun-inc/skills --skill limrun-bazel -a codex2Manually: put the files in place
.agents/skills/limrun-bazel/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add limrun-inc/skills --skill limrun-bazel -a cursor2Manually: put the files in place
.cursor/skills/limrun-bazel/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install limrun-inc/skills skills/limrun-bazel2Manually: put the files in place
.github/skills/limrun-bazel/SKILL.md1Skills CLI (Vercel)
npx skills add limrun-inc/skills --skill limrun-bazel -a gemini-cli2Platform CLI
gemini skills install https://github.com/limrun-inc/skills --path skills/limrun-bazelManually: put the files in place
.devin/skills/limrun-bazel/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add limrun-inc/skills --skill limrun-bazel -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about limrun-bazel
How do I install limrun-bazel in Claude Code?
Run npx skills add limrun-inc/skills --skill limrun-bazel -a claude-code. The skill lands in ~/.claude/skills/limrun-bazel/SKILL.md.
What does limrun-bazel do?
It describes how to point a Bazel workspace at Limrun's build plane: lim bazel setup, building with bazel build --config=limrun, a shared remote cache, and running the built app on a Limrun simulator or emulator.
What are the requirements for this skill?
Bazel 8 or newer, rules_apple or rules_android in the root MODULE.bazel, and the npm-installed lim CLI at version 0.44.0 or later. Android builds also need rules_cc, rules_java, protobuf and hermetic_android_toolchains in MODULE.bazel.
Source text
SKILL.md · MIT
--- name: limrun-bazel description: "The default way to build any Bazel workspace on Limrun: build its iOS and Android targets on Limrun's shared build plane with `lim bazel setup` and `bazel build --config=limrun`, from any environment (Linux, Windows, macOS, VM, container, CI), with one remote cache shared across the organization. Use when the project is a Bazel workspace (MODULE.bazel) with rules_apple or rules_android and the user wants to build it remotely, run the built app on a Limrun simulator or emulator, set up Bazel remote execution in CI, or fix a `--config=limrun` build that fails on authentication, workers, or missing MODULE.bazel lines. limrun-xcode-bazel covers only the legacy `lim xcode rbe` flow; use it only when the workspace already runs on `lim xcode rbe` or the user asks for it. For non-Bazel Android builds, use limrun-gradle." user-invocable: true effort: high --- # Bazel on Limrun's build plane `lim bazel setup` points a Bazel workspace at Limrun's build plane: Apple actions run on Limrun's Macs, Android actions on Limrun's Linux workers, and every build of the organization shares one remote cache. Bazel keeps running where it already does; no local Xcode or Android SDK is needed for the remote actions. ## Auth and CLI Install with npm: `npm install --global lim` (0.44.0 or later). The npm package also installs `lim-bazel-credentials`, the credential helper Bazel calls; the standalone tarball and DotSlash builds do not put it on `PATH`, so Bazel cannot authenticate with them. Auth is `lim login` or `LIM_API_KEY` (it may already be set even when the shell does not show it; check before asking). The helper reads only `lim login` or `LIM_API_KEY`, never a key passed with `--api-key`. The CLI is the source of truth: if a flag errors, check `lim bazel setup --help` instead of guessing. ## Set up Run inside the workspace (it walks up to the directory with `MODULE.bazel`): ```bash lim bazel setup ``` It needs Bazel 8 or later and `rules_apple` or `rules_android` in the root `MODULE.bazel`. It writes a gitignored `.limrun/` with the `--config=limrun` configuration and adds a `try-import` to `.bazelrc`. Nothing secret is written: Bazel asks the credential helper for a short-lived token. - **Region:** setup picks the closest region that runs a build plane. `--region <name>` pins one. - **Android:** Linux workers need `rules_cc`, `rules_java`, `protobuf` and `hermetic_android_toolchains` in the root `MODULE.bazel`. Setup prints the missing lines and asks; `--yes` adds them without asking. Without a terminal and without `--yes` it stops and prints the lines, so pass `--yes` in scripts and CI. - **Java runtime:** a `--java_runtime_version` already in `.bazelrc` is kept; otherwise the limrun config uses `remotejdk_17`. - Re-run setup after upgrading the CLI or when the workspace starts using Apple or Android rules. Do not hand-edit `.limrun/`. ## Build ```bash bazel build --config=limrun //your:target ``` Build actions run remotely and Bazel downloads only the top-level outputs (the `.apk` or `.ipa`). Without `--config=limrun`, Bazel builds as before. Own flags for the limrun path go in `user.limrun.bazelrc` at the workspace root; the generated config imports it last and it survives re-running setup. In CI: install `lim` from npm, set `LIM_API_KEY` as a secret, run `lim bazel setup --yes`, then build with `--config=limrun`. ## Run the app Build for the simulator or emulator, then install the `.ipa` or `.apk` path Bazel prints: ```bash lim ios create && lim ios sync bazel-bin/App/App.ipa lim android create && lim android install-app bazel-bin/app/app.apk ``` Re-run `lim ios sync` after each rebuild; it sends only the difference. To drive the running app, use limrun-ios-simulator or limrun-android-emulator. ## Check results The console's Bazel page (`https://console.limrun.com/bazel`) lists the organization's builds from every region, with live output for running builds and the remote cache hit rate per build. ## When a build fails - **Bazel cannot authenticate** or reports a credential helper error: check that `lim-bazel-credentials` is on `PATH` (npm install) and that `lim login` or `LIM_API_KEY` is set where Bazel runs. - **"the build plane could not start a worker"** or **"no linux worker is free"**: transient capacity; retry the build. - **Missing `@androidsdk` or Android toolchain errors:** the `MODULE.bazel` lines are missing. Re-run `lim bazel setup` and accept them. - **Each region keeps its own cache:** the first build in a new region starts cold.
© limrun-inc · MIT · limrun-inc/skills