Coordinate Lovable with Manager.

Lovable turns prompts into apps. Manager plans the work, hands it to Lovable over MCP, and tracks every feature through to done.

Why pair them?

MCP-native

Manager exposes your backlog over MCP, so Lovable can read tickets, pick up work, and report progress automatically.

Parallel features

Run several Lovable builds at once against one shared, prioritized backlog.

Spec, don't vibe

Every ticket carries acceptance criteria and wiki links, so Lovable builds to spec.

The workflow.

  1. Plan the app in Manager

    Break the idea into goals and tickets with clear acceptance criteria.

    Say to your agentManager: Interview me about my app idea and break it into goals and tasks with clear acceptance criteria.

  2. Connect Lovable over MCP

    Point Lovable at Manager's MCP server; it can now read and update the backlog.

  3. Hand off tickets

    Manager assigns prioritized tickets to Lovable with full context: specs, links, and wiki pages.

    Say to your agentManager: Assign the highest-priority tasks to Lovable and link each to its spec in the wiki.

  4. Build features in parallel

    Lovable builds each feature from its ticket; run several at once instead of screen by screen.

    Say to your agentManager: Claim the next unassigned task and build it to its acceptance criteria.

  5. Track progress & update the wiki

    As features ship, Manager updates status, logs decisions, and keeps docs current.

    Say to your agentManager: Summarize what Lovable shipped this week and update the relevant wiki pages.

  6. Review & ship

    Approve completed work in Manager, request changes, and ship, with a full build record.

    Say to your agentManager: List everything waiting for review and ask me what to approve and what to send back.

From idea to shipped app.

Every ticket, decision, and artifact lives in Manager. Open Manager and see exactly what Lovable built, what's in progress, and what's next.

Get early access