All packs
Memory
Agents on all your machines share what they learn through your own private memory repo.

How it works
- Agent on your Mac
- Your memory repo
- Agent on a devbox
Workflows
Shared memory
On with the packNeeds GitHubAgents on every machine read and write one private memory repo, which syncs every five minutes.
What it costs
You need a small private GitHub repo. It syncs every five minutes.
Know before you turn it on
Agents write notes about you and your work into the memory repo. Keep it private.
Settings2 settings that your agent asks about
memory.repoWhich private GitHub repo holds your agent memory, such as you/agent-notes?Default: from your context repomemory.subtreeWhich folder of the memory repo holds the memory? Leave it empty when the memory is the whole repo.Default: from your context repo
Add Memory to your Fleet
Paste this prompt into a T3 Code thread on a machine that runs Fleet.
Your install prompt
Add this Fleet pack to my setup with me: Memory. Fleet already runs on this machine. Ask me each choice with your question tool, and run every command yourself. 1. Run `fleet update`, so this machine has the newest engine and packs. Then run `fleet packs`, and leave out each pack that is already on. 2. Read the setup note of each pack. Ask me what it asks, and collect the flags that it names. Where a note names "the setup command" or "the command in step 9", use the `fleet packs` command of this prompt. Do not run a step that a note puts after that command yet. - Memory: ~/.local/share/fleet/engine/packs/memory/SETUP.md 3. Turn the packs on with one command, and add the flags that the notes name: fleet packs --add memory 4. Do the steps that each note puts after the command. 5. Run `fleet doctor`, and explain each line. Do each `To do:` line with me, and say what a sign-in is for before it opens. 6. My other machines take the change at their next `fleet update`. To give it to one now, run `fleet update` there.