Recall earlier meeting commitments
AI meeting memory can retrieve the relevant decision, question, or promise from an earlier conversation without treating memory as the current source of truth.
Ghost can resolve the intended Calendar event, retrieve the relevant history, and prepare a focused brief with earlier decisions, unfinished commitments, current project state, and useful questions.
Thirty minutes before an Atlas renewal meeting, Ghost identifies the correct event, retrieves Maya’s earlier pricing question, finds the promised comparison task, and prepares a brief that shows what changed, what is still open, and what to ask next.
This is one workflow across Ghost, not a bundle of disconnected products. Each feature owns a specific stage and keeps its own access boundary.
AI meeting memory can retrieve the relevant decision, question, or promise from an earlier conversation without treating memory as the current source of truth.
Calendar, Gmail, Jira, Slack, and document tools can provide the current event and project evidence when those sources are connected and available to the task.
A configured Heartbeat can check for relevant upcoming work and bring the brief forward. The cadence is set by the user; the page does not promise an unconfigured alert.
The handoff stays inspectable from source to result. Every stage names what it received, what changed, and what needs review.
Ghost resolves the intended Calendar event, timezone, recurrence, attendees, and subject. Similar titles should not cause context from the wrong conversation to be mixed into the brief.
Relevant meeting notes, speaker context, and prior decisions establish what the group already discussed and what someone committed to do.
Recent email, project updates, documents, and Focus items show what changed after the last meeting. If a source is unavailable, Ghost should surface that limitation instead of treating missing access as proof that nothing happened.
Open action items and promises are separated from completed work. The brief can point to the source record and the current task status so the user knows which part is historical and which part is current.
The output stays concise: why the meeting exists, what changed, open work, talking points, and questions. It can be saved with the AI note taker when the user wants an editable source trail.
Heartbeat can surface the prepared context before the meeting. Afterward, the lifecycle continues through action-item extraction and meeting follow-up automation.
Connected work still needs accurate sources, explicit destinations, and review where an action changes another person’s system.
A useful brief can include the meeting purpose, attendees, earlier decisions, unfinished commitments, current project changes, talking points, and questions. Ghost keeps references to the sources used.
Ghost can retrieve a relevant earlier commitment from meeting memory and compare it with current task or project context. It should keep the original meeting available for verification.
A configured Heartbeat can surface the brief before the meeting on the rhythm the user chooses. Without that configuration, creating a brief does not imply a guaranteed alert or delivery channel.
No. The workflow focuses on relevant, authorized work context for the intended meeting. It does not imply blanket background research across private or public sources.
Calendar changes are separate operations and may notify attendees. Preparing the brief alone does not edit, move, or cancel an event.
Bring the source, the intended result, and the boundaries that matter. Ghost is in private beta for macOS.
Request access