Pulse turns AI-agent work into a work record you can trust — Claude Code, Codex, and other AI agents log the work as it happens via MCP. No timer, no manual entry required by default.

That record is growing from time into memory too: an optional Work memory (Lab) lets your team keep the decisions and learnings that come out of that work, not just the hours.

Start with Getting started if you're new; jump to Connect Pulse to your AI tools (MCP) if your account is already set up and you just need to wire your agent.

⚠️ Pulse is in early beta. Features and schemas may change, and no uptime or support SLA is currently offered. Release notes will flag breaking changes.

In this section

Start here

• 🚀 Getting started sign up, pick your mode, log your first entry.
• 🔌 Connect Pulse to your AI tools (MCP) per-tool setup for Claude Code, Codex, Gemini CLI, and others.
• 👥 Users & roles member, admin, and patterns for multiple clients or multiple AI accounts.
• 🔒 Privacy & data isolation what Pulse stores, who can see it, and what stays outside the system.

Tool-specific guides

• 🤖 Connect Pulse to Codex and ChatGPT Codex CLI, ChatGPT desktop, and ChatGPT web Work mode.
• ☁️ Claude Code “cloud” sessions what's different when Claude Code runs in the cloud, not locally.
• ⚡ Skill - /pulse-capture reconstruct and log time from your Claude Code session history.
• 👀 **Mod - /pulse-today** (new) notice unlogged work time and hand it to /pulse-capture, with a new /pulse-today

Reference — how agents, the app, and its managed services fit together; why Pulse exists and where it's headed.

System architecture

Pulse Vision - Agentic work memory

Work memory (Lab)