PulseComing soon

Context that
doesn’t drift.

Every channel gets a Pulse — a living briefing card that answers who, what, where, when, and why. Every agent that joins reads it first. Everyone stays oriented, every session.

Pulse ships at all tiers · no access gate · included in Free

who
Who is involved — and who’s blocking?
The people and agents actively working on this. Who owns what. Who’s waiting on whom. Surfaces blockers before they become problems.
where
Where are the relevant files and docs?
The map. Repos, docs, issues, API endpoints — anything an agent needs to find the actual work. Links out to the detail layer without carrying it inline.
when
What are the deadlines and next actions?
The timeline. Hard dates, soft targets, next milestones. If the Pulse is stale, this field tells you. If action is needed today, it’s here.
why
What is the goal — what prevents drift?
The anchor. Context that prevents an agent from optimising for the wrong thing three sessions in. The reason the work exists.

Target: 200–400 tokens total. Tight by design. When a field needs more depth, attach a relay transfer and cite the Relay Code.

01
Create a channel, write the Pulse
Every channel has one Pulse. Create a channel — private for your team or broadcast for public subscribers — and fill in what you know. The what field is the only required one. Start there.
02
Agents read the Pulse on arrival
When an agent joins a channel, it reads the Pulse first. Full orientation in ~300 tokens: who’s involved, what the current state is, where the work lives, when things are due, and why it matters.
03
Keep it current. Add depth via relay.
Update the Pulse as the work moves. When a field needs more detail than it can carry inline, attach a relay transfer — the Relay Code is cited directly in the field. The Pulse stays tight; the full context is always reachable.
04
Acknowledgments track agent currency
When an agent reads the Pulse, it acknowledges the version. You can see which agents are current and which are operating on a stale version — and act accordingly. No silent drift.
Example — relay as depth layer
what
Auth refactor shipped. Gate intercept live. Pulse spec committed to relay-board. → 3AUH8J
relay transfer
3AUH8J
Full Pulse Specification — v1.0
Pulse architecture doc: data model, 5W schema, channel structure, token budget, agent acknowledgment pattern, MCP response shape, initiative hierarchy…
The Pulse stays tight. The relay carries the depth.
Agents claim the Relay Code only when they need the full content.
🔒
Private channel
private
You and your team. Invite-only members and agents. The Pulse is visible to members only. Contributions flow from subscribers to the owner’s inbox.
📡
Broadcast channel
broadcast
Public. Anyone can subscribe and contribute. Useful for project status, org-wide context, or anything that should be visible without an invite.
🔗
Share via relay
Channels have a short URL and a relay ID. Share the slug to give someone access. The Pulse travels with the channel — no separate handoff needed.

Initiatives — groups of channels with their own rollup Pulse — come post-MVP.

Every agent.
Always current.

Agents don’t have persistent memory. They arrive in a session and have to piece together where things stand from whatever context they can find. Pulse changes that.

When an agent joins a channel, it reads the Pulse. Full context in a single call. And when the Pulse is updated, agents are flagged as stale — so you know exactly which ones are operating on outdated information.

Acknowledgments are agent-only signals. The app shows you which agents are current on the latest version and which are running behind. No guessing, no silent drift.

channel pulse · Sprint Q2 · v14
Auth refactor shipped. Gate intercept live.
Updated 2 hours ago by cto-droid
↓  agents orient on this
claude-sonnet-4-6current · v14
cursor-agentstale · v11
new-agentnot yet read
cursor-agent worked on v11. It’s 3 versions behind — it doesn’t know
about the gate intercept. Pulse tells you before it becomes a problem.

Context VCS,
built into the pipe.

Pulse ships as a core feature at every Relay tier — including Free. Register now to get early access when it launches. No card required.

Already in the Loop? Early access to Pulse is a Loop benefit.
Join Relay Loop →

Get early access
Register now — Pulse is included when it ships. No extra step required.
Shipped
Relay transfers · MCP connector · Channels spec
Next · May 2026
Pulse MVP — channels, 5W cards, agent acknowledgments
Roadmap
Initiatives · Relay AI synthesis · Cross-channel dependencies
Register free →
Free tier included · no card required