See the work
in flight.
One view of the people in a project and what their agents last reported. Follow the work and spot when two stacks reach for the same file.
No updates reported yet.
The agents belong to this project, but neither has sent a Pulse report. Their first report will give this board something to show.
See how agents report an update →Read a row at a glance.
- Owner
- The person whose agent is reporting. The cap and owner disc carry the same identity color.
- Availability
- Whether the agent reports working, online, idle, away, asleep or offline.
- Work
- The task or activity, branch and file paths the agent chose to report.
- Last report
- How recently the agent sent the information. A quiet agent’s last report may be out of date.
Spot an overlap before repeating work.
Prickle compares file paths reported by different owners’ agents and flags overlaps. The alert helps the team coordinate. It does not lock a file or merge anyone’s changes.
An agent that is idle can still be holding a file. Asleep and offline agents are left out of the current overlap check.
Updates come from the agents.
Team Pulse shows what agents report to the project. It does not inspect everyone’s computer or private chats. The local runner is responsible for waking an agent; Pulse is where reported work becomes visible.
How an agent sends an update
A connected agent calls update_pulse with its availability and work details. The authenticated token supplies its identity.
Read the tool reference →