Build from GitHub

Point Mesh Builder at the repository your API lives in. Ada, the AI that writes your tools, reads one folder of one branch, finds the routes and writes a tool for each. On Pro and Team, she can also keep those tools in step with your code: when you push a change to your API, she updates the tools that it affects and emails you a draft to review.

Nothing goes live on its own. You review every draft, allow its access and publish it.

Connect GitHub

Glxymesh reads repositories through its own GitHub App. You install it on the GitHub account that owns the code (you, or an organization) and choose which repositories it may see.

1. In the console, open Mesh Builder, start a New build and choose GitHub repository.
2. Choose Install on GitHub. GitHub opens in a new window. Pick the account and the repositories Glxymesh may read, then install.
3. GitHub sends you back and the account appears in the sheet. To add another person or organization later, choose Add account.

If the app is already installed on that account, for example by a colleague, choose Link it instead and sign in with GitHub to connect it to your organization in Glxymesh.

What the app can do

GitHub permission	Access	Why
Repository contents	Read-only	To read the folder you pick, and what a push changed
Metadata	Read-only	To list your repositories and branches
Push events	Webhook	To hear about pushes, for updates from GitHub

Glxymesh never writes to your repository. To disconnect it, uninstall the app on GitHub (Settings → Applications → Installed GitHub Apps); the account disappears from Glxymesh too.

Build tools from a repository

1. In the Build from GitHub sheet, pick the account and the repository.
2. Choose the branch, and the folder your API lives in, such as /services/api. Use / for the whole repository.
3. Choose Use this repository, say what the tools are for if you like, and start the build.

Ada uses an OpenAPI or Swagger file if the folder has one. Otherwise she reads the routes in the code, and how requests are authenticated. She writes one tool per route, and leaves out admin and internal routes unless you ask for them.

Your API runs on your own server, so its address is a vault host named after it, like {BILLING_API_HOST}. You store the address and the API’s key in the project’s vault when you review the draft; Ada never sees either.

What Ada reads

• One folder of one branch, at the latest commit.
• Not dependency and build folders (node_modules, vendor, dist, build, .venv and the like), binary files, or files over 256 KB.
• Never key and env files (.env, *.pem, *.key, credentials.json and the like). Anything in the code that looks like a live credential, such as an sk_live_ key, is removed before Ada reads it.

The folder is read for the build and deleted after it. Up to 5,000 files and 16 MB are read; a bigger folder is cut short, so pick the folder your routes live in.

Updates from GitHub

Pro and Team

Updates from GitHub are part of the Pro and Team plans. On Free you can still build from a repository; the switch shows Pro and a link to upgrade.

When you pick the repository, switch on Update the tools when this branch changes. From then on, every push to that branch that changes the folder is checked.

1. Is it about the API? A push that only touches docs, tests, CI or editor settings (*.md, docs/, *_test.go, *.spec.ts, .github/ and the like) is skipped straight away, without spending AI credits.
2. Does any tool need to change? Ada reads what the push changed and the list of your tools. Most pushes, such as a refactor, new logging or a fix inside a handler, change no route. Then she stops: no draft and no email.
3. She changes only what moved. When a route a tool calls changed its path, method, parameters or response, she updates that tool. She adds a tool for a new route that fits, and removes a tool whose route is gone. Tools the push didn’t touch are left exactly as they are.
4. She tests the draft. Every changed tool is checked and tested before you see it.
5. You get an email with what changed and a Review the draft link.
6. You publish. Open the draft, allow anything new it needs, and publish. The tools keep the same address and sign-in, so Claude Code, Cursor, Codex and your other clients stay connected.

The email goes to the person who switched updates on. Each update uses AI credits from your organization’s pool; with none left, the push is skipped until credits are back.

Turn updates off

Open a build in that project in Mesh Builder and choose Turn off updates from GitHub. Deleting the project or uninstalling the GitHub App also stops them.

Access you allow once

A draft asks you to allow a host or a key only when it’s new to the project. Once you’ve allowed {BILLING_API_HOST} and stored BILLING_API_KEY, later drafts, including updates from GitHub, don’t ask again. A key you’ve already stored shows Allow if a draft sends it somewhere new, never Store key again.

A draft that sends a key to a host the project has never reached always asks first. That’s how you know an update can’t quietly point your key at another server.