Pack

Pack reads a folder and writes its text files into one file you can hand to an AI model. Before it writes anything, it shows what goes in, what stays out and why.

Where it is

Superpowers › Pack › Open, in the Developer category. The card is always shown: there is no switch for it in Settings › Integrations. The page has one screen: the form at the top, and the plan below it.

How to use it

1. Paste a path in Folder, click Choose folder, or drop a folder on the window. Dropping or choosing a folder plans it right away.
2. Narrow it down if you want, with Include only (globs) and Leave out (globs), and set a Token budget.
3. Click Plan. Nothing is written: you get the list of files with their token counts, and the list of what was left out.
4. Click Build pack. The page shows Pack ready with the path of the file, its token count and its size.
5. Click Show in folder or Copy path.

The plan

The first table lists each File, how it goes in (Detail) and its Tokens. Tokens are an estimate: one token for every 4 characters. The table shows the first 100 files and says how many there are in total.

Left out lists every file that stays out, with the reason:

Reason	What it means
Ignored by git	The file matches a .gitignore rule of the folder.
Binary	The file is not readable text.
Lockfile	A dependency lockfile, such as Cargo.lock or package-lock.json. The pack gets one line with its package or line count instead.
Too large	The file is bigger than 1 MB.
Possible secret	The file is a .env file, or a line looks like a private key, a cloud access key or an API token. The row shows the file, the line and the rule that matched.
Your rule	The file matches Leave out (globs), or does not match Include only (globs).

The .git folder is never read. Secrets are never included, and there is no option to include them.

Token budget

With a budget, Pack fits the folder into it by shortening the largest files first:

Detail	What goes into the pack
Full	The whole file.
Outline	Only the lines that declare something: headings, functions, classes, types and exports.
Path only	Just the file’s path.

A bar shows how much of the budget is used, and a line says how many files were shortened. If the folder still does not fit, the page says Over budget and how many files did not fit: raise the budget or leave more out.

Options

Option	What it does	Default
Include only (globs)	Keeps only files that match, in gitignore style, like src/**, *.md. Separate rules with commas.	Empty: every file
Leave out (globs)	Drops files that match, like **/*.test.ts.	Empty
Token budget	The most tokens the pack may have.	No limit

The pack file

The file is plain text: a list of the files, a short Dependencies section with the lockfile summaries, then each file under a line with its path. From this page it is created as a new file in your system’s temp folder, in omniget-devtools. A pack never replaces an existing file.

For AI agents

dev_pack of the MCP server does the same work in two steps. op=plan returns the token estimate per file and every exclusion with its reason. op=build writes the pack and returns its path and manifest, not the text itself; output sets the file to create, which must not exist yet. include, exclude and maxTokens are the same three options as above.

The tool needs the devtools_read permission. From a terminal, omniget-cli tool dev_pack op=plan path=. calls it while the app is running. See Command line.

Common problems

“No files to pack.”

The filters left nothing. Check the folder and the include rule, or point at a folder that has text files.

The folder has too many files

Pack stops above 20,000 files and lists the folders that hold the most. Point Folder at one of them, or narrow it with the include and leave-out rules.

A file I need was left out as a possible secret

Pack does not include it. Remove the key from the file, or paste that file into your prompt by hand after checking it.

A file shows as Outline but I need it whole

Raise the Token budget, or leave other large files out so this one fits.