Feature
Agent work should stream as live change rows
Hubbla shows proposed account updates, tasks, and memory changes as visible rows that can be reviewed with citations.
Visibility is the safety layer
When generated work is hidden behind a spinner, teams cannot tell what changed or why. Live rows make each candidate update inspectable before it becomes part of the customer record.
- Every important generated update is visible before apply.
- Reviewers can inspect the citation trail behind a proposal.
- Rejected changes remain explainable instead of silently disappearing.
FAQ
Live change rows FAQ
Are live change rows the same as an activity feed?
No. Live change rows represent proposed work before it is applied. Activity history records what has already happened.
Can a user reject a generated update?
Yes. Hubbla's product rule is that important agent writes go through candidate change, approval, and applied change.