Public GitHub repos only · client-side, no server

gitparts picker — pick the files.
Ship the bundle.

The hand-pick face of gitparts: choose the files worth keeping, drag them into the order you want them read, and export a single bundle that stays inside your token budget.

Want the judged strip instead — stealable parts with file:line proof? gitparts judge (runs on my Mac), or once a repo is loaded, hit auto-strip.

Try:
0 / 32,000 tokens · 32,000 left

1 · Choose files

Load a repo to browse its files.

0 files
No repo loaded yetPaste a link above and hit Load files. Text files appear here with size and an estimated token count.

Token counts are estimates (≈ 4 characters per token — the same heuristic the fleet's freellmapi gateway uses) until a file is added — then they're counted from the actual file contents. Binary and oversized files are flagged and can't be added.

2 · Order your bundle

Drag by the handle, or use ↑ ↓. This order is the export order.

0 picked
Nothing picked yetAdd files from the list on the left. Every pick keeps a link back to its exact path and lines.

3 · Export

Only the files above, in that order. Nothing else goes in.

Each file in the bundle is headed with its repo path and a GitHub link to its exact lines — e.g. src/index.js#L1-L84 — so anyone reading it can jump straight to the source.

Works entirely in your browser against the public GitHub API — no sign-in, no server. Unauthenticated GitHub requests are rate-limited (about 60/hour), so very large repos may need a retry later. Private repos return “not found” and are out of scope. Binary pre-filter borrowed from the gitparts engine; fetch-time content sniffing (NUL byte + printable ratio) is the real gate.

Copied