Everything in Bundlle, from workspace to task.

A clear tour of how Bundlle is put together — the way work is organized, the people who run it, and what each of them can do.

Coming soonSee the features
Structure

Workspaces, projects, and tasks.

Bundlle nests in three simple layers. A workspace is your organization. Inside it live projects — usually one per repo or product area. Inside each project are the tasks your team actually works on. Everything else hangs off this spine.

  • A workspace holds all of your projects and people
  • A project holds its own board, team and linked repo
  • A task is a single piece of work on that board
Acme workspace
Web App
Fix login button
Billing portal
Marketing Site
Launch hero
Pricing copy

One workspace · many projects · many tasks

Workspaces

One you own, plus any you join.

Every account comes with one workspace you own. Get invited to other teams and you can belong to theirs too — switch between them anytime, with your role shown on each. Members are always free, so there is no reason not to bring everyone in.

  • You own exactly one workspace; you can join many more
  • Switch workspaces from the header at any time
  • Each carries its own projects, members and billing
A

Acme

12 members

Admin
B

Beta Labs

7 members

Member
S

Side Project

3 members

Viewer
Roles & permissions

Everyone gets the right level of access.

Access is set in two places — once across the whole workspace, and again per project — so people see exactly what they should.

Across a workspace

Admin

Runs the workspace and its team day to day.

  • Invite & remove members
  • Create & manage all projects
  • Work across every project

Member

Collaborates on the projects they belong to.

  • Create & move tasks
  • Comment, assign & attach
  • Join project teams

Viewer

Follows along without making changes.

  • Read-only access
  • See boards & insights
  • No edits

Workspace owner

Whoever creates the workspace is its owner — not a role you assign, just the person who set it up. On top of everything an admin can do, only the owner can change member roles, transfer ownership, and delete the workspace.

Inside a project

Project lead

Owns a single project and its board.

  • Manage the project team
  • Link GitHub Issues to tasks
  • Shape the workflow

Project member

Contributes to the project's tasks.

  • Pick up & move tasks
  • Comment & collaborate
  • Be assigned work
Members

Invite by email, manage in one place.

An admin invites teammates by email and picks a role. An invite stays pending until the person signs up and accepts; then it flips to active automatically. Manage everyone — roles and removals — from the Members page.

  • Invite by email with a role attached
  • Pending invites activate the moment they're accepted
  • Remove a member and their project access goes with them
teammate@acme.comMember Invite
AM

Aria M.

aria@acme.com

Admin
DS

Dev S.

dev@acme.com

Member

lena@acme.com

Invite sent

Pending
Projects

A board per project, repo optional.

Each project is a self-contained space: its own Kanban board, its own team drawn from the workspace, and an optional linked GitHub repository. Link a repo and the board starts keeping itself current from your commits and pull requests.

  • Independent board and team per project
  • Link a GitHub repo in a couple of clicks
  • Add people from the workspace as project lead or member
Web App24 tasks
acme/web-app
AMDS+4
Marketing Site11 tasks
acme/marketing
AMDS+4
Tasks

The unit of work.

A task moves through four statuses — Todo, In Progress, In Review and Done — and carries everything you need to act on it: a priority, a description, a deadline, and one or more assignees. It's what your commits ultimately move forward.

  • Four statuses: Todo → In Progress → In Review → Done
  • Low / Medium / High priority and an optional deadline
  • Multiple assignees per task
High priorityIn Progress

Fix login button on mobile

Tap target is too small and the auth flow breaks on narrow screens.

AMDS
Due Fri
Collaboration

Everything happens on the task.

Discuss work right where it lives. Comment and @mention teammates, organise with colored labels, attach files, and wire up dependencies so a task can't start until its blocker is done — when the blocker lands, the next assignee is notified.

  • Comments with @mentions
  • Colored labels and file attachments
  • “Blocked by” dependencies with automatic hand-off
DS

@aria can you review the spacing once the PR is up?

2h ago

frontendbugp1
PDFlogin-spec.pdf · 240 KB
Blocked byDefine API contract
Views

See the work the way you think.

Read the same tasks as a drag-and-drop Kanban board or a compact list, narrow to just your own work with My Tasks, and open Project Insights for throughput and workload. The board updates live for everyone, from any source.

  • Kanban board and list view
  • My Tasks across every project
  • Project Insights & analytics
BoardListMy Tasks
Todo

Pricing copy

In Progress

Fix login

Done

Launch hero

Inbox

Caught up at a glance.

A single inbox gathers what concerns you: new assignments, comments and @mentions, AI confirmations to approve, workspace invites, and GitHub issues that need attention. The ones that need a decision are grouped as “needs action.”

  • Assignments, comments and mentions in one feed
  • AI confirm and invite items you can act on inline
  • A clear “needs action” section
You were assigned “Fix login button”
Confirm: move “Billing portal” to Done?Action
You were invited to the Beta Labs workspaceAction
GitHub Issues

Issues, mirrored and linked.

Issues from a linked repo are mirrored into the project so nothing is missed. A project lead or admin links an issue to a task with one action, and if a linked issue is closed while its task isn't done yet, Bundlle flags it for review.

  • Repo issues mirrored into the project
  • Lead or admin links an issue to a task
  • Mismatched closes are flagged, never silent
#42Dark mode flicker on load Linked to task
#47Add keyboard shortcutsLink
MCP

Your AI tools, on the board.

Every workspace exposes its own MCP server. Add its URL to Claude Code, Cursor or claude.ai, sign in with your Bundlle account, and your agent can read the board, create and move tasks, and comment — scoped to your role, with viewers read-only. The code it ships still flows through commit matching, so the card follows the work.

  • One URL per workspace, from Settings → Integrations
  • OAuth sign-in — no API keys to create or leak
  • Reads and writes land on the live board instantly
“Pick up my next task and move it to review”
my_tasks3 tasks assigned to you
move_taskFix login button → In Review
comment_on_taskPR #218 linked for review

Set up your workspace in minutes.

Create a workspace, add your first project, invite the team — all free to start, no card required.

Coming soonSee pricing