sources/ directory, where it becomes available for the compile pipeline. Every ingest produces a single Markdown file with YAML frontmatter recording the source URL or path, the detected source type, the ingest timestamp, and a truncation flag if the content exceeded the character limit. That file is the stable, content-addressed record the compiler reads.
You typically ingest first and compile second. If you’re just getting started and want to do both in a single step, see llmwiki quickstart below.
llmwiki ingest <url|file>
<url> or reads <file> from disk, converts the content to Markdown, enforces a character limit, and writes the result to sources/<slug>.md. After a successful ingest the CLI prints the saved path and reminds you to run llmwiki compile.
Supported source types
llmwiki ingest detects the source type automatically:
Content longer than 100,000 characters is truncated. The saved file records
truncated: true and originalChars: <n> in its frontmatter so downstream tooling knows the source is partial.
Flags
llmwiki ingest takes no flags beyond the positional <url|file> argument. Source type detection, character limits, and output paths are handled automatically.
Examples
SSRF considerations
llmwiki ingest is a server-side fetch primitive - it follows the URL you give it and reads files from disk. Only pass trusted input to llmwiki ingest. If you’re building a tool that ingests user-supplied URLs or untrusted strings, use the SDK’s ingestText() method instead. ingestText accepts raw text without making any network requests or filesystem reads, so it is safe for untrusted content.
llmwiki ingest-session <path>
sources/. Session export files are JSON records that capture the full conversation transcript from an AI coding or chat session. llmwiki ingest-session parses the file, identifies the adapter (Claude / Codex / Cursor) automatically, formats the conversation as Markdown, and writes it to sources/ with frontmatter that records the adapter name, session start/end times, and participant identity when present.
You can pass either a single session file or a directory. When you pass a directory, llmwiki ingest-session scans every file at the top level of that directory, imports all recognised session files, and skips unrecognised ones with a warning. The batch run throws an error if zero files were imported, so you always know if something went wrong.
Examples
sources/ just like any other ingest result. The compile pipeline treats them identically to web or file sources - concepts are extracted from the conversation text and turned into wiki pages.
llmwiki quickstart <source>
quickstart is a first-run convenience wrapper that ingests a source, compiles the wiki, and opens the local viewer - all in one command. It is the fastest way to go from zero to a browsable wiki.
Under the hood, quickstart runs ingest then compile. Compile requires LLM credentials; if credentials are missing, the source is still saved to disk before quickstart reports the compile failure, so your content is preserved and you can run llmwiki compile manually once credentials are configured.