Live PlanningBeta

Plans don'tsink.

Live Planning (Beta) moves the plan your coding agent wrote out of one laptop and into HubBound: share it, edit and comment on it together in real time, revise it with your own agent, and approve it before anything runs.

The plan stayed here

Why does a plan on one laptop hold a team back?

A plan written in a coding agent's plan mode lives in one developer's session: nobody else can read it, change it or approve it before the agent starts writing code from it.

  • No sharing.

    The plan sits in a terminal on one machine. Teammates see it only if someone pastes it somewhere, and that copy is stale the moment it is sent.

  • No live edits.

    Corrections come back as chat messages, and one person retypes them into the plan. The people who know the system never touch the document.

  • No review before it runs.

    A wrong assumption in step two turns into code, a pull request and a revert. Nobody approved the plan because nobody could see it.

What if your plan could surface?

LivePlanningBeta

Now your plan goes live.

Illustrative sample

In short

What is Live Planning?

Live Planning is HubBound's collaborative workspace for implementation plans, in Beta: the plan your coding agent writes becomes a shared Markdown document that your team edits live, comments on, revises with their own agents and approves at a review checkpoint before it is executed.

BetaLive Planning is in Beta. An organization turns it on in its settings, and an org admin chooses which coding agents can run work and can cap the monthly agent spend.

  • One shared Markdown plan

    Your agent creates the plan in HubBound. You share it with people or teams as Owner, Editor or Viewer, and everyone works on the same document with live presence and cursors.

  • Your own coding agent

    From the plan, each member launches the coding agent they already use, on their own device, to edit the plan, resolve or answer a comment, or execute the approved plan.

  • Review before it runs

    Checkpoints freeze a version of the plan. Reviewers approve it or request changes with a reason, and the history keeps every checkpoint so you can compare and restore.

How does a team work on one plan in Live Planning?

In Live Planning, every plan opens in one workspace: the Markdown document in the middle, its outline on the left and the plan tools on the right, so sharing, live editing, comments, your agent and review all happen on the plan itself.

Chapter 7 of 7

Illustrative sample

Which coding agents work with Live Planning?

Live Planning works with Claude Code, Codex, Cursor, GitHub Copilot and Antigravity, and with any other MCP client that supports remote HTTP servers with OAuth, through the hubbound-live-planning MCP server.

  • Your agent, on your device

    A run launches the coding agent already installed on your machine, through the HubBound daemon, in a terminal or an editor session. Private run details stay visible only to you.

  • Another client? Plug in the MCP

    Connect any MCP client that supports remote HTTP servers with OAuth to the hubbound-live-planning server. It asks you to authorize HubBound the first time.

  • Admins set the limits

    An org admin chooses which code providers can run agent work, and can cap the monthly agent spend for the organization.

How does a plan go from draft to execution?

A Live Planning plan moves through five statuses, from Work in progress to Approved, and only an approved plan can be executed by an agent.

  1. Work in progress

    Draft it

    Your agent creates the plan through the hubbound-live-planning MCP server. The team edits and comments on the live draft.

  2. Ready to review

    Mark a checkpoint ready

    A checkpoint freezes the version under review, so later edits never change what reviewers decide on.

  3. Waiting for review

    Request reviewers

    Reviewers read that checkpoint and approve it, or request changes with a reason.

  4. Changes requested

    Revise

    The team, or an agent, updates the plan and sends a new checkpoint to review.

  5. Approved

    Approve, then execute

    Once the plan is approved, launch Execute plan to carry it out in your workspace.

When the team agrees, approve it. And ship it.

Execute plan

Good to know

What else should you know about Live Planning?

Short answers about Live Planning's Beta status, how agents work on a plan, and who can see it.

Is Live Planning generally available?

No. Live Planning is in Beta. An organization turns it on in its own settings, and the feature may change while it is in Beta.

Does HubBound run the AI for me?

No. Live Planning launches the coding agent you already use, on a device you authorized, and that agent reads and edits the plan in HubBound. An org admin chooses which providers are allowed.

Can people edit while an agent is working on the plan?

While an agent edits the whole document, people can still comment and react. When it edits one fragment, the rest of the plan stays editable.

Who can see a plan?

Only the people and teams the plan is shared with, as Owner, Editor or Viewer. Mentioning someone who cannot read the plan yet sends an access request that the plan owner approves.

Can I take the plan out of HubBound?

Yes. Download Markdown exports the plan as a Markdown file at any time.

Plans don't sink anymore.

LivePlanningBeta

Your team. Your agents. One live plan.

Open beta for HubBound users