Coding Agents
Connect a coding agent to BetaHub with one prompt. It sets up a project for your game, reads your reports, and works on bugs and suggestions for you.
Overview
A coding agent is an AI tool that works in your game’s folder and can run commands: Claude Code, Cursor, Codex, VS Code with Copilot, Gemini CLI and others.
- No token to copy. The prompt holds no password or token. The agent opens a BetaHub page in your browser, you approve it, and the agent saves its own access.
- Project setup. The agent creates the project, switches on modules your plan includes, creates the token your game reports bugs with, and adds BetaHub to your game.
- Work on reports. Afterwards it reads everything you can see in BetaHub and, if you allow it, triages bugs and suggestions.
- Visible to your team. Every change it makes shows in the activity feed with the previous value.
The agent works through the BetaHub MCP server and the BetaHub API.
When to Use
- You are starting a BetaHub project and your game’s code is open in a coding agent.
- You want the in-game SDK or the HTML widget wired up without copying tokens by hand.
- You have a project and want to ask your agent which bugs to fix first, or have it update statuses, priorities, tags and duplicates while it works on the code.
To set up an MCP client yourself with a token you create, see Using a Personal Access Token.
Prerequisites
- A BetaHub account. You approve the agent in a browser where you are signed in, so two-factor sign-in applies.
- A coding agent that can run commands. If it can’t open a browser (for example over SSH or in a container), it shows you the link to open.
- To create a project in an existing organization, you must be its admin. If you administer no organization, the agent creates the project in a new one.
Connecting an Agent
For a New Project
- Create a project, for example with New Project on the Projects page.
- The first step asks how. Under Let your coding agent do it, click Use my coding agent.
- Open your coding agent in your game’s folder and paste the prompt shown on the page:
Set up BetaHub for this game by following https://app.betahub.io/agents/setup.md
- Approve the agent in your browser. See Approving the Agent.
The page follows the setup: agent connected, project ready, how reports arrive, first report. It updates by itself for 30 minutes. You can close it; your agent carries on.
Prefer to do it yourself? Click Set up manually and follow Project Setup. You can connect a coding agent later.
For an Existing Project
Developers see the card Work on this game with your coding agent on the project overview. Click Copy prompt and paste the prompt into your coding agent. The same prompt is in Settings → Integrations → AI Assistants. It names your project:
Connect to my BetaHub project "My Game" by following https://app.betahub.io/agents/setup.md
You can hide the card. Other ways to connect on the card opens the page with the manual setup.
What the Agent Asks You
Before it creates anything, the agent asks what the code doesn’t tell it: the game’s name, where players talk (a Discord server, Steam discussions, nowhere yet), where the game is (closed playtest, open beta, released), and where your team tracks work. It then proposes one or two ways for reports to arrive and says which need a higher plan.
Approving the Agent
The agent opens a page titled “Connect a coding agent?”.
- Check that the code on the page matches the one your agent shows. If you didn’t just ask an agent to connect, click Cancel.
- Under What may it do?, choose:
- Read and work on reports (the default): it reads everything you can see and works on bugs and suggestions.
- Read only: it reads and changes nothing.
- With Read and work on reports, under Where may it make changes?, untick the organizations it should not change. All are ticked by default. This does not limit what it reads.
- If the agent sets up a project, pick one under Which project?: a new project in an organization you administer, or an existing project whose settings you can edit.
- Click Approve.
Setting up a project works with either access level.
The page also has two switches, off by default: Let it message players and Let it change visibility, NDA and integrations. Today the second one lets the agent add your project’s first NDA from a document you give it, require the NDA of new members, and make tester links that skip it. The first is for features that come later, so turning it on changes nothing yet.
You get an email every time you approve an agent, with a link to disconnect it.
The agent names itself, for example “Claude Code (MacBook)”. A second agent connected under a name already on your list gets a number, such as “Claude Code (MacBook) 2”.
The agent saves its token in its own user-level settings, never in your repository. Its BetaHub tools appear in a new session: start one, or restart the agent.
What the Agent Can Do
The agent can do no more than you can. A change your role in the project doesn’t allow is refused for the agent too.
Read
Everything you can see in BetaHub: projects, bugs with their attachments, suggestions, releases, sentiment and Steam discussions. The access lasts until the agent goes unused for 90 days. Each use starts the 90 days again.
Work on Bugs and Suggestions
With Read and work on reports, in the organizations you ticked:
- Bugs: status, priority, assignee, release, tags, custom fields, title and description; archive and unarchive; merge a duplicate into the original and undo the merge; confirm or reject a duplicate BetaHub flagged, or take a bug out of a duplicate; change the status, priority, release or assignee of many bugs at once.
- Suggestions: move a suggestion along its statuses (under review, planned, started, completed, declined); approve, reject or restore a suggestion waiting in moderation; merge duplicates and undo the merge.
-
Discord forms: build a form step by step, change it, and switch it on or off. A step can save its answer in a custom field, or create one as the builder does when your role may. A form reaches players only after it is switched on and set in Discord with
/set, so the agent gives you the command and the builder link to check it first. It asks you before changing a form that is switched on, and never deletes one. - Testers: invite them to a project, by a link the agent gives you to share or by email. BetaHub sends at most 10 invitation emails a day for all your agents together; past that, the agent gives you the link to invite the rest yourself. On a project with an NDA, its links ask testers to accept it, unless you let the agent change visibility, NDA and integrations. It invites testers only: you invite developers and support members, from the link it gives you. The activity feed shows each invitation, without the link or the addresses.
- Custom fields: create one for bugs, suggestions or tickets, for example a build version your game fills in through the SDK. It never makes a field required, since that would refuse reports from game builds that don’t send it, and never changes or deletes a field.
- Log redaction: list the patterns that hide personal data in uploaded logs and add your own, switched on. It never switches one off or deletes one.
- Support bot: load help articles into Support Knowledge, from text, files or web pages, and update an article by loading it again under the same title or URL; change Game Facts field by field; and change the bot’s personality, tone, length, footer and source links. The bot answers players from these at once, so the agent asks you first. It never deletes an article and never switches the bot’s engine. The activity feed shows each change, with an article’s previous text when the agent replaced it.
- NDA, with Let it change visibility, NDA and integrations: add the project’s first NDA from a PDF or text you give it, which switches the NDA on, and require it of new members. It never writes an NDA itself. A later version, or asking members who already joined to accept, can make everyone accept again, so you do that on the NDA page; the agent gives you the link. The activity feed shows each new version and each change of the setting, a person’s too.
Set Up One Project
For 24 hours, or until the first bug report arrives through the token it created:
- create the project, if you picked a new one (one project only);
- switch on modules your plan includes;
- create the token your game reports bugs with, and add the SDK or the HTML widget to your game;
- if you are an admin of the organization, email a link to pay for a plan to the person you name (Share with Finance). You get a copy.
The agent never changes your plan. When a feature needs a higher plan, it suggests one and opens the upgrade page in your browser, where an organization admin picks the plan.
To finish, the agent asks you to send a test report from the game. It doesn’t send one itself: the first report proves the game is wired up and ends the setup.
A Discord bot, a hosted feedback form and Steam discussions need you in the browser. The agent gives you the link. Testers it can invite itself, as above.
What It Cannot Do
- Delete anything.
- Edit a reporter’s draft, or rewrite what players wrote in a suggestion.
- Change your plan or payment details, or manage tokens or two-factor sign-in.
- Deactivate a project. At the active project limit, it lists your active projects and links you to where you deactivate one.
- Not yet: change tickets, releases, comments or project settings, change or remove members, or message players. These come with later BetaHub updates.
When the agent can’t do something, it gives you a direct link to the page where you do it and says what to click.
Asking for More
When the agent needs more than you approved, for example to make changes in an organization you didn’t tick, it asks you in the browser again. The page is titled “Give your agent more access?”. It shows what the agent can already do and what it asks for, and the organization it needs is ticked. The agent keeps its token and its MCP settings.
What Your Team Sees
- The activity feed and each bug’s history show every change with the previous value, as “you via agent name”.
- An agent makes at most 300 changes an hour. A change to many bugs counts each bug. Past the limit it stops and tells you; it can make changes again when the hour ends. Reading is not limited.
- An account is one person’s. While one coding agent session works on it, other sessions of the same account share 30 requests every 5 minutes. The agent tells you why and links to the page where an organization admin adds a seat. If someone else works with you, give them their own seat. A second terminal of yours waits at most two minutes after the first one goes quiet.
Titles, statuses and tags can show on public boards and in notifications to reporters. BetaHub tells the agent to confirm with you before it changes many things.
Managing Your Agents
On your Profile, in the API Access card, click Manage API Tokens. The Coding Agents card lists each agent with its last use, what it may do, and when it expires.
- Make read only: the agent keeps reading and changes nothing.
- Stop changes here: for an agent that makes changes in several organizations, it stops making changes in that one.
- Turn off: turns one of the two switches off.
- Disconnect: the agent stops working.
Each applies at once.
A disconnected agent asks to connect again by itself. Nothing changes until you approve it in your browser.
Notes to the BetaHub Team
When an agent can’t tell how to do something, it looks in this documentation first. If the answer isn’t there, or something blocks you, it sends a short note to the BetaHub team. At the end of a task it also sends one note listing what it had to hand to you because BetaHub could not do it yet. It tells you what it sent.
- Notes go to BetaHub support, with your email address to reply to.
- BetaHub asks the agent to leave out tokens, passwords and personal data.
- Your agents together send at most 10 notes an hour.
Security
- Players write the reports the agent reads. A report can contain text meant to steer the agent. Every result the MCP server returns tells the agent that player text is data, not instructions. The limits that matter are enforced by BetaHub: the organizations you ticked, the hourly limit, and what your role allows.
- The agent never asks you for a password or a token.
- The agent token works only for API calls. It can’t sign in to the BetaHub website or approve more access for itself.
- Review the activity feed if an agent made changes you didn’t expect, and use Make read only or Disconnect.
Troubleshooting
The Tools Don’t Show Up After Connecting
Coding agents load MCP servers when a session starts. After the agent saves its token, start a new session (or restart the agent) to get the BetaHub tools.
The Agent Was Disconnected
After you click Disconnect in Profile → Access Tokens and Coding Agents, the agent’s next call fails and it asks to connect again. Nothing happens until you approve it in your browser. If you meant to stop it, click Cancel there.
The Agent Says Another Session Is Working
A BetaHub account is one person’s. While one coding agent session works on it, other sessions on the same account share 30 requests every 5 minutes. If a teammate uses your account, give them their own seat; the agent’s message links to the page. If it is only you, finish in one session.
The Agent Says It Made Too Many Changes
The agent reached 300 changes an hour. It can make changes again when the hour ends. Reading still works.
The Agent Hit the Active Project Limit
On the free plan an organization has a limit of active projects. The agent lists your active projects with links. Deactivate one you no longer need, or upgrade. See Active Project Limit.
See Also
- AI Assistants – MCP server, its tools, and setup with a personal access token
- Personal Access Tokens – Tokens you create, and where your coding agents are listed
- Project Setup – Create and configure projects
- Organizations – Plans, the active project limit and Share with Finance
- Developer Dashboard – Your project’s setup guide and inbox