Updates

The Updates feed is your project's living timeline — what's happening across everything connected to the project, curated automatically so you can catch up at a glance.

How the feed works

Each row in the feed is one living update tracking one topic: a negotiation, a support ticket, an invoice, a discussion heading toward a decision. Avi titles the updates it curates by the kind of matter they track — "Sales: Acme — Enterprise", "Support: Globex — SSO login failures", "Feature: Panel state in URL", "Trip: Tokyo — March" — so the feed scans as a set of named workstreams, and everything about one matter (a deal from first call to signature, a feature from proposal to deploy) stays on one row no matter how many channels it spans. As new activity arrives, the update gains a new beat — a one-line headline of what just happened, with detail underneath. The newest beat is the update's current status; expand a row to see the full history. Timestamps show when things actually happened — when the email arrived or the message was sent — not when Avi processed them.

• New and Updated markers are personal — they track what you have and haven't seen. An update you've read resurfaces only when something material happens.
• The small channel icons on a row show where the activity came from (email, Slack, and so on). One update can span several channels — the same deal discussed over email and Slack stays one update.
• Updates linked to a task show the task's name; clicking it opens the task. When you complete a task, its update leaves the feed automatically. If closure news arrives afterward (a confirmation, a receipt), the update resurfaces once so you see the outcome, then retires again on its own — and quiet standalone updates retire after a month of no activity. Anything retired comes right back if the matter genuinely picks up again.
• The feed stays current on its own as activity arrives. On a touch device, you can also pull the feed down from the top to refresh it on demand.

Automatic curation

Avi curates the feed for every project by default — no setup. As messages arrive from your connected sources, Avi decides what's worth surfacing, groups related activity into one update per topic, and writes the timeline beats. Replies in the same thread stay together on one update, so a conversation is understood in context rather than message-by-message. Avi keeps the substance from everyone in your conversations — decisions, agreements, action items, key facts, open questions — whoever said them, you included, so you and Avi share the full picture of what your team is doing. It filters the noise — newsletters, bulk mail, and content-free chatter like reactions, acknowledgements, and off-topic banter — no matter who sends it. A message that @mentions you is always given full consideration — and so are your own messages: Avi reads each one alongside the conversation it's replying to, so a quick "approved", "ship it", or "yes, go ahead" from you lands as the decision it is, not dismissed as a throwaway.

Curation never creates or changes tasks. Tasks are yours; Avi only records information and can attach an update to a task you already created.

Some apps also publish their own digest updates straight into the feed — for example the X app's daily topic briefings. Those belong to the app that writes them: curation never merges, regroups, or rewrites a digest.

Grouping is automatic

Keeping related activity together is Avi's job, not yours. Avi continuously watches for duplicates — when it finds the same topic appearing as two updates, it folds them together (the merged update keeps both timelines) and learns from each repair so future activity lands in the right place.

Ask Avi about your feed

When you chat with Avi in a project, it already has your most recent updates in view — so you can ask "what happened today?" or "anything I missed on the Acme deal?" and get a straight answer without telling it to go look. For anything older or more specific, it pulls the full feed or opens a single update to read the whole timeline.