Set up with AI

Instead of clicking through the dashboard, give your AI assistant one prompt. It uses the Venelx MCP server to inspect your repo, create the project, configure it and run the first build. It asks before anything sensitive, such as env values or signing credentials.

Prerequisites

• A Venelx account with GitHub connected (Account settings in the dashboard).
• The Venelx MCP server installed and logged in: run npx @venelx/mcp login and approve in your browser.
• The MCP server added to your client (Claude Code, Cursor, or another MCP client). See MCP Server for the exact config.

The prompt

Set up this repository on Venelx using the venelx MCP server.

1. Run detect_project_setup on this repo and show me what it found (GitHub URL, branch,
   build stack, platforms, app folder). If there is no GitHub remote, stop and tell me:
   Venelx builds from GitHub.
2. Call create_project with the detected name, githubUrl, buildStack and defaultBranch.
   If the stack is ambiguous, ask me which one.
3. If the app is not in the repo root, call update_project_settings with the rootDirectory.
4. For every key in envKeys, ask me for the value (do not read my .env file) and set it
   with set_env_var. Mark secrets as secret.
5. If detect_project_setup lists gitignored build files (google-services.json, keystore,
   local.properties), upload them with sync_build_files, after telling me which files.
6. Signing: run discover_local_ios_signing and discover_local_android_signing, show me
   what was found, and only sync after I say yes. Then check signing_status.
7. Run list_workers. If no worker is online, call worker_install_command and give me the
   command to run on the build machine, then wait for me to confirm it is paired.
8. Call trigger_build for the main platform, follow it with build_status and tail_logs, and
   if it fails, diagnose it. Fix build configuration with get_build_config and
   update_build_commands; do not change my source code unless I ask.
9. Finish with a short summary: project id, what was configured, build result, anything left.

Rules: never print token values or secret values; ask before any step that uploads
credentials; stop and ask if something is unclear.

The same text is available at https://docs.venelx.com/ai-setup-prompt.txt.

What happens

1. The assistant inspects your repo and shows what it found: GitHub URL, branch, build stack, platforms and app folder. Venelx builds from GitHub, so a repo without a GitHub remote stops here.
2. It creates the project with the detected settings, and sets the app folder if it is not the repo root.
3. It asks you for the value of each environment variable it finds. It does not read your .env file. Secrets are marked as secret.
4. It uploads gitignored build files (such as google-services.json, keystores, local.properties) after telling you which ones.
5. It discovers iOS and Android signing on your machine, shows you what it found, and syncs only after you say yes. Then it checks signing status.
6. It checks for an online worker. If none is online, it gives you an install command to run on your build machine and waits until you confirm pairing.
7. It triggers a build for the main platform, follows the logs and, if the build fails, diagnoses it by adjusting build configuration. It does not change your source code unless you ask.
8. It finishes with a summary: project id, what was configured, build result and anything left to do.

Worker install commands

Run on the machine that will build:

curl -fsSL https://get.venelx.com | sh

On Windows (PowerShell):

irm https://get.venelx.com/win | iex

See Workers for pairing and requirements.

Not using AI?

Follow the manual walkthrough in Getting Started.