MemoryPersonal · source-linked · reviewable
How memory carries between missions.
Personal memory is scoped to the work that produced it, keeps its sources, and stays under your control. Organization-wide memory is Planned, and labeled that way everywhere it appears.
Simulated recall
The rollout stalled on a base image below glibc 2.35. The constraint was recorded, and worker base images are now pinned to distroless arm64 variants.
Click a query to drive the exampleEvery answer carries its sources
Where the answer usually ends up.
Why the build is pinned, who owns the keys, what broke last time. Each of these gets written down once, in a place that is not where the next person or the next agent will look.
Skyflo gives AI coding agents persistent memory that stays on your machine and remains tied to the mission and source that produced it. You can accept, dismiss, forget, or delete each record.
▲ recovered by: interrupting whoever remembers
Chat threads
- holds
- the decision and the debate
- fate
- scrolled away in a week
Closed pull requests
- holds
- what changed and how
- fate
- the why never made it in
Runbooks and wikis
- holds
- how it worked at write time
- fate
- stale the sprint after
Senior engineers
- holds
- the real integration map
- fate
- context leaves with them
The approach
A record is written by the mission that learned it, in the place the next mission already reads from.
What a memory record contains.
Every record that ships today is personal, scoped to the work that produced it, and removable. Organization-wide shared memory is Planned and stays labeled that way for the rest of this page.
Relevant to the current mission
Memory is retrieved against the current workspace and mission context instead of being loaded as one large archive.
workspace · repository scope
This constraint belongs to the registered checkout and mission that established it.
mission source
Source-linked by default
Accepted memory retains the source needed to inspect where the context came from.
accepted memory
The worker base image requires a compatible runtime.
mission local-042
Controlled by the user
Current controls include dismiss, forget, and hard delete paths for personal memory.
memory control
Remove context that is stale, irrelevant, or no longer wanted.
review action
Four steps from work to recall.
Nothing is written automatically. A mission proposes a candidate with its source attached, you accept or dismiss it, and only what you accepted is available to be retrieved later.
1write
Candidate forms
context stays source-linked
2write
User reviews
accept · dismiss · forget
3write
Memory retained
scoped personal context
4read
Later mission recalls
only when relevant
recall loops back into every new mission ↺
Want to see the write path in detail? Follow the illustrative mission.
Open the illustrative missionEvery record carries its sources.
A record names the mission and the files it came from, so you can check it. When later work contradicts an accepted record, both sources are shown and the record waits for you instead of being quietly overwritten.
DreamerPreviewReviews completed work while the machine is idle, finds records that repeat or contradict each other, and proposes a consolidated one with its sources attached. Nothing it proposes is kept until you accept it.
Checkout workloads run multi-arch; the delivery matrix is pinned.
example accepted record · mission arm-042 · delivery/ci.yaml
Worker base images must satisfy glibc 2.35 or newer.
example accepted record · mission arm-042 · incident-2041
Staging deploys need release-captain approval.
a later mission recorded the opposite · shown with both sources
payments-v2 supersedes payments-v1 for new integrations.
proposed by mission pay-207 · waiting on you to accept or dismiss
On your disk today, shared later.
Personal memory sits on your linked Mac next to the repositories it describes. Organization-wide shared memory is a Planned team capability and is not current behavior.
Personal memory, on disk
Memory lives on the same machine as your repositories and your execution. Model calls go only to the providers you configure.
Shared knowledge, governed
Architecture, ownership, and outcome records for a whole organization, with permissions, a promotion review step, and audit history.
Questions
What memory can and cannot do.
Including the parts that are not shipped yet. To see how a record is written, follow an illustrative mission.
01What carries across missions?+
Accepted, source-linked personal memory can be retrieved when it is relevant to a later mission.
02Can I remove memory?+
Yes. Current memory controls include dismiss, forget, and hard delete paths.
03Can I correct a memory card inline?+
Correctable is Preview. The service contract exists, but the current Desktop surface does not expose the edit-then-accept action.
04Can an organization share one memory set?+
Organization-wide shared knowledge is Planned and is not presented as current behavior.
Skyflo Desktop
Let the second mission start where the first stopped.
Personal memory ships in the free build and runs on your own machine, with your own model keys.
Personal memory ships with Desktop. Organization-wide shared memory is Planned.