v1.9.0 — No more guessing
This release is about the things you couldn't see: who a workflow is shared with, how long an agent will wait for you, which specialist picks up your request, and whether anyone can find what you published.
Workflows you can actually share
Choose who a workflow reaches when you create it — private, a project, your organization, or public — and change it later from the workflow's own page. Every card and row now carries a visibility badge, and you can filter the list down to a single level.
Re-scoping or archiving is now owner-only, so a workflow you shared to run can't be re-pointed by someone who was only meant to run it.
The right specialist, every time
We fixed a routing fault that could hand your request to a wildly unsuited agent — a fortune-teller or a cat persona editing code — and could pick a different one each time you asked the same thing.
The cause: owning a vaguely related tool counted as much as genuinely knowing the subject. It now counts for what it's worth. This sat underneath inline edit and ordinary chat alike, so routing is sharper across the board, and consistent run to run.
When an agent asks you something
- The deadline is visible — a rail drains for the full window, with a countdown that shifts from calm to urgent.
- Every action states its consequence, including the one nobody discovers: what happens if you do nothing.
- Dismissing is not stopping. It lets the agent carry on without your answer; only the stop control ends the turn. Running out the clock does the same thing as dismissing — and now the form says so.
- Your answer stays on screen after you send it, instead of the form vanishing without a record.
Published work that can be found
Community posts are now discoverable across the entire library, not just the first slice of it. A post's "last updated" reflects a real content edit rather than a visit, and renamed or moved posts forward to their new address instead of dead-ending.
The full release note lives in the in-app What's New drawer.
Keep the feedback coming in Feature Requests — the input form rework came straight from it.