# Getting started

Write a note, connect an agent, and see how its edits reach your notes only through you or a grant you made.

## Your first note

Open Fastpad and start typing. The first note exists before you have an account: it lives in a CRDT in your browser and is adopted into a workspace when you sign up. Nothing is lost in between, and nothing about that first note is a demo.

Every block — every paragraph, heading, list item, code fence — is given a stable identifier the moment it is created. That identifier is what lets a comment, a citation or a link point at the middle of a note and still be pointing at the right thing after the note is rewritten around it.

- Press `/` for the block menu: headings, lists, tables, code, callouts, toggles, columns.
- Press `Cmd/Ctrl-K` for the command palette.
- Type `[[` or `@` to mention another note. The link is a real edge, not a string.
- Press `Cmd/Ctrl-Z` as usual. Undo is local and never fights a sync.

## Organizing without deciding first

There is no database to create before you can write. Notes are notes. When a set of them turns out to be the same kind of thing, apply a type — `#Person`, `#Meeting`, `#Project` — and that type brings its properties with it.

Typing is optional, retroactive, and multiple: a note can carry several types at once, and untyped notes are completely first-class. Once notes share a type you can save a view over them — table, board, calendar, gallery, list or timeline — and embed that view inside any other note. See [Concepts](/en/docs/concepts).

## Connect an agent

Fastpad speaks the Model Context Protocol. Point any MCP client at the endpoint below and it can search, read, traverse links and propose edits.

```text
https://mcp.fastpad.ai
```

Mint a token in Settings → Agents & tokens (also linked from the Agent activity page), where you choose its scopes and autonomy and can revoke it later, or run `fp login` in a terminal. An unauthenticated request answers 401 with a challenge telling the client exactly where to authenticate.

> **Important:** By default an agent's edits are proposals: it hands you a review URL and nothing reaches the note until you accept. When you mint a token you can grant more — `turns:accept` lets the agent accept its own proposals, marked as agent-accepted, and auto-apply lets its edits land without a proposal. Either way every such write stays marked and is listed on the Agent activity page for you to review or revert. See [Agents](/en/docs/agents).

## Your notes are files you can read

Everything serializes to CommonMark with YAML frontmatter and a `{#blockId}` anchor after each block. That is one canonical format, used by the export, the API, the agent tools and the on-disk mirror — there is no second, lossier one.

```bash
fp pull ./my-notes     # the whole workspace, as Markdown
fp push ./my-notes     # send your local edits back
```

Because each block carries its anchor, `fp push` reads which paragraph is which block rather than guessing. See [Markdown](/en/docs/markdown) and the [CLI](/en/docs/cli).

## Where to go next

- [Concepts](/en/docs/concepts) — notes, blocks, types, collections and links
- [Agents](/en/docs/agents) — what an agent can and cannot do, and why
- [MCP](/en/docs/mcp) — the tool surface, in detail
- [CLI](/en/docs/cli) — `fp`, for terminals and CI
- [API](/en/docs/api) — the HTTP surface