What's new in flower, written as what changed for you rather than how. Newest first. Follow along with the Atom feed.
A dashboard across your projects
Anything stuck or failing is listed once, worst first, with a link to the place where you fix it.
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.
Ship and deploy from the app
The buttons run the ship or the deploy on your own flower.
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.
Mark yourself away
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.
A brief's page shows where it is
A table lists each round of building and review.
One quota pool across your accounts
When an account is nearly used up, new work moves to the account whose weekly limit resets first. You can change that order.
Work with a session from the app
The conversation shows each turn, the tools it called with their results, and the briefs and decisions it touched.
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.
Paste, drop or attach screenshots and PDFs, and they arrive with your message.
A status line and a panel for Claude Code
A panel lists your project’s agents, its builds, what is shipping and what is up next.
Long-running agents that sleep and wake
Send it a correction while it works, queue your next message, or interrupt it without ending it.
It sleeps after 20 minutes idle and wakes when it gets a message, with its conversation and work intact.
Move the same conversation to a terminal and back, or take it to your laptop.
Agents ship and deploy under a grant you approve
The grant’s page shows what was asked for and what was approved.
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.
Ships and deploys on its own, Cloudflare Workers included
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.
A deploy can follow each ship, so a landed change reaches the live site without a hand step.
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.
Standards checks on every build
Exempt a check on chosen paths of a project, with a reason and an expiry.
Ask for a review pass over the open findings, or for a brief to fix a check that has a known fix.
The app opens, by invite
Each project has a page with its route, its health, what needs you, its agents, its briefs by stage and recent activity.
Open decisions are listed under Needs you. Answer one in place, with its recommendation and the evidence behind it.
Follow a change until it's live
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.
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.
Start a session from the browser
The session runs in its own throwaway workspace, and its work comes back on a branch of its own when it stops.
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.
Steer a build while it runs
Change the work order mid-run and the agent building it picks up the change as it works, in Claude Code and in Pi.
You’re told when the build has read it, and it can’t finish until it has.
A terminal in the browser
Watch without being able to type, or take control when you need to. It reconnects on its own if the connection drops.
On a phone, a row of keys covers the ones a phone keyboard lacks, and a paste asks before it’s sent.
Reviews that block only on real defects
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.
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.