Fleet a side project atPostHog
All packs

Context library

Agents find your plans, research, decisions and saved threads in a private notes repo, and you save new ones with one command.

Add to your Fleet

How it works

  1. Your prompt
  2. Your notes repo
  3. Links to the notes it names

Workflows

  • Context library

    Off until you turn it onNeeds GitHub

    A prompt about a topic of your private notes repo gets links to its documents, fleet context searches and saves notes, and every machine pulls the repo every five minutes.

What it costs

You need a small private GitHub repo of Markdown notes. It syncs every five minutes, and saving a link runs one short agent.

Know before you turn it on

Agents read the library on every prompt, and saving a link writes a note from other people's text into it. Keep the repo private.

Settings4 settings that your agent asks about
  • context-library.repoWhich private GitHub repo holds your context library, such as you/notes?Default: from your context repo
  • context-library.pathWhich folder holds the checkout of your context library?Default: from your context repo
  • context-library.urlWhich web address opens a document of the library, before its path? Leave it empty for the repo's page on GitHub.
  • context-library.ownerWhose library is it, as the related context names it, such as Sam? Leave it empty for "your library".

Add Context library 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: Context library.

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.
   - Context library: ~/.local/share/fleet/engine/packs/context-library/SETUP.md
3. Turn the packs on with one command, and add the flags that the notes name:
   fleet packs --add context-library
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.
Open in T3 Code

Add more packs in one prompt