Revyl
com.revyl由 revyl.com 發布v1.0.0更新於 Nov 21, 2026
iOS simulators, Android emulators, web browsers and macOS computers for agents to verify their work
概覽
Revyl 為 AI 編碼代理提供雲端 iOS 模擬器、Android 模擬器、瀏覽器與 Mac,用來執行應用程式測試並驗證工作成果。
- 可以做什麼
- 啟動或接入即時裝置開發迴圈,並與執行中的應用程式互動
- 從雲端裝置擷取螢幕截圖與報告以驗證變更
- 撰寫、驗證、推送並執行自然語言或 YAML 測試、工作流程與應用程式探索
- 將應用程式畫面與 Figma 設計稿或跨平台畫面進行比對
- 在專案中安裝與管理 CLI 的代理技能
- 適用情境
- 適合代理需要實際執行並以視覺檢查 iOS、Android、Web 或 Mac 應用程式,而不只是從程式碼推論時;也適合想把自然語言測試放到雲端裝置執行並接入 CI 的團隊。
- 執行需求
- 需連線 backend.revyl.ai 遠端端點並以 OAuth 登入,另需免費的 Revyl 帳號。文件流程還會安裝 Revyl CLI(shell 安裝腳本、Homebrew、pipx 或 uv)並完成驗證,可用瀏覽器互動登入,或透過 REVYL_API_KEY 使用 API 金鑰。需要連線至 Revyl 雲端服務的網路。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Revyl,將其新增到工作區。
- 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/com.revyl%2Frevyl/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。
{
"mcpServers": {
"revyl": {
"type": "http",
"url": "https://backend.revyl.ai/api/v1/mcp"
}
}
}README
Revyl
Proactive Reliability for Your Apps
[Version] [License: MIT] [Homebrew] [PyPI]
Revyl is an AI-powered testing platform for your apps. Define tests in natural language, run them on cloud devices and computers, and catch bugs before your users do. It works with iOS, Android, web and Mac, supports Expo / React Native / Flutter / native builds, and integrates with your CI pipeline and AI coding tools.
For coding agents
To set up Revyl for a user, run these from the app's directory:
To sign in, run revyl auth login and post the approval URL it prints as a
link; the user can approve it from any browser. A hosted agent with
REVYL_API_KEY in its environment is already signed in; it also runs
revyl auth persist-cloud-env so an MCP server that does not inherit the
variable can use it. Then follow the revyl-cli-dev-loop skill to start a
cloud device with revyl dev --remote --detach --json, and share the
viewer_url it returns.
In a project that already uses Revyl, the open skills installer adds the same recommended skills:
#stable matches the latest CLI release; main can be ahead of it. Name an
optional skill from revyl skill list --all with --skill <name>, and refresh
with npx skills update. For MCP and editor setup, see
MCP Setup.
Install
sh
The sh installer runs on macOS, Linux, and Windows Git Bash, MSYS2, or
Cygwin, where it installs revyl.exe into ~/.revyl/bin and prints the PATH
steps for Git Bash and PowerShell. When it cannot write your shell profile, for
example one Nix manages, it still installs the binary and prints the export PATH line to add yourself.
Windows PowerShell
Homebrew (macOS)
pipx (cross-platform)
uv
The PyPI package is CLI-only and contains the native binary for your platform,
so uv, pipx, and pip do not download executable code at first run.
See Local runtime files for managed storage paths, permissions, and directory-symlink restrictions.
For a restricted or headless runner, see Sandboxed environments. It covers a writable home and runtime state directory, non-interactive PATH, proxy and CA trust, minimum egress, and the boundary between local inspection and authorized cloud actions.
Authenticate
Create a free account at app.revyl.com, then log in via the CLI:
The CLI prints an approval URL and a short code and waits. Open the URL wherever you are signed in — it does not have to be this machine, so the same command works over SSH, in a container, and in a cloud agent.
For an unattended machine, use an API key from your dashboard instead:
Quick Start
revyl init always writes a stable project.id in .revyl/config.yaml. When
detection succeeds, it also writes build.framework and named profiles for the
detected iOS and/or Android platforms before any optional interactive onboarding.
Supplying a project ID writes it locally but does not validate, attach, or publish
it; use -y to stop after local config creation. Authenticated interactive setup
can continue into revyl github setup after the project config has been written.
GitLab automation is configured separately with revyl gitlab setup.
When the connected provider
can access the repository, committing that valid config to the repository's default branch
reconciles a matching server project or creates a new Git-managed project when
its project.id, project root, and config path are unclaimed and its references
are valid. Pull requests validate new configs as unpublished bootstrap candidates;
creation occurs only from the actual merged default-branch commit. revyl config push remains the explicit manual publication and recovery path.
For GitLab automation tokens, terminal connection, and manual webhooks, see Connect GitLab.
For an existing legacy file, preview or perform the local conversion explicitly:
A successfully prepared legacy migration uses one concise human-readable
summary of whether fields will be dropped or defaulted; a write creates an
exact-byte backup. JSON --check output contains the complete migration
proposal and migration ledger. Migration
externalizes legacy top-level test aliases to conflict-checked
.revyl/tests/<alias>.yaml files, preserves an existing matching mapping
byte-for-byte, and stops on destination conflicts because those are unsafe to
write. The retired top-level workflow alias cache is reported and removed.
The conversion exists only in your checkout until you commit it. After
migrating, commit the converted .revyl/config.yaml and any new
.revyl/tests/ files with your change, but not the backup; otherwise every
fresh checkout fails with the legacy-format error again. A write lists those
files, and --write --json reports them in
uncommitted_config_migration.repository_relative_paths_to_commit. Until the
commit lands, commands that read the project config print a one-line stderr
reminder at most once every 24 hours per machine, never with --json or
--quiet. If you can't commit, tell the repository owner.
When authenticated, migration may make read-only verified lookups to reuse or
interactively select a project from the verified repository, resolve enabled
legacy PR-build app names to exact platform app IDs, and resolve legacy PR
workflow names to exact organization workflow IDs.
Missing, duplicate, or inaccessible workflow names are omitted and reported,
including the implicit smoke workflow from the legacy smoke_every_pr
preset. An enabled PR build is never silently omitted: app or framework meaning
that still cannot be resolved is reported as lossy and omitted from the best-effort
proposal. Inspect JSON --check before writing; afterward, compare the reported
backup or ask a coding agent to reconcile omissions. Migration
never creates or attaches a server project, pulls or publishes configuration,
or otherwise mutates server state. Edit the project YAML directly when you
need to change project settings, then run revyl config validate.
You can also create and edit manual-authority projects from the GitHub integration in
the Revyl web app. After creating a project there, run revyl config pull from that
project root (or a directory beneath it). If no local config exists, the CLI verifies
the connected repository and writes the nearest matching project's configuration to
its exact .revyl/config.yaml path; it never imports legacy or invalid remote state.
When an existing config differs, pull creates an exact-byte backup, atomically
replaces the file, and reports the backup path without prompting. If the local
project was deleted and exactly one active replacement owns that same root, pull
performs the same backup and replacement without trusting the stale ID.
Project roots are immutable. Correct a mistaken root by deleting the manual project
in the web app, creating its replacement at the intended root, then running
revyl -C <replacement-root> config pull. A Git-managed project must first return to manual
authority by removing its designated config file from the repository's default branch; that file
removal alone preserves the project and its automation. Project deletion remains a
web operation—there is no CLI project-delete command—and preserves the repository
connection, GitHub installation, report destination, historical results, and work
that already started.
Build profiles are customer-named recipes, not active modes. A profile can
contain an iOS recipe, an Android recipe, or both. Select the profile and
platform per invocation. revyl build executes the recipe on a Revyl cloud
runner by default, with its remote image and caches:
When omitted values have exactly one eligible choice, the CLI resolves them. Otherwise it prompts interactively or fails non-interactively with the valid choices. No profile is stored as active or default.
See Build with Revyl for prerequisites, source uploads,
billing, and migration guidance for existing scripts. Builds land on --branch
when supplied. Otherwise they use your Git branch when automatic Git branch
detection is enabled in the app's Build branches settings, or the app's default
branch when detection is disabled or no Git branch is available. See
Build branches from the CLI.
When you're ready to run outside the dev loop:
Blocking human-terminal test and workflow runs open their completed report by
default. Use --no-open to suppress it. No-wait, JSON, GitHub Actions, CI,
SSH, and other headless executions never open a browser.
YAML-first creation requires the selected project to already have a
.revyl/config.yaml. Pull an existing registered project, initialize a new
local project, or migrate a legacy file before creating the test:
test create --from-file validates and copies the YAML into the selected
project; it never creates or migrates project configuration.
See the Revyl Docs for the full authoring workflow, YAML examples, module imports, and troubleshooting.
revyl devstarts a live-device development loop and installs a build from one named profile/platform recipe. Pass--build-profileand--platformexplicitly, or let Revyl resolve a unique development-like or sole eligible choice. Ambiguous interactive runs prompt; non-interactive runs fail with the valid choices. No profile or platform is stored as active or default.
Agent Skills
For guided comparisons of Figma frames or components with Atlas screenshots, see the Figma review handoff, including a shareable setup prompt and private report or annotation options. For iOS/Android comparisons without Figma, use the cross-platform review handoff. It compares confirmed matching states without treating unmatched screens as missing features.
Interactive revyl init offers optional agent skill setup. Choose your tool
and the skills you want; the recommended skills are preselected, and an empty
selection skips installation. The standalone revyl skill install command uses
the same preselected skill picker:
Without --name, noninteractive installs, --yes, and --json install the
recommended skills from revyl skill list and name them on stderr; --json
output adds "selection": "default". Repeat --name to choose specific
skills, and use --all only when you deliberately want the entire catalog.
Packages live in .agents/skills/, which Cursor and Codex discover directly.
Claude Code uses per-skill relative links under .claude/skills/. Other agents
that read the shared directory can also discover these skills. --global
selects the equivalent directories under your home directory; --copy keeps
independent packages in each selected tool's legacy skill directory instead.
Conflicting legacy packages in any agent directory block shared storage, even
when you selected another agent. This includes retired auth-bypass platform
aliases; Revyl preserves rather than prunes them. Noninteractive installs then
continue as if --copy were given; move conflicting copies aside to switch to
shared storage. In init, choose Claude Code (copy mode) when Claude
compatibility links are unavailable.
A symlinked shared directory must resolve inside the selected project or home
directory. Installation does not modify
AGENTS.md or inject Cursor rules. For client-specific setup and optional MCP,
see MCP Setup.
Installation copies the complete skill package, including source-authored
agent metadata and any references, scripts, or assets. show and export
return only the root SKILL.md, not an installable package. Auth-bypass loads
only the reference for the detected stack. Auth-bypass and Atlas review require
an explicit user request; ordinary workflows allow implicit invocation.
Existing packages are unchanged unless you explicitly use --force, which
replaces the selected package and discards local edits. Prefer
revyl skill update to refresh already-installed, Revyl-managed packages from
your CLI version: it preserves local edits and unmanaged packages, reports conflicts,
and never adds skills. revyl upgrade updates only the binary and may remind
you to run revyl skill update; it does not install or refresh skills.
A customized package is reported as preserved and makes skill update exit
non-zero, so name only the skills you want refreshed. See
Agent skills for the reminder and older CLIs.
Use revyl-cli-dev-loop when you want the agent to start or attach to a generic
Revyl dev loop, interact with the device, and verify with screenshots or
reports. Use revyl-cli-atlas when the agent should explore an app bottom-up as
a graph, opening relevant screenshots at each node and tracing misunderstood
connections backward through edge clips and their originating reports. Use
revyl-cli-atlas-review when the user explicitly asks the agent to create or
manage grounded Atlas annotations. Use
revyl-cli-create when you want the agent to author or refine a
stable Revyl YAML test, validate it, push it, run it, and iterate from reports.
Use revyl-cli-auth-bypass when the agent should set up test-only auth bypass
after inspecting the app. Implement the handler in the detected stack; do not
install a separate platform skill.
Example prompts:
Documentation
For full documentation of the CLI see the Revyl Docs.
Troubleshooting
Xcode / Command Line Tools errors during brew upgrade revyl
If softwareupdate does not install Command Line Tools, reinstall them:
If you use full Xcode builds, install the latest Xcode version from the App Store and then run:
Homebrew directory ownership errors
License
MIT
來源:README.md,提交 fb6e8b2
工具
0版本歷史
1- v1.0.0最新Nov 21, 2026
評分
已滿足適用檢查項的 85%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分