MemoryLearned · source-linked · revertible
How Skyflo learns between missions.
Skyflo keeps what a finished mission's evidence supports, asks you about the rest, and can turn a workflow proven in two repositories into a Skill. 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 keep, correct, dismiss, or remove 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
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
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. When a mission completes, Skyflo drafts what it taught with its sources attached. Drafts backed by your own words or by work that ran successfully are kept; anything weaker waits for you, and only what is kept can be retrieved later.
1write
Mission completes
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
recall loops back into every new mission ↺
Want to see the write path in detail? Follow the illustrative mission.
Open the illustrative missionA workflow that proves itself twice becomes a Skill.
One repository running its gate is that repository's habit, and it stays a memory there. When a second repository verifies the same commands, Skyflo proposes a Skill. The agent that proposed it cannot approve it: another agent has to arrive at the same Skill, or you keep it yourself.
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 another agent reaching the same content · or by you
- available
- / menu in that repository · one Revert removes it
Every record carries its sources.
A record names the mission and the files it came from, so you can check it. When later work contradicts a kept record, both sources are shown and the record waits for you instead of being quietly overwritten.
After every completed missionA 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 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?+
Source-linked memory Skyflo learned from completed missions, and the Skills it has promoted, retrieved when they are relevant to a later mission in the same scope. Use memory in tasks decides whether any of it reaches a mission.
02How 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.
03Can I correct a memory?+
You can edit a suggestion's wording before you keep it, and the edit is screened like any other memory. Learned wording that is already in force stays fixed to its sources, so you remove it rather than rewrite it.
04Can 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.
05What is a Skill?+
A workflow that succeeded in two of your repositories, packaged so a later mission can follow it. It becomes a Skill only when another agent or you approve it. You call it from the / menu in the repository it belongs to, and one Revert removes it.
06Can I add memories myself?+
Yes, from the Memory page. Memories you add are saved and listed, but they are not given to tasks yet.
07Can 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.
Memory, Skills, and Improvements ship in the free build and run on your own machine, with your own model keys.
Personal memory ships with Desktop. Organization-wide shared memory is Planned.