New features

Meetings that cannot find a deal

When Cedar cannot tell which company a meeting belongs to, the recording used to vanish , no event, no ping, nothing to fix later. It now saves the meeting unattributed and DMs you in Slack with a Find it button so you can put it on the right deal.

Calendar matching is a bit more forgiving when the recorder's clock is a few minutes off the invite, and a tool or vendor named in the transcript no longer steals the company.

Improvements

• Before Cedar drafts a follow-up, it re-checks your live inbox , if you already replied, or already have a draft, it will not write another
• Asking chat which companies brought up a topic now uses structured deal fields, so those questions stop dying on a broken search
• When a CRM deal first lands, Cedar also looks at the domains people on that deal actually email from, so a company domain that does not match real contact emails no longer mints a second conversation

Fixes

• Cedar no longer drafts a recap off a Salesforce or HubSpot sync, or off a calendar RSVP , those were being treated as a reason to write
• If a conversation is linked to two CRM deals, the inactive one can no longer overwrite fields. Only the active deal writes
• Org-level weekly reports post once again, not once per teammate
• Daily agenda and other document writes no longer fail because the agent sent an empty upload placeholder
• Custom agents (a sequencer, an orchestrator) that were silently skipped now actually run, so their style rules are in play

Behind the scenes

• Prompt cache now leads with the stable block so reusable context can actually hit cache , CRM updater, next-steps, strategist, and the email orchestrator
• Conversation lookup sends domain guidance once per run instead of repeating it on every call
• Debug recent-executions reports real per-run tool-call counts instead of the whole table's row count
• Gateway tags are sanitized so mixed-case user IDs no longer reject an orchestrator spawn
• The documents skill warns agents not to put user-editable review docs under thread paths , those saves fail in the editor
• Playbook documents now describe the dispatch order the orchestrator actually uses

  

Confidence Score: 4/5

The PR should not merge until the unsupported empty-upload fix claim is removed or the corresponding implementation is included.

Findings

1.  Unreleased Fix Is Announced <a href="h