Launch and iterate on apps/mobile from a cloud sandbox (no local Xcode or simulator) using Limrun's remote iOS simulators. Use when asked to run, start, open, or show the mobile app from a cloud workspace, or to verify a mobile change there. On a machine with real Xcode, use mobile-sim-verification instead.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
A cloud sandbox is Linux — no xcrun/simctl. apps/mobile/scripts/limrun-dev.sh is the one command
that gets the real dev-client app running on a Limrun cloud iOS simulator, connected to this sandbox's
own Metro and API. Run it:
apps/mobile/scripts/limrun-dev.sh
It reuses a shared build when one already exists for this branch (seconds, no Xcode sandbox at all) and
only builds when it has to. Pass --rebuild after changing a native dependency or native config (new
native module, Info.plist, entitlements), or --force-prebuild if an EXPO_PUBLIC_* value a native
config plugin reads (not a plain JS read) changed — see apps/mobile/AGENTS.md's "Verifying in the real
app" section for exactly why each of those is needed. Don't re-derive any of this by hand; the script and
that doc are the record of what was actually discovered getting this working (2026-10-02), including two
dead ends (Limrun has no way to persist the Xcode sandbox-exec fix, confirmed by testing a disk-snapshot
restore; .env never reaches the remote build because it's gitignored).
The script prints a console.limrun.com/stream/... URL — share it as a Markdown link if the person asked
to see the app, not just to have it running.
After it finishes, drive the simulator with the limrun-ios-simulator skill (tap, type, screenshot,
element tree, logs) or limrun-maestro-testing for a Maestro flow. The script does not start apps/relay
or tunnel its port, so host/workspace presence features will show as unreachable until that's done too —
fine for auth/UI verification, not for anything host-dependent.
Needs LIM_API_KEY (usually already in .env) and this repo's .env already written
(.superset/setup.sh or .superset/setup.cloud.sh). A 400 cannot create an instance when organization has no remaining credits means the Limrun org needs credits or a subscription — check
console.limrun.com's billing page; there's no CLI command for this.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Personalized audit that teaches the advanced Superset features the user isn't using yet (automations, parallel agents, tasks, multi-host, terminal remote control, custom commands, MCP, pages) and sets them up live. Use when the user wants to get more out of Superset, asks "what else can Superset do", "how do I 10x my workflow", "what am I missing", or wants to learn a specific Superset feature.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a recurring chore into a Superset automation. Drafts the agent prompt, confirms the schedule or event trigger and the target, creates it with the CLI, and reviews the first run together. Use when the user wants a scheduled or recurring agent, a daily or weekly job, or an agent that reacts to a Slack message, GitHub pull request, Linear issue, Sentry issue or incoming email, or says things like "every morning do X", "automate this", "set up a cron agent", "run this on a schedule", "when someone opens a PR, do X".
日本語の概要は準備中です。原文の説明を表示しています。
Open, navigate, screenshot, read, click, and type in web pages from an agent. Use when the user asks to open a URL, preview or verify a running web app, check a page's console, fill a form, click through a web flow, or automate anything in a browser, including "open localhost:3000", "screenshot the page", "what does the console say", "click the submit button", "I'm logged in on Chrome". Drives the in-app browser pane of a Superset workspace by default and Browser Use for browsers the panes cannot reach.
日本語の概要は準備中です。原文の説明を表示しています。
Write Stripe code against what the API does today — plan the product shape, confirm every parameter from Stripe's own docs and schemas, and keep the agent in a sandbox. Use when adding checkout, billing, subscriptions, invoicing, or webhooks to a codebase, or when debugging Stripe integration code that compiles but behaves wrong.
日本語の概要は準備中です。原文の説明を表示しています。
Verify UI behavior end-to-end by driving the running desktop app over the Chrome DevTools Protocol. Use when asked to verify, reproduce, or confirm a UI change, bug, or regression in the real app rather than in tests.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose a failing GitHub Actions run — find the first real error in the logs, tell a flake apart from a genuine failure, and identify the commit that broke it. Use when checks are red on a PR, a workflow failed, the build is broken, CI is flaky, or the user asks why a run failed or whether a failure is real.
日本語の概要は準備中です。原文の説明を表示しています。