FamiliarGet Familiar

Familiar documentation

Install Familiar and create your first module.

Install the app, connect Codex, and choose a folder for your campaign. Then start a conversation or use the module builder to draft an adventure.

Quick start

Set up Familiar in three steps.

  1. 01Install Familiar

    Download the desktop alpha, or install Familiar skills in your own agent. Both options are on the Get Familiar page.

    Installation options →
  2. 02Connect Codex

    Sign in with a ChatGPT plan that includes Codex, or connect your own OpenAI API key.

    Account setup →
  3. 03Open a campaign

    Create a campaign folder or select one that already contains your notes, images, and PDFs.

    Campaign structure →

Install

Install the alpha.

Choose the desktop workspace for guided campaign preparation, or choose the skills edition to work inside your existing agent.

Desktop installers

On Windows, download the .exe installer and follow its setup steps. On Linux, install the .deb through your package manager, or make the AppImage executable and open it. These alpha builds are unsigned. Your operating system may show a warning; compare the file’s checksum with the release page before installing. A macOS installer is not yet available.

Get Familiar →

Enable PDF formatting

Install Python 3.10+ and Poppler, plus the Python packages ReportLab, pdfplumber, and pypdf. Use a Python virtual environment if your system manages Python packages; launch Familiar with PYTHON_BIN pointing to that environment’s Python. Familiar includes its renderer and fonts. The skills installer prints a setup command that creates its own PDF environment.

Prefer your own agent? Follow the skills setup guide →

Collaborator source build

You will need Node.js 22 or newer, pnpm 10, Git, a separately installed Codex CLI, and access to the private source repository.

cd the-familiar-codex
pnpm install
pnpm dev:desktop

The development command starts the renderer and Electron shell together. Keep the terminal open while using the source build.

Agent access

Sign in to Codex.

Familiar does not include or update the Codex executable. Install Codex using the official OpenAI guide, run codex login, and then open Familiar. Familiar connects to codex app-server, so the desktop app uses the same threads, approvals, questions, plans, and tool events as Codex.

Codex is a separate prerequisite

Familiar discovers Codex on your system but never downloads, bundles, or updates it. After installing or updating Codex, use Check again in Familiar.

Open the official Codex installation guide →
Recommended

Sign in with ChatGPT

Choose Sign in with ChatGPT, finish the browser login, and return to Familiar.

  • Uses your eligible ChatGPT plan
  • Shows account and rate-limit status
  • No API key to paste into Familiar
BYOK

Use an OpenAI API key

Open Settings, choose the API-key option, paste the key, and connect it to the local Codex runtime.

  • Usage is billed to your Platform account
  • Useful for separate project accounting
  • Disconnect any time from Settings
Your AI account

Familiar uses your Codex account. You do not need a separate AI subscription from Familiar.

Campaigns

Choose your campaign folder.

A Familiar campaign is a normal local folder. Start empty or use a folder with existing Markdown, images, PDFs, rules references, and notes. Familiar stores runtime state in .familiar/codex/; the campaign material remains readable outside the app.

my-campaign/
├── campaign.md
├── characters/
├── locations/
├── sessions/
├── artifacts/
├── modules/
└── .familiar/
    └── codex/

Your first conversation

  1. 1

    Create a campaign or select an existing one from the left rail.

  2. 2

    Start a conversation with an idea, a question, or something you want help preparing.

  3. 3

    Include your party’s level, the game system, and any campaign details you want to use.

  4. 4

    Talk through the suggestions and tell Familiar which parts you want to develop.

Module workflow

Draft your first adventure.

Choose Make a ready-to-run adventure on the start screen when you’re ready to draft. Fill in the brief and decide whether to compare hooks or use an idea you already have.

  1. 01
    Brief

    Describe your idea, party, tone, and session length in the adventure brief.

  2. 02
    Hooks

    Compare three to five adventure hooks, or use an idea you have already chosen.

  3. 03
    Selection

    Choose a hook and confirm it before Familiar starts the full draft.

  4. 04
    Draft

    Codex writes the complete adventure inside the campaign workspace using the selected hook.

  5. 05
    Evaluate

    Familiar checks for inconsistent details, missing material, rules references, and how well the adventure will work in play.

  6. 06
    Save and export

    If needed, Familiar revises the draft once. It then saves the adventure, linked notes, and an export bundle. PDF formatting needs the dependencies below.

Give Familiar a starting point

Create a one-session mystery for four level-3 characters.
Use the people and unresolved debts in this campaign.
Keep the threat intimate, include one social confrontation,
one dangerous location, and a player-facing handout.
Pause so I can choose the hook before drafting.

Files and ownership

Find and reuse your finished work.

Familiar saves the adventure and separate files for its NPCs, locations, encounters, secrets, and handouts. Export a module bundle to move the adventure and its supporting files between Familiar campaigns.

Conversation

Your saved conversation, including Familiar’s questions, plans, and the actions you approved.

Artifact

An editable campaign note, such as a character or location, with links to related notes.

Bundle

The adventure and its supporting files, packaged so other Familiar tools can open them.

Print output

The interior and cover PDFs, page previews, and results of the print checks.

Printing

Review the PDFs before checkout.

The print flow renders the module, checks page count and trim requirements, produces separate cover and interior PDFs, and opens a private proof page. Nothing is sent to print until checkout is complete.

  1. 1

    Review the interior PDF page by page and inspect the full cover spread.

  2. 2

    Request a live price based on format, page count, destination, and shipping method.

  3. 3

    Pay in your browser through Stripe Checkout.

  4. 4

    Familiar submits the approved files to Lulu and keeps the private order page updated.

Production delay

A paid Lulu order waits in a configurable production-delay window before printing begins. That provides a final recovery window; it is not an error state.

Open the Fields & Tides proof →

Architecture

What runs locally and what uses the web.

On your computerDesktop, Codex runtime, campaign, and generated working files

Your campaign files are saved on your computer. Familiar uses the Codex installation on that computer for AI conversations.

On Familiar’s web serviceDownloads, community modules, book proofs, checkout, and order status

Familiar’s website lets you share modules, review book proofs, and order printed copies.

With outside providersYour AI account, Stripe payment, and Lulu printing

Codex sends your prompts and relevant campaign context to your AI provider. Stripe handles payment; Lulu receives the book files and delivery details for printing.

Troubleshooting

Fix common setup and order issues.

Familiar says Codex is disconnected.

Confirm that the Codex CLI is installed and available to the desktop process. Verifycodex app-server starts in a terminal, then choose Check again in Familiar. Source builds can use FAMILIAR_CODEX_PATH for non-standard installations.

ChatGPT sign-in opened, but Familiar still shows signed out.

Finish the browser flow, return to the desktop app, and wait briefly for the account state to refresh. If it times out, reopen Settings and start the sign-in once more.

The agent cannot find campaign material.

Check that the selected workspace is the campaign root and that the files are readable. Name the relevant artifact or path directly when you know it; precise retrieval is faster and safer.

A module stopped before the draft.

That is expected when hook selection is required. Open the module panel, compare the proposed hooks, select one, and continue the staged run.

A paid print order is still “Production Delayed.”

The order is paid and waiting for Lulu’s configured delay to expire. It should advance to production automatically unless Lulu reports a separate rejection or file problem.

Try the current alpha

Open a campaign and create a module.

Download an installer for your computer or install the skills in your existing agent.

View download optionsReview the module workflow