Developers

GitHub app

Connect your repositories to Buda's Developer Portal to import skills and agents and keep Marketplace listings in sync.

Publish from the repo you already maintain. Connect the Buda GitHub app once, point it at a repository, and Buda imports the skills and agents inside it as Marketplace listings — then re-syncs them whenever the source changes. No copy-pasting, no manual uploads.

Install the GitHub app

Open the Developer Portal

Go to the Developer Portal and open the Repos tab. If no GitHub installation is connected yet, you'll be prompted to connect one.

Authorize on GitHub

Buda sends you to GitHub's app-install screen. Choose the account or organization and grant access to all repositories or just the selected repositories you want to publish from.

Return to Buda

GitHub redirects back to the Developer Portal (/developer/repos) and Buda records the installation against your account. You only do this once — the connection is reused for every repo you add later.

The connection is per-user. Reinstalling on GitHub replaces the previous installation automatically.

Import a repository

With the app connected, add a repo by its GitHub URL and a short description:

  1. In Repos, choose Add repo.
  2. Paste the repository URL (for example https://github.com/your-org/your-skills) and a description.
  3. Save. The repo is created with status pending and Buda kicks off the first sync automatically.

Buda reads the skills and agents in the repo and turns them into Marketplace companies and listings. The Repos view shows how many companies and listings each repo produced.

Sync updates

When you push changes to a connected repo, re-import them with Sync on that repo:

  • New and changed skills/agents are re-imported.
  • Items removed from the repo are unpublished from the Marketplace, and the sync result reports how many were removed.

Sync uses your GitHub installation token, so it can read private repositories you granted access to.

Troubleshooting

  • No repositories listed. Make sure the install granted access to the repos you expect. Open the app's settings on GitHub and add the missing repositories, then return and sync.
  • Connection silently dropped. If GitHub returns a 404 for your installation (for example, the app was uninstalled or access revoked), Buda clears the stale installation and shows an empty repo list. Reconnect from the Repos tab.
  • A listing didn't update. Run Sync again — imports run in the background after create, so a failed first pass is fixed by an explicit re-sync.
  • A removed item is still listed. Sync the repo; removed items are unpublished on the next successful sync.

Connect GitHub to a specific Agent

This page covers the per-user connection used by the Developer Portal. Agents have a separate, per-Agent GitHub connection that's unrelated to Marketplace publishing — it's what lets an Agent's cloud computer read (and, depending on the permissions you grant, push to) real repositories during chat and task runs.

  • Connect — open the Agent, then either click the + menu in the chat composer → IntegrationOAuthGitHub (shows Install GitHub App until it's connected), or open the Agent's Integrations settings and click Connect next to GitHub. Both paths send you through GitHub's install screen to pick the account/org and repositories to grant.
  • Shared by the whole chat — the installation is tied to the Agent, not to you personally. Everyone who can chat with that Agent uses the same GitHub access; only an editor (or owner) of the Agent can connect, replace, or disconnect it.
  • One installation per Agent — connecting again replaces whatever was connected before for that Agent.
  • Disconnect — from the Agent's Integrations settings, open the GitHub row's menu and choose Disconnect. This only forgets the installation on Buda's side; the GitHub App itself stays installed until you remove it from GitHub. There's no confirmation prompt, and disconnecting immediately cuts off access for everyone chatting with that Agent.

This Agent-level connection is completely separate from the per-user connection described above — different installation, different table, different purpose. Connecting GitHub for an Agent does not give you Developer Portal / Marketplace publishing access, and connecting the Developer Portal doesn't give any Agent repo access in chat.

See Git for how the Agent uses this connection to work with real repositories.

On this page