# Second brain

Your goals, plans, notes and the people you work with, in plain files every agent you use can read and keep up.

This is a recipe from flie: a person can read it first, and an agent follows
it. It makes one folder in the person's flie, with a README in it that holds
the rules, so every agent that opens the folder later works the same way.

## 1. Make sure flie is set up

If the `flie` command is not found or `flie whoami` says nobody is signed in,
and you have no flie tools over MCP, set flie up first, with the person's
authorization, by following https://flie.sh/setup.md
Then come back here.

The steps below are `flie` commands. Over MCP, call the tools of the same
names, with the same arguments written as named arguments, and pass a file's
text as `content` instead of `--from`.

## 2. Make the folder

`flie whoami` prints the person's Root folder. Make the folder there unless
the person names another place. If a folder called "Second brain" is already
there (`flie agent list <root ID>`), use it: read its README and follow it
instead of starting again.

    flie agent mkdir <root ID> "Second brain"
    flie agent mkdir <folder ID> "journal"

Each command prints the new item's name and its ID; every later command names
the item by that ID. Laid out, the folder is:

    Second brain/
      README.md      the rules
      goals.md       what you are working towards
      this week.md   focus, waiting on, reminders
      ideas.md       anything to come back to
      journal/       one file a day

## 3. Write the README, then start

Write this README into the folder, adapted where the person says so, with the
text on stdin:

    flie agent create --from - <folder ID> "README.md"

~~~markdown
# Second brain

What <the person> wants every agent to know: goals, plans, notes and people.
Agents read it before helping and keep it up when something changes.

- goals.md: what they are working towards.
- this week.md: this week's focus, what they are waiting on, reminders.
- ideas.md: anything to come back to, newest first.
- journal/: one file a day, named "2026-09-30.md".

## Rules

- Keep each file short. Link to another file rather than repeating it.
- One subject per file. Start a new file when a subject outgrows its place, and
  list it here.
- Write down only what the person told you or asked you to keep.
- Change files in place; every earlier version is kept.

## When to write

- When the person tells you something worth keeping about their goals, plans,
  work or people.
- At the start of a conversation, read this README and this week.md.
~~~

Then create goals.md, this week.md and ideas.md the same way.

Ask the person what to keep first, and write only what they tell you. Don’t bring in anything they didn’t point you to.

## 4. Ask the person, then connect their other agents if they want

Any agent reaches this same folder once its host has flie's server registered,
once per host. Offer it; register only the hosts the person asks for:

- **Claude Code** — `claude mcp add --transport http flie https://flie.sh/mcp`
- **Codex** — `codex mcp add flie --url https://flie.sh/mcp`, then `codex mcp login flie` to sign in
- **Cursor** — add `{"mcpServers": {"flie": {"url": "https://flie.sh/mcp"}}}` to `~/.cursor/mcp.json`

In Cursor, flie shows Needs authentication under Tools & MCPs in its settings, and Connect there is what opens your browser. The person completes each sign-in, not you.

## Done

Tell the person what you made, give them the folder's link
(`flie agent link <folder ID>`), and ask whether to connect their other agents (step 4).
Editing its README changes the rules for every agent that reads it. How to
change a file without losing anyone's edits: https://flie.sh/skill.md.
End your reply with the question in step 4.
