AI workflow memory. Keep what worked.
The useful part is not always the finished file. Sometimes it is the method that got you there. Save the steps, find them for a relevant task, and update them when the work changes.
Reusable procedures · Searchable steps · Private beta for Mac
Atlas review report export
- Method
- Read the sources, create the report, export, then inspect the result.
- Useful next time
- The steps and checks that worked in the reviewed environment.
- Still required
- Check the current brief, tools, and output before reusing the method.
What is AI workflow memory?
AI workflow memory stores the method for a task, not just its final answer. In Ghost, a procedure can contain ordered steps, trigger keywords, related tools, status, and failure history. Ghost can search those records for a relevant request, then check the retrieved guidance against the current instructions and tools.
Keep the method, not just the result.
A successful Atlas report leaves more than a finished file. Ghost can save a reusable procedure, retrieve it for a relevant task, and update it when the method changes.
Find out which steps actually worked.
Inspect the report and its export before treating the method as reusable. Keep the useful sequence and the important checks, rather than copying every exploratory attempt.
Give the procedure a name and a scope.
ghost can store a title, ordered steps, trigger keywords, related tools, and working status. Notes and failure history explain the conditions that matter.
Atlas review report export
- Triggers
- Atlas report · review export
- Steps
- Read sources → create → export → inspect
- Status
- Working in the checked environment
- Caution
- Recheck layout after changes
Find the method when the work is similar.
For a relevant request, ghost can search stored workflow titles, steps, and trigger keywords. A returned procedure is guidance; current instructions and available tools still take priority.
Prepare the next Atlas review report.
- Search
- Retrieve the relevant saved procedure
- Check
- Current brief, sources, tools, and output format
- Use
- Adapt the method to this task
Change the record when the method changes.
If an export step stops working, record the failure and mark the procedure broken or deprecated. After checking a repair, update the steps and status—or remove an obsolete record.
- Failure history
- What failed, under which conditions
- Repair
- Revised steps with the result checked
- State
- Working, broken, or deprecated
A broken procedure can still be retrieved with its status. It should not be followed as if nothing changed.
Illustrative saved procedure, not model training. Retrieval is selective rather than guaranteed. A saved status or verification date is context to check, not proof that the procedure will work in a new environment.
Keep the procedure separate from the source material.
A research note holds the evidence. A presentation holds the explanation. Workflow memory holds the method: which steps to take, which tools matter, and what to check before calling the work finished.
This is one form of procedural memory for an AI assistant. Instead of relying on a long chat to preserve the useful sequence, Ghost can save a named procedure with steps and trigger keywords that help it be found later.
Keep the underlying material in Notes. Keep preferences and broader work history in Memory. A workflow record has a narrower job: describe how to approach a repeatable task.
- Source note
- The facts, evidence, draft, and open questions.
- Workflow record
- The sequence, relevant tools, and checks.
- General memory
- Useful preferences and saved work history.
- Finished artifact
- The actual output you still need to inspect.
Save the useful steps, including the checks.
A reusable workflow needs more than “make the report again.” Give it a descriptive title, the ordered steps, and trigger keywords that identify when it is relevant. Optional notes and related tools add the conditions that make the method useful.
For an Atlas review report, the method might begin with reading the current brief, move through creation and export, and end by inspecting the rendered output. A method is stronger when it records how to check the result, not just which tool to call.
That same distinction matters for research and presentations: preserve the verification step. An earlier successful artifact is not proof that new sources, changed tools, or a different output format will behave identically.
A method with enough detail to reuse.
- Title
- Atlas review report export
- Triggers
- Atlas report, review export
- Steps
- Read sources → create → export → inspect
- Notes
- Review the layout after content or format changes.
Search for a relevant method. Check it before use.
Agent workflow memory is useful when the right procedure can be found for the current request. Ghost can search stored titles, steps, and trigger keywords, with record status and freshness affecting which matches are returned.
Retrieval is selective. It is not a promise that every relevant procedure is always loaded into every conversation. A new request can need a different query, more context, or a method that has not been saved yet.
Treat the returned steps as guidance. Your current request and the currently available tools take priority. A saved verification date is helpful context, but it does not certify that the procedure still works today.
If the work should run later, use Scheduled Tasks for the timing and a complete standalone brief. Workflow memory is not itself a scheduler, and a future run should not depend on unstated context.
For a job with dependent steps, task orchestration coordinates execution. A saved procedure describes the method; a workflow run tracks the work happening now.
- Find
- Use the task and relevant trigger terms to retrieve a procedure.
- Check
- Compare the saved steps with the current brief and tools.
- Adapt
- Apply only the parts that fit the present work.
- Verify
- Inspect the actual result, including limitations.
Remember the failure without trusting a stale fix.
A method can become outdated. Ghost’s workflow records support working, broken, and deprecated states, along with failure history. Those fields let a procedure carry the warning that a once-useful step no longer works as expected.
Search can still return broken or deprecated procedures with their warnings. Check that status before using a method, and keep a known failure visible instead of treating an old result as current guidance.
After checking a repair, update the steps and status. Remove a record when it is no longer useful. This is maintainable stored guidance—not a claim that Ghost retrains its underlying models, automatically learns from every task, or can never repeat a mistake.
- Working
- A saved method that was useful in its checked context.
- Broken
- A known problem needs attention before reuse.
- Deprecated
- The method is outdated or superseded.
- Failure history
- What went wrong and what needs to be reconsidered.
Product details
Workflow memory, at a glance.
Supported work, useful outputs, and what to check before you start.
- Saved procedure
- A named workflow can keep steps, trigger keywords, related tools, notes, and the date it was last verified.
- Maintenance
- Search, revise, or delete a procedure. Mark it working, broken, or deprecated, and retain failure notes so the next attempt has context.
- Reuse
- A retrieved workflow is guidance to inspect for the current task. Saving a procedure is not model training or a guarantee that every future request will load it.
One assistant. Connected work.
Ghost is a personal AI assistant for Mac. Meetings, Notes, To-dos, Memory, and Research are connected capabilities of the same product, with records you can bring into the next task.
Research can produce a source-linked note, a presentation can explain the result, and workflow memory can preserve the checked method for producing it. General memory supplies relevant work context; a scheduled task controls when a later brief runs.
Questions about workflow memory.
How is workflow memory different from personal memory?
Personal memory covers relevant preferences and saved work history. Workflow memory is narrower: a named procedure with steps, trigger keywords, status, and optional notes about tools or failures. See Ghost’s Memory feature for the broader context.
Does Ghost train itself when I save a workflow?
No. Workflow memory saves reusable procedures that can be retrieved later. It does not retrain the underlying model.
Does every task automatically become a saved workflow?
No such guarantee is made. Ghost has explicit tools to create, search, update, and remove workflow records. Tool success or failure observations are not the same as a complete reusable procedure.
Will the right workflow always load automatically?
No. Ghost can search for relevant stored procedures, but retrieval is selective and bounded. Current instructions and available tools still take priority over any returned record.
Can I update or remove a stored procedure?
Yes. Ghost can revise a workflow’s steps, trigger keywords, notes, status, and failure history, or delete the record when it is no longer useful.
What happens to a broken or outdated workflow?
It can be marked broken or deprecated. Those states lower its retrieval score but do not guarantee it will never be returned. Its warning and failure history should be checked before following the steps.
Can I use a workflow for recurring work?
A stored method can inform a relevant task when retrieved. Use Scheduled Tasks to define when work runs, and give that schedule a complete brief. Do not rely on a promise that every future run loads every workflow record.
Keep a useful method ready to revisit.
Save the steps, keep their limits visible, and check them against the next task. Workflow memory is part of the same Ghost. Private beta for Mac.
Request access