Walkie is a Craft 6 plugin. Craft 6 is still in beta, and so is Walkie (6.0.0-beta.1) — try it on staging first and use caution on production sites.
Craft 6 · Beta — use caution on production
Your content, live
Craft 6 tells your own browser tabs when you save. Walkie tells everyone else who's allowed to know: colleagues with the same entry open, and front ends showing a live blog, a scoreboard or a news feed. Laravel broadcasting underneath, Craft permissions on every channel.
Three lines on the front end
Load Laravel Echo as you normally would, then let Walkie wire the channels. The same helpers exist in Blade. Messages carry ids, so your page refetches what it shows through its own permission-checked request.
{# layout: after Laravel Echo is loaded #}
{{ walkie.script() }}
<script type="module">
addEventListener('walkie:ready', ({ detail: walkie }) => {
walkie.on({ id: {{ entry.id }} }, 'saved', () => refreshArticle());
walkie.onSection('news', 'saved', ({ id }) => prependTeaser(id));
walkie.onSection('news', 'removed', ({ id }) => dropTeaser(id));
});
</script>
{{-- Blade --}}
{{ $walkie->script() }}
Features
Broadcasting that knows what Craft knows: sites, sections, statuses and permissions.
Saves, deletes and status changes
Created, saved, restored and deleted entries and assets, plus entries going live or expiring when a post or expiry date passes — something Craft itself never announces.
Channels that respect permissions
Private channels are authorised with Craft's own element policies: viewEntries, viewPeerEntries, viewAssets, editSite. Unknown sites, drafts and revisions are refused.
Public channels, only for live content
Switch a section to public and guests hear about its live entries — ids only. Pending and disabled entries are never mentioned, not even by id.
Per site, after the commit
Every channel belongs to one site. A save is announced once per site after the database transaction commits, so a rolled-back save sends nothing.
- A save that propagates to three sites sends three messages
- Repeated saves in one request fold into one
Presence
Who else is looking at this entry, as a first name and a user id. Never an email address.
Built for other plugins
Walkie::send() broadcasts your own events on an element's channels to exactly the people who may view it. Twig, Blade, a small Echo client and a GraphQL query for headless front ends.
Frequently Asked Questions
The questions worth answering before you install it.
No. It is a native Craft 6 plugin built on Laravel broadcasting. Craft 6 is still in beta.
Use caution. Craft 6 and Walkie (6.0.0-beta.1) are both in beta, so expect changes between releases. Test on staging, keep backups, and move to production only once you're comfortable with the beta.
Yes, under the Craft License.
You need a WebSocket server browsers can reach: Laravel Reverb (free, self-hosted), Pusher, or a Pusher-protocol server such as Soketi. Walkie only uses Laravel's broadcasting API.
Core tells your own other control panel tabs, through the response. Walkie tells other editors and front ends through a WebSocket server, per site, with permission checks. It keeps core's guards and leaves core's messages alone.
Public channels only mention live entries of sections you made public. Private channels need Craft's view permissions for that element or section, in that site. Payloads never contain titles, fields or URLs.
Yes: a walkieChannels query gives headless front ends the public channel names for sections the schema can read, and the public connection details. Never the broadcaster's secret.
Craft CMS 6.0.0-beta.1 or later, PHP 8.5, Laravel 13 broadcasting.
Try it on staging today
Walkie is free. It's a Craft 6 beta plugin on a beta CMS — start on a development or staging site and use caution on production.