Keep a local safety copy of long application answers. Recover lost writing, check answer fit, and reuse approved paragraphs. Free, MIT-licensed, and private by default.
Draft Cairn keeps a local safety copy of supported answers on websites you choose.
- You're filling in a website's big answer box, perhaps explaining a project in a grant application.
- You spend half an hour writing.
- The website reloads or logs you out. Your answer disappears.
- If Draft Cairn was enabled beforehand and finished saving, you open its recovery workspace, preview your saved answer, and copy it back. You can also explicitly restore it when the original field is confidently matched and empty.
Protection must be enabled before the loss. Wait for saved on this device; text that has not finished saving may still be lost. Draft Cairn cannot keep you logged in or recover text written before protection was enabled.
Two other everyday uses:
- An answer that won't fit. You paste a 600-unit answer into a field with a declared 500-unit limit. Draft Cairn stops the oversized paste and opens the complete original in a larger editor, so you can edit it yourself. After an allowed paste, it also checks the visible result for silent changes and offers the original for review if needed. Server acceptance and later changes are not verified.
- A paragraph you use again. You explicitly save an approved project description in the answer library. Next time, search for it and copy it into your application.
This is an early preview. Commercial demand and broad compatibility have not been established. Keep a separate copy of important work.
| Light | Dark |
|---|---|
![]() |
![]() |
- Download
draft-cairn-0.4.0.zipfrom Releases, verify it againstSHA256SUMS, and extract it. - Open
chrome://extensions, enable Developer mode, choose Load unpacked, and select the extracted folder containingmanifest.json. - Pin Draft Cairn. On an ordinary HTTP/HTTPS website, open its popup and choose Enable for this site. Approve Chrome's site-access request.
- Type in a supported field and wait for saved on this device. Open Recovery & library to inspect saved text.
For a source checkout, load the extension/ folder directly. Chrome 120 or later is required. The publisher reports an existing Chrome Web Store listing. Submit new packages to that existing item to update installed users.
Preparing a store listing? The release also includes a separate draft-cairn-store-kit-0.3.1.zip with the icon, promotional tile, real-interface screenshots, listing copy, and reviewer instructions. Extract it and use its inner extension ZIP for the package upload. Asset guide · Final manual checks. Those manual permission and clipboard checks remain pending; prepared assets do not imply store approval.
- Visible, editable standard textareas, and ordinary text inputs with a declared
maxlengthof at least 120. - Plain-text answers in targeted top-level Quill, ProseMirror/Tiptap, CKEditor 5 and inline TinyMCE roots. Rich-text recovery uses copy back; formatting and attachments are not saved.
- Up to 180 recovery records in a rolling history; the oldest recovery records are removed when the count or byte budget is reached, with a visible notice. Explicit library answers are never evicted. Up to four snapshots per field. Rapid edits update the current snapshot; revisions at least 30 seconds apart can remain as earlier snapshots.
- One day of recovery by default on new installs (existing choices are preserved), configurable to 1, 3, 7, 14, or 30 days globally and per site. Increasing retention does not extend earlier records or defeat storage eviction. Complete oversized pastes expire within one hour. Expiry cleanup runs hourly while Chrome is running and on reads/startup.
- Library answers with a title and optional project. These remain until deleted; import/export uses a documented v1 format.
Supported ordinary fields and targeted rich editors can also save in open shadow roots and authorized HTTP/HTTPS frames. Enable both the containing site and an embedded form’s exact origin. Frame and shadow-root recovery is copy-only. Closed shadow roots, opaque/about:blank/srcdoc frames, generic contenteditable, browser-internal pages and incognito remain excluded. See the public portal and editor sample matrix and precise compatibility limits. A public demo result does not establish compatibility with every customer portal using that technology.
Focus a supported field, open the on-page Draft Cairn editor and choose Use library answer, or press Alt+Shift+L (configure conflicts in chrome://extensions/shortcuts). Choose a saved paragraph, inspect the projected result and character/word counts, then explicitly insert it at the saved cursor. Existing text outside your selection stays. A changed destination cancels insertion; oversized HTML limits disable it. The extension checks the visible result after 1.5 seconds. Rich editors remain copy-only.
A visible, explicitly linked 342/500 words or 120/500 characters counter can supply an advisory website limit. Local word counts are whitespace estimates; website rules can differ. Conflicting or unrecognized counters are ignored. These hints do not prove server acceptance or block form submission.
Choose Try a sample recovery in the toolbar popup for a local, synthetic save → reload → recover exercise using the real encrypted store. It does not grant website access. On real sites, enable protection before writing.
In Recovery drafts, select the saved revisions you want and choose Export selected snapshot. The readable Markdown file contains only those revisions, with question labels when page details were saved. It is an application snapshot, not proof of submission. It can miss fields that were never captured or have expired; exports remain outside vault protection.
For several portals, use Sites & settings → Enable several exact website origins to request their host access together. Both the parent website and the embedded form origin must be enabled for frame capture. No vendor-wide wildcard presets or untested compatibility promises are bundled. Optional organization policies restrict allowed origins and maximum retention; they never silently grant Chrome access.
A minimal Material-inspired interface with automatic light and dark themes. Choose Sites & settings → Appearance to follow your system or use a fixed light/dark theme. The choice applies to the workspace, toolbar popup and larger on-page editor, and stays available while the vault is locked. It is saved with encrypted local settings. Fonts and icons stay local. Reduced-motion and system high-contrast preferences are respected.
No analytics, accounts, advertising, remote AI, or answer transmission. Storage is in this browser profile, not synchronized. No URL query strings, fragments, or raw paths are stored. Page titles and field details are optional and off by default for new installs. Enabling them permits direct restoration when the match is safe; without them, drafts are copy-only. Existing installations keep their previous choice. Turning the option off removes those details from existing drafts.
Password, payment, one-time-code, hidden, disabled, read-only, and sensitive-hint fields are excluded. Sensitive autocomplete tokens are excluded; autocomplete="off" is supported. Specific credential/payment phrases are filtered without rejecting ordinary narrative labels such as “payment schedule”. The on-page status says when the focused field is unsupported. Filtering cannot identify every confidential answer. Answer records are encrypted automatically with a non-extractable key in this profile. For password-free use, leave that default on. For protection of answer contents in copied profile files, enable the optional passphrase vault in Sites & settings. New drafts still save while locked; unlock to read, search, restore or change library answers. A forgotten passphrase means losing those answers. The operational index, including selected origins, hashes, sizes and times, has a separate automatic key in the profile, so the vault does not hide that metadata from a profile holder. Neither mode protects an actively compromised browser/device. See the precise boundaries below. Read the privacy policy and security policy before using client information.
Block sites from the popup or exclude fields from the on-page editor. Exclusions can be removed in workspace settings. Choose session-only recovery to clear drafts when the browser/extension session ends; Chrome can keep running after its last window closes. This smaller 2 MiB buffer evicts oldest drafts if necessary; library answers stay persistent.
Delete one revision, a site's drafts and access, or all extension data in the workspace. The popup also offers Delete all, including while locked. Manually saved library answers have no site association; delete them separately or use Delete all. Choose readable JSON or passphrase-encrypted library exports. Export passwords are independent of the vault. Exports and clipboard contents, including OS clipboard history, remain outside the extension.
| Choice | Daily use | Protection boundary |
|---|---|---|
| Automatic (default) | No passphrase; answers open immediately | Encrypted record bytes; the key stays in the same profile, so a copied complete profile can expose answers. |
| Optional passphrase vault | Save while locked; unlock once per browser session to read | Protects encrypted answer contents in copied files/backups made after setup. Operational metadata uses a same-profile automatic key; it is readable to a profile holder. Forgotten passphrases cannot be recovered. |
In settings choose Enable passphrase vault, enter and confirm at least 12 characters, and acknowledge the recovery limit. Lock vault hides saved answers and clears unsaved workspace editors; it does not erase text on websites, open on-page editors, exported files or the clipboard. Close those separately when needed. Changing the vault passphrase leaves previously exported files unchanged. Returning to automatic encryption requires the current passphrase and re-encrypts existing answers. Keep a separate backup of important work; local storage and browser profiles can be lost.
Requires Node.js 24 and Python 3. No runtime dependencies or build step.
npm ci --ignore-scripts
npm test
npm run check
npm run demoOpen http://127.0.0.1:8765/index.html, enable protection, and use synthetic answers. The demo intentionally loses text on reload and has a Simulate session expiry button. Test the two identically labelled fields, excluded inputs, selection-aware oversized pastes, and emoji.
npx playwright install --with-deps chromium
npm run test:browser
python3 scripts/package.pyOn Windows use python instead of python3. Browser tests use trusted keyboard paste with a browser-populated clipboard, an isolated temporary profile and a test-only localhost host pre-grant. They exercise the shipped JavaScript; they do not automate Chrome's native permission dialog or revocation. Set CHROMIUM_PATH to a Chrome for Testing executable if necessary. Validation notes separate local, CI, and unverified checks.
The package script uses an exact file allowlist, fixed metadata, and uncompressed ZIP entries for reproducible bytes. The extension ZIP contains only the 19 runtime files; source, demo, tests, and policies remain in this repository. Icon generation is reproducible with python3 scripts/icons.py.
The separate store kit uses the committed listing screenshots, so fresh test screenshots cannot change its bytes. Check store image dimensions and transparent icon margins with python3 scripts/check-assets.py.
Plain JavaScript, HTML, and CSS keep review and maintenance straightforward. The service worker validates messages, serializes storage changes, limits size, and restricts direct storage access to trusted extension pages. Content scripts only receive their own save responses and explicitly requested restores. User text is rendered with textContent or value.
Restoration uses a hashed page path, a stable field descriptor, and the ordered form structure. Duplicate or missing identities refuse restoration. Pages with query strings or fragments support copying only. This conservatism reduces wrong-field restoration; it cannot prove that a website has kept the same meaning for an identifier. Always check restored text before submitting.
- Ten-tester pilot kit — invitation, synthetic tasks and grant-portal worksheet.
- Organization policy — optional origin restrictions and retention caps.
- Edge handoff — prepared instructions; native Edge testing and submission remain pending.
- Commercial validation — first users, alternatives, and decision criteria.
- Costs — current requirements, no recurring infrastructure, future cost categories.
- Store listing and submission checklist.
- Release notes.
No paid services or paywalls are included. No verified sponsorship destination was available, so no sponsorship link is included.


