Skip to main content

Workspace Memory

Give the next task a better start.

Keep useful decisions and their sources close to the work.

Reuse context from earlier work. Review its source, correct mistakes, and retire outdated information.

Join the waitlistSee the memory record

Give useful lessons a place to stay.

When a task ends, its decisions can still help the next one. Shared context may reduce repeated explanation and mistakes, especially when the source remains available for review.

Example — fictional team and data. Not a live run or customer result.

Workspace Memory

Illustrative example

  1. A person writes the rule

    Human ruleCurrent
    “Migrations run by hand after deploy; never assume a merge applied them”

    Written by · Maya Chen

    Source · Workspace brief · Deployment rules

  2. The next agent recalls it

    Claude Code

    Launching on · AES-203

    Ship the carrier-rate refresh · 2 memories available

    1. Decision
      Item 1

      Release owners run migrations after each production deploy.

      MEM-041 · Accepted run · AES-184

    2. Constraint
      Item 2

      Migrations run after deploy.

      MEM-042 · Workspace brief · Deployment rules

  3. One correction updates what follows

    Corrected by · Maya Chen

    ConstraintSuperseded

    Migrations run after deploy.

    MEM-042

    ConstraintCurrent

    Migrations run by hand after deploy; never assume a merge applied them

    MEM-044 · Correction · Maya Chen

    Next task · AES-204
    Serves MEM-044 · Item 1

See where a remembered fact came from.

Check the source and its relevance before relying on a remembered decision. A citation helps with review; it does not make a claim infallible.

  • Sources you can check

    Open the supporting work or human guidance behind a remembered fact.

  • Useful work can inform the next task

    Keep lessons from reviewed work available so the next person or agent has a more useful starting point.

  • See what changed

    Review corrections and earlier decisions when a remembered fact no longer fits the work.

Example — fictional team and data. Not a live run or customer result.

Claim evidence

Cited

A migration is not applied by a merge.

Accepted run · AES-184Accepted work

Open the source and review the full decision

Your team decides what remains useful.

Review suggested memories, correct mistakes, and stop outdated information from being used. Keep human judgment in the loop.

  • Review the supporting evidence

    Check where a suggested memory came from and whether the source is relevant and reliable.

  • The queue shows what needs attention

    Find suggested memories, conflicting information, and items that may need an update.

  • A person keeps the last word

    Correct or retire information that should no longer guide future work.

Example — fictional team and data. Not a live run or customer result.

Memory review

Needs review

Deploys always run migrations automatically.

Superseded workspace briefAging

Review the source, then correct or retire this memory

Questions about shared memory.

Shared context is useful when people can check it, control access, and correct mistakes.

What if an agent teaches itself something wrong?

Treat suggested memories as information to review. Your team can inspect the source, correct a mistake, or retire a memory. Important results still need human review.

Will another organization see our memory?

Memory uses organization and workspace access boundaries. Review who has access and which sources your team shares.

What happens when the source changes?

Changed or outdated information may need review or retirement. Check the source when a remembered fact affects an important decision.

An early usage snapshot, with limits.

27 memories delivered before launch
Recorded deliveries of remembered context before this launch work began. The count has grown since. This baseline does not measure accuracy or time saved.
2 recorded points of use
As of September 4, 2026, remembered context had been delivered in Drop and external agent sessions. This does not show adoption across all agent workflows.
16,958 seconds to first use
About 4 hours 43 minutes on average in this early snapshot. This is elapsed time until first use, not response speed or a performance target.

Aestus internal production records · baseline measured 2026-09-01, re-measured 2026-09-04 · not a customer benchmark

Won't shared memory become shared misinformation?

Shared context can be wrong or outdated. Sources and review controls help your team check it and make corrections; they do not replace judgment about the result.

Keep a useful lesson for the next task.

Talk to us