Learned · source-linked · revertible
Stop rebuilding the same project context.
Skyflo keeps what a finished mission proved, links it to its source, and brings it back when the next mission needs it.
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.
Research sources, the decisions behind a launch, why the build is pinned. Each answer gets written down once, often somewhere the next agent does not look.
Skyflo gives AI agents persistent memory, stored on your Mac and tied to the mission and source that produced it. You can review, remove or erase what it learned.
▲ 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
Experienced teammates
- holds
- the context behind decisions
- fate
- context leaves with them
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 is personal, scoped to the work that produced it, and removable.
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
Every learned record retains the source needed to inspect where the context came from.
learned memory
The worker base image requires a compatible runtime.
mission local-042
Controlled by the user
Dismiss a suggestion, remove a memory, or erase it permanently. Learning itself can be turned off.
memory control
Remove context that is stale, irrelevant, or no longer wanted.
review action
Four steps from work to recall.
Nothing is kept without evidence. Drafts backed by your own words or by work that ran successfully are kept; anything weaker waits for you. Only what is kept can be recalled.
1write
Work finishes
Skyflo drafts what it taught
2write
Evidence decides
kept · or waits for you
3write
Memory retained
scoped · source-linked
4read
Later mission recalls
only when relevant
what is kept can be recalled by later missions ↺
Want to see the write path in detail? Follow the illustrative mission.
Open the illustrative missionA workflow that proves itself twice becomes a Skill.
A command sequence that works in one repository stays a memory there. When a second repository verifies it, Skyflo proposes a Skill, and an independent agent or you must approve it.
Skills are part of what makes Skyflo a HyperAgent. Every Skill, and every change to how Skyflo routes work, is listed under Improvements with who judged it.
How Skyflo improves how it improvesnpm run lint:ci then npm run test:ci
- verified
- repository one · procedure kept on evidence
- verified
- repository two · same commands, different words
- proposed
- by the agent that ran the second mission
- approved
- by an independent agent reaching the same content · or by you
- available
- / menu in that repository · one Revert removes it
Every record carries its sources.
Each record names the mission and files it came from. When later work disagrees, the new draft waits for you instead of replacing the old one.
After each finished turnA consolidation pass reads what the mission did and drafts what it taught, citing your words and the commands that ran. A draft whose only sources are tool output or repository files is quarantined: it is never offered as a one-click keep.
Checkout workloads run multi-arch; the delivery matrix is pinned.
example kept record · mission arm-042 · delivery/ci.yaml
Worker base images must satisfy glibc 2.35 or newer.
example kept 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.
inferred by mission pay-207 · waits in Needs attention
On your Mac, beside your work.
Personal memory sits on your linked Mac beside the workspaces it describes, and stays there.
Personal memory, on disk
Memory is stored on the same machine as your repositories and is not synced to Skyflo. A memory a mission recalls joins that mission's context, so it can be sent to the model provider the mission uses.
Stays on the Mac
A mission you move to Skyflo Cloud runs without your Mac's memory. Nothing in memory is synced to Skyflo, on any plan, team plans included.
What memory can and cannot do.
Including what it does not do. To see how a record is written, follow an illustrative mission.
What carries across missions?
Source-linked memory Skyflo learned from finished work, recalled when it is relevant to a later mission in the same scope, and Skills, which you call by name from the / menu. The Use memory in tasks switch decides whether any memory reaches a mission.
How does Skyflo decide what to keep?
The evidence decides. A draft backed by your own words or by a command the work ran successfully is kept when every admission condition holds. Anything inferred, conflicting, or with an unclear scope waits in Needs attention, and a draft whose only sources are tool output or repository files is never offered as a one-click keep.
Can I correct a memory?
Only before it is kept: you can edit a suggestion's wording in Needs attention, and the edit is screened like any other memory. Once learned wording is kept it cannot be edited. It stays fixed to its sources, so you remove or erase it instead.
Can I remove memory, or stop Skyflo learning?
Yes. Dismiss a suggestion, remove a memory, or erase it permanently. Erasing a learned memory takes it out of every view and every task, while the append-only activity log keeps its original entry. Turning off Learn automatically stops learning altogether.
What is a Skill?
A command sequence verified in two of your repositories, packaged so a later mission can follow it. It becomes a Skill only when you approve it, or when an independent agent on a different model or provider proposes the same Skill. You call it from the / menu in the one repository it belongs to, and one Revert removes it.
Can I add memories myself?
Yes, from the Memory page. Memories you add are saved and listed, but they are not given to tasks yet.
Does memory leave my Mac?
It is stored on your Mac and is not synced to Skyflo. When a mission recalls a memory, it becomes part of that mission's context, so it can be sent to the model provider of the lane the mission uses, along with the rest of the conversation. A mission in Skyflo Cloud does not take your Mac's memory with it.
Can an organization share one memory set?
No. Memory is personal to each person's Mac and is not synced to Skyflo, on every plan, team plans included.
Let the second mission start where the first stopped.
Memory, Skills, and Improvements are included on the Free plan and are stored on your Mac, whichever agents you run.