Parallel timeline
See human focus and every active agent lane on the same clock. Spot review windows, idle gaps, and overlapping work.
Pulse Stack brings human focus, agent runtime, waiting, overlap, projects, tasks, sessions, and files into one trustworthy timeline.
The missing layer
While you review one change, Codex can implement another and a second agent can investigate a failure. Sequential timers flatten that into a misleading total.
Pulse Stack preserves each lane, then shows wall time, agent-minutes, waiting, and human-agent overlap without pretending parallel work happened sequentially.
One workday, correctly modeled
Navigate the hierarchy people actually use: Agent → Project → Task or Session → Files.
See human focus and every active agent lane on the same clock. Spot review windows, idle gaps, and overlapping work.
Keep tasks, sessions, real Git branches, and projects distinct even when their names overlap.
Review primary and touched files from supported tool activity—not guesses from terminal output.
Understand when focus, agent runtime, waiting, and supervision happened across the day.
Create revocable project and period reports. Additional name-hiding controls remain a beta launch gate.
Three steps
Generate a private API key for your workstation.
The native installer configures launchd, systemd, or Windows startup automatically.
Your projects and workstreams appear as privacy-safe activity arrives.
Privacy is architecture
Pulse Stack stores time and activity metadata needed to explain a work session. Unknown and sensitive payload fields are rejected or redacted at ingest.
Read the privacy model →Native onboarding
Release artifacts share the same privacy and configuration contract, with automatic background registration on each platform.
Install Pulse StackFounder beta
Beta access is free during the initial cohort. Planned Pro pricing is $6 monthly or $59 yearly, with a $29 first-year founder offer after billing launches.
Questions, answered
No. Waka-compatible editor activity is preserved, but Pulse Stack adds explicit agent sessions, waiting, concurrency, and human-agent overlap.
No. The collector extracts supported activity metadata and intentionally excludes prompts, replies, source contents, transcripts, full tool output, and patch contents.
Codex tracking is live. The data model and UI already support provider comparison; the dedicated Claude Code collector is the next integration block.
Yes. Existing Waka-compatible heartbeats and human editor time continue to work alongside agent activity.