Question 1

How long does setup take?

Accepted Answer

A couple of minutes, start to finish. You connect a GitHub repository to a project and Bundlle handles the rest of the wiring for you — nothing to install, no config to write, and no data to migrate. The moment a repo is linked, new pushes and pull requests begin moving the right tasks on their own.

Question 2

What do I need to connect Bundlle?

Accepted Answer

A GitHub account and a repository. You create a project, link the repo, and authorise the connection — that's everything. Bundlle registers the webhook it needs automatically, so there's nothing to set up by hand.

Question 3

Do we have to change how we work?

Accepted Answer

Not in the slightest. Your team keeps committing, opening pull requests and merging exactly the way they do today — there's no new tool to adopt and no checklist to keep up with. Bundlle works quietly from the activity you already create, keeping the board current in the background while everyone just keeps shipping.

Question 4

Can I try it for free?

Accepted Answer

Yes. The Free plan gives you one project, up to three members and 100 AI credits a month for as long as you like, with no card required to start. Add projects only when you're ready to grow.

Question 5

How does it know which task to move?

Accepted Answer

When work lands, Bundlle looks at what actually changed — the branch, the commit messages, the pull request — and compares it against the open tasks in your project to find the best fit, showing you the reasoning behind the match. Where the work happens sets the new status: starting a feature branch moves a task into progress, opening a pull request moves it into review, and merging marks it done.

Question 6

What moves a task to each status?

Accepted Answer

The trigger decides the destination. A push to a feature branch moves the matching task into In Progress, opening a pull request moves it into Review, and merging the pull request (or pushing straight to the default branch) marks it Done.

Question 7

Does it ever move a task backwards?

Accepted Answer

No. Status only ever moves forward along the flow, so finished work is never dragged back into an earlier column by a later, unrelated event.

Question 8

Does the board update without a refresh?

Accepted Answer

Yes. Every change — an AI auto-move, an email confirmation, an incoming webhook or a teammate's edit — streams onto the board in realtime, so what you're looking at is always current.

Question 9

Can we discuss work and track blockers inside Bundlle?

Accepted Answer

Yes. Every task has a comment thread — @mention a teammate and it lands in their Inbox alongside assignments and AI confirmations. Tasks can also be marked as blocked by other tasks; the moment the last blocker reaches Done, the next assignee is notified that they're clear to start. Attachments, labels, multiple assignees and deadline reminders round out the collaboration basics.

Question 10

What if it moves the wrong task?

Accepted Answer

Bundlle only acts when it's confident. Every match comes with a confidence score and a short, clear reason, so a move is never a black box. When it's highly confident it updates the card for you; when it's only fairly sure, it emails you to confirm before anything changes; and when it's unsure, it leaves the task exactly where it is. It also never moves finished work backwards — and you can always see why something changed in the activity feed.

Question 11

How do the confidence tiers work?

Accepted Answer

Each match gets a 0–100 score. At 80 and above Bundlle moves the task automatically; between 50 and 79 it emails you a one-click yes/no to confirm first; and below 50 it logs the attempt and leaves the board untouched. Every tier is recorded so you can see exactly what it decided and why.

Question 12

It's working in the background — how do I know what it did?

Accepted Answer

Everything it does is on the record. Bundlle keeps a live AI Activity feed next to your board that logs every task it touches — what moved and to which status, the commit, branch or pull request that triggered it, a confidence score, and a short, clear reason for the match. Open any entry and you get the full story: the status flow, a confidence meter, the evidence it actually read, and a timeline of exactly when it acted or emailed you to confirm.

Question 13

Which GitHub events does Bundlle react to?

Accepted Answer

Pushes and pull requests. Bundlle listens for commits landing on branches and for pull requests being opened or merged, then maps each one to the right task and status. Other event noise is ignored.

Question 14

Does it work with multiple repositories?

Accepted Answer

Yes. You link a repository per project, so a workspace with several projects can track several repos at once — each board stays driven by its own repo's activity.

Question 15

Do I need to configure webhooks myself?

Accepted Answer

No. When you link a repo, Bundlle registers the push and pull-request webhook for you and verifies every incoming event by signature. There's nothing to wire up or maintain by hand.

Question 16

Can my AI tools work the board too?

Accepted Answer

Yes. Every workspace comes with its own MCP server. Add its URL to Claude Code, Cursor, or claude.ai as a connector and sign in with your Bundlle account — there are no API keys to manage. Your agent can then read the board, pick up tasks, move them, and leave comments, with exactly the access your role allows: viewers stay read-only, and everything is scoped to that one workspace. Work an agent ships still flows through the same commit matching, so the board follows the work no matter who — or what — is doing it.

Question 17

How do I connect Claude Code or Cursor to Bundlle?

Accepted Answer

Copy the workspace MCP URL from Settings → Integrations → MCP server. In Claude Code, run the one-line add command shown there and sign in when the browser opens; in Cursor, paste the ready-made snippet into mcp.json; on claude.ai, add it under Settings → Connectors as a custom connector. Setup takes about a minute, and the same page shows a green tick once your client is connected.

Question 18

Can other tools move tasks — CI, deploy scripts, GitHub Actions?

Accepted Answer

Yes. Every project has an incoming status webhook: a unique URL with its own token that any tool can POST to with a task and a status. A CI job can move a task to In Review when checks pass, or a deploy script can mark it Done on release. Changes appear on the board live, like every other update.

Question 19

Is our code safe?

Accepted Answer

Yes. Bundlle never stores the contents of your files. It reads only the lightweight details it needs to recognise the work — the branch name, commit message and pull request title — and uses them purely to match the right task. Your source code stays in GitHub, where it belongs.

Question 20

What data does Bundlle actually store?

Accepted Answer

Only the minimal signal it needs: branch names, commit messages and pull-request titles, plus the match decisions it made. File contents and diffs are never persisted, and every event is verified by HMAC signature before it's processed.

Question 21

Do you charge per member?

Accepted Answer

Never. Members are always free on every plan. You pay for the projects you run, not the size of your team, so invite everyone.

Question 22

What counts as a project?

Accepted Answer

A project is a single board inside your workspace — usually one per repository or product area. You pay only for active projects, and you can add or remove them anytime.

Question 23

How do AI credits work?

Accepted Answer

One credit is one push or pull request the AI analyzes to move your tasks. Every paid project adds 1,000 credits a month to your workspace, and the Free plan includes 100. Bot and merge-only events cost nothing, viewing the AI Activity feed is always free, and you can buy extra credits anytime.

Question 24

Can I change plans later?

Accepted Answer

Anytime. Start free, add projects as you grow, and scale back down whenever you need to — changes apply right away.

Questions, answered.

Still have a question?