What's new in flower, written as outcomes. https://useflower.dev/growing 2026-11-12T00:00:00Z flowerhttps://useflower.dev/ https://useflower.dev/growing#a-dashboard-across-your-projects 2026-11-12T00:00:00Z

The app opens on a dashboard that reads across all your projects and shows what is happening now, what is running and what is ready to ship.

<ul> <li>Anything stuck or failing is listed once, worst first, with a link to the place where you fix it.</li> <li>It shows what happened since you last looked. That mark is kept for you, not for the device, so reading on your phone clears it on your laptop too.</li> </ul> https://useflower.dev/growing#ship-and-deploy-from-the-app 2026-11-12T00:00:00Z

A project's page in the app has Ship and Deploy buttons, and the app can ask for your passkey before either one runs.

<ul> <li>The buttons run the ship or the deploy on your own flower.</li> <li>Asking for a passkey first is on by default. A team’s owners and admins can switch it on or off for each project, with a default for the whole team.</li> </ul> https://useflower.dev/growing#mark-yourself-away 2026-11-11T00:00:00Z

Tell flower you're away until a set time, and it stops asking you to confirm things in your session until you're back.

<ul> <li>You can also let the project’s lead agent answer ordinary decisions for you while you’re away. That is off unless you turn it on.</li> </ul> https://useflower.dev/growing#a-brief-page-that-shows-where-it-is 2026-11-10T00:00:00Z

Each brief's page in flower's web UI shows where the brief is on its way to live, what is happening now, what it waits on and what comes next.

<ul> <li>A table lists each round of building and review.</li> </ul> https://useflower.dev/growing#one-quota-pool-across-your-accounts 2026-11-10T00:00:00Z

flower's web UI shows one pooled quota for each model provider across all your accounts, with a chart over time and a forecast that marks each expected reset.

<ul> <li>When an account is nearly used up, new work moves to the account whose weekly limit resets first. You can change that order.</li> </ul> https://useflower.dev/growing#work-with-a-session-from-the-app 2026-11-10T00:00:00Z

Start a session from a project's page in the app, read its conversation as it works, and send it a message or interrupt it.

<ul> <li>The conversation shows each turn, the tools it called with their results, and the briefs and decisions it touched.</li> <li>When it asks for permission or has a question, a card appears in the conversation and under Needs you. Allow once, allow for the session, edit or deny.</li> <li>Paste, drop or attach screenshots and PDFs, and they arrive with your message.</li> </ul> https://useflower.dev/growing#a-status-line-and-a-panel-for-claude-code 2026-11-09T00:00:00Z

A flower status line in Claude Code shows the project and branch, how full the session's context is, its mail, and the decisions waiting for you.

<ul> <li>A panel lists your project’s agents, its builds, what is shipping and what is up next.</li> </ul> https://useflower.dev/growing#long-running-agents-that-sleep-and-wake 2026-11-09T00:00:00Z

Start a long-running agent from a project and a prompt, with no brief, and keep working with it over many turns in flower's web UI.

<ul> <li>Send it a correction while it works, queue your next message, or interrupt it without ending it.</li> <li>It sleeps after 20 minutes idle and wakes when it gets a message, with its conversation and work intact.</li> <li>Move the same conversation to a terminal and back, or take it to your laptop.</li> </ul> https://useflower.dev/growing#agents-ship-and-deploy-under-a-grant 2026-11-08T00:00:00Z

An agent that needs to ship, deploy or add a project asks for a grant. You approve it, and the agent acts only within it.

<ul> <li>The grant’s page shows what was asked for and what was approved.</li> <li>When an agent makes a change on your behalf, flower asks you, in the Claude Code session you last typed in, whether you told it to.</li> </ul> https://useflower.dev/growing#ships-and-deploys-on-its-own 2026-11-08T00:00:00Z

A project can now ship each change once it has landed and settled, and deploy as soon as it ships, including to Cloudflare Workers with its database migrations applied first.

<ul> <li>Set a project to ship on its own, and each landed change goes out once it has settled and its checks after landing stayed green. You can hold shipping or deploying for a project at any time.</li> <li>A deploy can follow each ship, so a landed change reaches the live site without a hand step.</li> <li>Cloudflare Workers is a deploy target. Pending database migrations are applied before the new version goes live, and a migration that fails stops the deploy.</li> </ul> https://useflower.dev/growing#standards-checks-on-every-build 2026-11-08T00:00:00Z

flower runs a project's standards checks on every build and every landed commit, shows which findings are new and which were fixed, and can hold a change when a check is set to block.

<ul> <li>Exempt a check on chosen paths of a project, with a reason and an expiry.</li> <li>Ask for a review pass over the open findings, or for a brief to fix a check that has a known fix.</li> </ul> https://useflower.dev/growing#the-app-opens-by-invite 2026-11-08T00:00:00Z

app.useflower.dev is live for invited teams. Pair it with your flower using a one-time code, and sign in with a password or a passkey.

<ul> <li>Each project has a page with its route, its health, what needs you, its agents, its briefs by stage and recent activity.</li> <li>Open decisions are listed under Needs you. Answer one in place, with its recommendation and the evidence behind it.</li> </ul> https://useflower.dev/growing#follow-a-change-until-its-live 2026-11-07T00:00:00Z

Ask flower to follow a brief, or a whole epic, and it reports back as the work lands, deploys and passes its checks on the live site.

<ul> <li>One request follows the work through every step and ends itself when the last one is done. You hear about a stuck or failing step along the way, without checking back.</li> <li>Each project can say how its live site is checked: an address that must answer, a page that must show, or a command to run. They run after a deploy, and you can run them at any time.</li> </ul> https://useflower.dev/growing#start-a-session-from-the-browser 2026-11-07T00:00:00Z

Start a Claude session on one brief from flower's web UI, read along as it works, and allow or deny each tool it asks to use, right there in the page.

<ul> <li>The session runs in its own throwaway workspace, and its work comes back on a branch of its own when it stops.</li> <li>Each request to use a tool waits for your answer and records who gave it. Only someone signed in can start, answer or stop a session.</li> </ul> https://useflower.dev/growing#steer-a-build-while-it-runs 2026-11-07T00:00:00Z

A correction you send to a running build now reaches it while it's still working, not only when it tries to finish.

<ul> <li>Change the work order mid-run and the agent building it picks up the change as it works, in Claude Code and in Pi.</li> <li>You’re told when the build has read it, and it can’t finish until it has.</li> </ul> https://useflower.dev/growing#a-terminal-in-the-browser 2026-11-04T00:00:00Z

Open the real terminal of a live agent session in flower's web UI, one click from its transcript, on a desktop or a phone.

<ul> <li>Watch without being able to type, or take control when you need to. It reconnects on its own if the connection drops.</li> <li>On a phone, a row of keys covers the ones a phone keyboard lacks, and a paste asks before it’s sent.</li> </ul> https://useflower.dev/growing#reviews-that-block-only-on-real-defects 2026-10-29T00:00:00Z

Reviewers from a different lab now send a change back only for a defect they can show is reachable, and stop after three rounds to ask for a ruling.

<ul> <li>A finding that blocks a change names where it is and how it’s reached. Style, hypotheticals and alternative designs become notes that don’t hold it up.</li> <li>After three failed rounds by default, the change waits for a ruling instead of going back for another fix, so a disagreement can’t loop forever.</li> </ul>