AI Context Builder 100% local

AI Context Builder for Local Files

Build one private context.md from documents, source code, configs, or a reviewed project folder.
Source files
Documents, source code, configs, or a project folder
No files
0Files
0Context tokens
ReadyTarget fit
0Secret warnings
No context No files
context.md
Editable LLM-ready Markdown handoff
0
local conversions counted worldwide Your files never leave your browser. Copying or downloading context.md only adds an anonymous +1.

AI context builder

Build one private context.md from local files or a folder.

Combine documents, source code, configuration files, or a local project folder in one structured handoff for ChatGPT, Claude, Codex, Gemini, or another LLM. MarkDone preserves relative folder paths, keeps source boundaries visible, estimates tokens, and detects common secrets without uploading your files.

Real project foldersInclude Swift and other source code, apply root and nested .gitignore rules, keep relative paths, and add a compact file tree.
Secret-awareDetect and optionally redact common keys, tokens, private keys, and password-like values before pasting.
Private by designPDF extraction, DOCX parsing, scanning, and token counting run in the browser.
All MarkDone tools How to build an LLM context pack Claude and Codex project context guide Token Counter JSON to TOON Markdown to PDF

Build one context.md from multiple files

  1. Drop supported files or choose Add folder and review its contents.
  2. Keep Redact secrets enabled unless you need exact raw text.
  3. Copy the Markdown for any LLM or download context.md for reuse.

Select and review the sources you include

Include or exclude each file before sharing. The generated Markdown keeps file names, metadata, token estimates, and clear begin/end markers so you can review exactly what an LLM will receive.

Keep secrets out of AI prompts

MarkDone checks common API keys, bearer tokens, private keys, JWTs, cloud keys, and password-like assignments. Optional redaction replaces detected values locally before they enter context.md.

Check the token budget before sharing

Choose a planning target and compare it with the estimated context size. If the pack is too large, exclude low-value sources or split the work into smaller, task-specific packs.

Use the context pack with ChatGPT, Claude, Codex or Gemini

The output is plain Markdown rather than a provider-specific format. Copy it into a chat, download context.md for a handoff, or reuse it with coding agents and local models. For the complete workflow, read how to build an LLM context pack from local files.

Context pack vs CLAUDE.md, AGENTS.md and project memory

MarkDone creates a portable file-based handoff for the task in front of you. It does not generate persistent tool-specific instruction files or replace the native project memory of a coding agent. See the Claude and Codex project-context guide for the practical differences.

What is an AI context builder?

An AI context builder prepares the source material an LLM needs. MarkDone extracts readable text, preserves file names and source boundaries, checks the token budget, warns about common secrets, and creates one portable context.md file.

What should a context.md file contain?

A useful context.md contains a clear task, a source summary, file metadata, warnings, and one labeled section per source so an LLM can distinguish and compare the evidence.

Are my files uploaded?

No. MarkDone extracts text, counts tokens, scans for secrets, and builds context.md inside your browser. Your source files are not uploaded to MarkDone or to a model provider.

Can I combine PDF, DOCX, Markdown, JSON, TOON, YAML and CSV?

Yes. You can combine readable PDF and DOCX files with Markdown, plain text, JSON, TOON, YAML, YML, and CSV sources in one context.md. TOON is preserved as readable structured text. Scanned PDFs require OCR and are not supported yet.

Can I add a whole folder?

Yes. Click the main drop area, choose Add folder, or drag and drop a folder to review supported files before import. MarkDone preserves relative paths, leaves files from common generated folders such as node_modules and dist unselected by default, and adds an included file tree to context.md. Free includes one context pack with up to 25 files per day.

Can I include Swift and other source code?

Yes. MarkDone supports common Apple, web, backend, systems, shell, and project file formats, including Swift, JavaScript, TypeScript, Python, Go, Rust, Java, Kotlin, C, C++, shell scripts, Dockerfile, Makefile, and common configuration files. Sensitive configs, lockfiles, generated folders, and minified output remain visible but start unchecked. Binary files are not read as source text.

Does the project importer respect .gitignore?

Yes. MarkDone reads root and nested .gitignore files locally, applies common Git ignore patterns including wildcards, directory rules, anchored paths, and negation rules, and leaves matched files visible but unchecked in the review. You can still include an ignored file manually.

How do I use context.md with Claude or Codex?

Review the generated Markdown, replace the task placeholder, then copy it into a chat or download context.md for a project handoff. The plain Markdown format also works with ChatGPT, Gemini, coding agents, and local models.

What happens when the context pack is too large?

MarkDone compares the estimated token count with the selected planning budget. If the pack is too large, exclude low-value files or split the task into smaller context packs before sharing it.

Does MarkDone generate CLAUDE.md or AGENTS.md?

No. MarkDone generates a portable context.md handoff from the files you select. It does not create tool-specific project instruction files such as CLAUDE.md, AGENTS.md, or GEMINI.md.