# Quickstart

Create a project, write a few lines, and export your first PDF.

Start with a document you actually need: a paper, a class report, or a resume. You can write and compile without configuring AI.

![A complete paper in the writing workspace: project files, editable LaTeX, and PDF preview.](https://cdn.oleafly.com/images/screenshots/desktop/docs/llama-writing-dark-window-v2.png)

## Install Oleafly

[Download the app](https://github.com/Oleafly/Oleafly/releases/latest) and open it. The [installation guide](/docs/install/) covers each platform. No account is required.

## Choose a starting point

1. Click **New project** in the library.
2. Choose a template and document format. LaTeX is a good fit for established journal classes; Typst offers a compact typesetting language; Markdown suits prose with lightweight markup.
3. Name your project and create it.

Already have source files? [Import your project](/docs/import-project/) instead. For a paper with research notes and data, use a [research starter](/docs/research-workspace/).

## Write and compile

Edit the source on the left. Press **⌘Enter** on macOS or Ctrl+Enter on Windows and Linux. Your compiled PDF opens beside it.

The first LaTeX build downloads the packages your document needs. Later builds reuse that cache. If a build fails, open its diagnostic to reach the source line; [Compiling](/docs/compiling/) explains the build controls and log.

In LaTeX, type `\` for command suggestions or `/` for the insert menu. Try inserting a section, equation, or citation. LaTeX and Markdown also offer a **Code / Visual** toggle for prose editing.

## Add a reference

Open **Add citation** from the toolbar. Look up a DOI, arXiv identifier, or title, check the record, then insert it. Oleafly adds the bibliography entry and uses the citation syntax for your document format.

[Read the citation guide →](/docs/citations/)

## Check and export

Open **Preflight** to inspect the document before sharing. Use **Export as PDF** for the finished document or **Export source (.zip)** to send the project files.

Successful compiles also save [checkpoints](/docs/checkpoints/) when automatic checkpoints are enabled. You can return to one later from **Versioning**.

## Try an assistant

[Connect a provider or CLI agent](/docs/ai-setup/), then ask for something specific:

> Shorten the abstract to 200 words. Keep the numerical results and citation keys unchanged. Show me the edits.

Use **Ask for approval** to review edits as the assistant works. For a larger job on a separate copy, create a [research task](/docs/research-tasks/).
