New features

LinkedIn counterpart profile

Open a LinkedIn DM and the chat panel now shows who you are talking to , current role, the companies behind it, and their recent posts. You can refresh the card yourself, and posts update daily rather than weekly.

Cedar keeps a profile it has already fetched so the same person is not bought twice, and it will skip a paid view when credit is too low, rather than spending the last of the day's budget just to look.

Improvements

• Chat knows which agent you are in and which file you are reading, so answers stay on the work in front of you
• Files has a Deleted section from the search row, so a file you removed is findable again
• A table cell bound to a deal field is editable , change stage or a date in the cell and it writes back to the deal
• An HTML document in the Files tab renders as a page, not as raw markup

Fixes

• Connecting Krisp no longer fails on OAuth , Krisp identifies the whole origin, and Cedar now accepts that
• Relative times say "3h ago" instead of "Today" if you are west of UTC
• Leaving a search no longer leaves the list filtered after you go back
• Opening a file no longer keeps re-rendering the browser that reports it

Behind the scenes

• Zero's pixel-block mark is gone, with a precommit check so it cannot come back
• Channel chats get a stable artifact and address; the old ticket store for deferred approvals is gone
• Org admins can view a teammate's debug executions in their own org
• Staff-check call sites are scanned so new bespoke gates cannot land undocumented
• Meeting transcripts are authorized against the org before Cedar trusts a stored key
• Internal configuration docs now describe routing a custom Salesforce object to its own AOP

  

Greptile Summary

The PR appends the September 11 product update to the Week 37 changelog.

• Documents the LinkedIn counterpart profile and several product improvements, fixes, and internal changes.
• One Krisp OAuth entry appears to describe work that landed before this update’s release window.

Confidence Score: 4/5

The PR appears safe to merge after correcting the non-blocking release chronology for the Krisp OAuth entry.

The changelog is correctly structured and its other statements correspond to landed changes, but the Krisp OAuth bullet has no implementation change in the release window it claims to summarize.

Files Needing Attention: docs/changelogs/2026-W37.md

Important Files Changed

### Issue 1
docs/changelogs/2026-W37.md:104
**Krisp Fix Misdated**

This bullet attributes the Krisp OAuth fix to the September 11 update, but no Krisp implementation changed in the September 9,11 release window. The relevant OAuth driver and origin normalization changes landed on August