Context Pack Help
Review browser captures before adding them, bring in supported local files, organize up to 10 retained sources, then inspect and export one editable context-pack.md.
What you see first
The first run opens Bring several sources into one workspace. Choose Start adding sources or skip the tour. After that, the left column adds and manages sources; the right column holds the built Markdown output.
Only the “tour completed” preference is remembered. Use Help in the workspace header to open the tour again. Closing or reloading the workspace discards its editable session.
Install Context Pack with Add to Chrome, then choose the recipe for your source. These steps use the current extension, not an online upload form.
Open the page and let the content you need load. Open Context Pack and choose Capture page. Check the editable Review capture result, choose Add to pack, then Build context pack. Finish with Copy Markdown or Download .md. See the browser capture walkthrough.
Open the extension and choose Open current pack. In the workspace, use Choose files or drag and drop a supported local file. After validation and conversion, it appears in the source list without a browser-capture review panel. Build the pack and inspect the Markdown before exporting. Check PDF and file limits.
Keep the workspace open. Capture another page or add another file, finishing any pending review first. Reorder or exclude sources, then build again. Up to 10 retained sources share one pack. Copy or download before closing or reloading; the editable session is not saved.
The popup closes and Chrome opens or focuses the dedicated workspace for review.
See the flow → 02 · TabsCapture another tab without losing the sources already in the pack.
See the flow → 03 · FilesPDF, DOCX, Markdown, and text files convert locally into the source list.
See the flow → 04 · OutputArrange sources, build once, edit the output, then copy or download.
See the flow →On a regular page, open Context Pack and choose Capture page. The popup closes; Chrome opens or focuses the Context Pack workspace and stages a Review capture panel. Check the title, sanitized URL, warnings, and editable Markdown, then choose Add to pack.
Leave the workspace open, move to another page, then capture again from the toolbar, right-click menu, or shortcut. Chrome focuses the existing workspace for review. After Add to pack, the first source remains and the counter becomes 2 included · 2 / 10.
Open the workspace, then choose or drop selectable-text PDF, DOCX, Markdown, or UTF-8 text files. They convert locally and enter the source list after validation. Unlike browser captures, local files do not use the staged Review capture editor.
Use the left column to include, exclude, reorder, or remove retained sources. Choose Build context pack; the right column shows editable Markdown and a local token estimate. Finish with Copy Markdown or Download .md.
Toolbar, right-click, and keyboard actions all stage browser content in the current workspace before it is retained.
Capture page reads the current page. Highlight text first to use Capture selection. Open current pack focuses the workspace without capturing.
Use Context Pack → Capture this page or, after highlighting text, Capture selected text.
Alt+Shift+M on Windows/Linux or Option+Shift+M on macOS captures the current page. Inspect or change the assigned command at chrome://extensions/.
New pack asks for confirmation when work exists. Closing or reloading always clears the editable session.
The limits keep local conversion and review predictable and prevent partial content from entering a pack.
On an eligible direct HTTPS URL whose path ends in .pdf, the popup changes to Capture PDF. Context Pack makes the requested fetch, validates the response, and parses it locally.
Embedded, custom, blob, protected, or plain HTTP PDF viewers are not direct-PDF capture targets. Download the file and add it locally, or open a supported direct HTTPS .pdf URL.
Markdown/text: 1.5 MB each. PDF/DOCX: 20 MB each and best under 10 MB. PDF: 30 pages per file.
10 retained sources, 50 MB total retained source bytes, 60 PDF pages, and 500,000 generated UTF-16 code units in the final pack.
No OCR for scanned/image-only PDFs, encrypted PDF or DOCX, legacy .doc, or malformed non-UTF-8 Markdown/text files.
A rejected capture or file shows a clear error and does not add partial content or replace sources already retained.
Context Pack does not passively read tabs and does not require a TryAIBlock account.
Chrome grants temporary access only after you invoke capture on the current tab.
Page, selection, and file conversion runs in the extension. An eligible direct PDF makes one requested HTTPS fetch from its current URL.
The source list and editable output stay in the loaded workspace. Copy or download before closing if you need to keep the result.
Capture converts readable content from the current main page; it is not a screenshot or a crawl of linked pages. Hidden or unloaded content, media, and unsupported embedded frames may be omitted. Let the desired section load, capture again, and inspect the warnings before adding. Use Capture selection for a specific visible passage. Do not expect interactive dashboards to retain every visual or control.
No OCR is included: PDFs need selectable text. DOCX conversion preserves supported document structure, not page layout; embedded images are omitted and complex or merged tables may lose fidelity. Review the output before use.
No. It does not bypass access or download restrictions. For a custom or embedded viewer, use a supported direct HTTPS PDF URL or add a local copy only when the site allows it. Check capture troubleshooting.
That is the intended workspace-reuse flow. It keeps earlier sources together and avoids duplicate Context Pack workspaces.
Highlight visible text in the main page first, then invoke Capture selection. Content inside unsupported embedded frames is not part of the main-page selection.
A browser or site viewer may be a webpage rather than a supported direct HTTPS PDF response. Download the PDF and add it locally when the site allows it.
It is not silently persisted. It remains only in the loaded workspace memory until you close or reload it; copy or download the generated Markdown to keep it.
