Check for work that needs attention
Heartbeat is the proactive system that evaluates relevant current context on a configured rhythm and stays quiet when there is nothing useful to surface.
Ghost can check the sources relevant to the day, filter for work that needs attention, and assemble a concise brief with meetings, open commitments, urgent messages, and practical next actions.
At the start of an Atlas launch day, Ghost surfaces the 10:00 review, the unfinished readiness brief promised last week, one customer email that needs a reply, and the blocked Jira item—then proposes the order in which to handle them.
This is one workflow across Ghost, not a bundle of disconnected products. Each feature owns a specific stage and keeps its own access boundary.
Heartbeat is the proactive system that evaluates relevant current context on a configured rhythm and stays quiet when there is nothing useful to surface.
Supported Calendar, Gmail, Slack, and Jira tools can provide current events, messages, and project state when they are connected and relevant to the request.
The Focus board shows active tasks, timing, blockers, and Epics. Meeting memory can add an earlier promise, while current task and source systems verify whether it is still open.
The handoff stays inspectable from source to result. Every stage names what it received, what changed, and what needs review.
The briefing resolves today’s events, timezones, and meeting identities, then identifies which meetings actually need preparation rather than copying the full schedule.
Ghost looks for relevant urgent Gmail or Slack work, distinguishes a request from noise, and keeps the source thread available. Connecting an account does not mean every message is continuously monitored.
Focus items, Epics, and relevant project state show what is due, in progress, blocked, or waiting on someone else. The brief should not mark missing source access as completion.
Relevant meeting memory can surface a promise or unresolved question from an earlier meeting and compare it with the current task state.
The output leads with what needs the user, why it matters today, and the next practical move. A reply can be drafted, a brief can be opened, or a task can be resumed as a separate action.
Heartbeat can surface the brief based on current context, while a scheduled AI task runs a defined brief at a chosen time. Those are related but different mechanisms.
Connected work still needs accurate sources, explicit destinations, and review where an action changes another person’s system.
It can include relevant meetings, preparation context, actionable email or Slack messages, open to-dos, blockers, and unfinished meeting commitments, with links back to the supporting source.
Not exactly. A scheduled task runs a defined brief at a chosen time. Heartbeat can evaluate current context and surface something when it is relevant. Either behavior needs the appropriate configuration.
No blanket monitoring is implied. The workflow uses supported connected sources that are relevant and available to the task, and it should avoid turning routine noise into the briefing.
Yes. It can point to an AI meeting prep brief or surface earlier decisions and open commitments for an upcoming Calendar event.
A useful proactive system should stay concise and can remain quiet when there is no material update, rather than manufacturing urgency to fill a template.
Bring the source, the intended result, and the boundaries that matter. Ghost is in private beta for macOS.
Request access