Every Odoo user lives inside the chatter. It is where messages, log notes, activities, tracked field changes, and attachments accumulate on every record — leads, sales orders, invoices, tasks, tickets. Yet the native chatter offers almost no control over how that stream is presented. On a busy record the log fills with hundreds of mail.message rows, activity reminders get buried between audit entries, and the fixed layout wastes horizontal space on wide monitors while cramping the form on narrow ones. Teams that read and write to the chatter dozens of times a day feel this friction constantly, and Odoo core gives them no settings to relieve it.

This build-to-order module extends the chatter to add the display and layout options that native Odoo omits. We build a configurable OWL component that wraps the standard mail.thread chatter, so you keep full compatibility with messaging, activities, and followers while gaining controls such as docking the panel to the side of the form versus below it, adjustable width and message density, collapsing the composer until it is needed, and filtering the feed by type (messages only, log notes only, tracked changes only, or activities only). Because it is layered on top of the existing mail framework rather than replacing it, everything that already writes to the chatter — automated actions, message_post() calls, and field tracking declared with tracking=True and @api.depends computes — keeps working untouched.

Technically, the module ships as a proper addon with its own __manifest__.py declaring a dependency on mail. The front end is delivered through the assets bundle: an OWL component and QWeb templates that patch or extend the core chatter without forking it, plus SCSS for the layout modes. Preferences are persisted per user via res.users fields (or a lightweight settings model) so each person's chosen layout follows them across sessions, and any admin-level defaults are exposed through ir.config_parameter or Settings. Access is governed the Odoo way through ir.model.access.csv and, where preferences are record-scoped, record rules — nothing bypasses your existing security model. We tune the exact behaviour to your data: threads with heavy tracking, portal-facing records, or multi-company setups each get validated against real screens.

Delivery is build-to-order, not an instant download. After a short scoping call we confirm the exact layout modes, filters, and defaults you want, pin the target Odoo edition (Community or Enterprise) and version (17.0, 18.0, or 19.0), then build and validate the module on a staging copy of your database before installing to production. Typical delivery is 2–4 weeks from confirmed scope, depending on how many layout variants and edge cases we harden against. Pricing starts from $249 (indicative, single-company base scope); additional layout modes, portal/website chatter support, multi-company theming, and deeper per-team preference logic increase the quoted scope.